[polakamtejas]

Problem

agent-env up from a PyPI install serves only the API: the wheel has no explorer/static/ (0 files in 0.9.1374), though pyproject.toml says the built UI ships there. Nothing in the release builds it.

Change

• publish-pypi.yml: a new explorer-ui job runs npm ci && npm run build:static and uploads out/. The framework job downloads it into src/agent_env/explorer/static/ before uv build, and fails if the wheel has no index.html. The UI builds in its own job, so the job that publishes to PyPI still runs no npm.
• pyproject.toml and .gitignore: explorer/static is a git-ignored hatch build artifact, like published_images.json.
• Explorer README: a release ships the UI; a source checkout still uses [explorer] static_dir.

Testing

• The release's own uv build --no-sources --out-dir dist, with a placeholder explorer/static/, ships it in both the source archive and the wheel, leaves explorer/ui/ out, and git status stays clean.
• The workflow runs only on a release tag, so this PR's CI doesn't exercise it.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge; the latest change addresses the missing UI in the source archive.

Summary

The release workflow builds the explorer UI separately and includes it in the Python package.

• Release installs can serve the Explorer web page with agent-env up.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Build explorer UI] --> B[Upload built files]
  B --> C[Download into explorer/static]
  C --> D[Build source archive]
  D --> E[Build wheel]
  E --> F[Check index.html]
  F --> G[Publish to PyPI]

Loading

_{Reviews (2) · Last reviewed commit: "fix(explorer): keep the built UI in the ..." · Reviewed by Greptile}

[earakely-scale]

🤖 Automated Claude routine — Env Pod PR Context Review. This is a bot, not Edgar Arakelyan; not a human review.

Context from outside this diff — the release path, not the change itself.

The new explorer-ui job and the wheel assertion it adds in .github/workflows/publish-pypi.yml (needs: main-ci, and framework now also gated on needs.explorer-ui.result == 'success') only run once a release tag's main-ci passes. That gate is red on main right now, so nothing has published since before this PR opened:

• main's tip 1a35e48 ("bump version to v0.9.1379") has Local backends (.github/workflows/local-backends.yml) → failure, main-ci → failure, and release → skipped (run 40797891696). main-ci waits for local-backends.yml, clean-install.yml and plugin-api.yml to have passed on the tagged commit, and exits 1 otherwise — which skips framework, and so the new explorer-ui job too.
• PyPI's latest agentenv-framework is 0.9.1378, so v0.9.1379 never shipped.
• test(env): import LocalSandbox from its new module in the artifact staging test #381 is the one-line fix for that red gate (the artifact-staging test still importing LocalSandbox from the module feat(computer): computer envs deploy on local Docker #369 moved).

Net: nothing to change here — just that the built UI first reaches a wheel on the earliest release tag whose commit has a green Local backends, i.e. after #381 (or an equivalent) lands, not on the next version bump by itself.

---

Generated by Claude Code