The cluster never ran Theia or the IDE gateway, so every workspace stayed
"未配置" forever. The feature is gone instead of half-present:
- API: workspace, launch and lifecycle endpoints, the gateway identity and
its internal routes, the dispatcher's workspace provisioning and the
lifecycle worker. Migration 003 deletes stored workspaces and settles
their pending outbox items.
- Provisioner: workspace provisioning and lifecycle for both backends.
- Web: the 云 IDE panel, the launch route, the start-branch picker that
listed IDE branches, and the workspace count on usage.
- apps/ide, infra/oct, dev:ide and the CI job; IDE parts of local k3s,
network policies, RBAC, docs and the architecture diagram.
A wish can still start from a pushed branch through the API (sourceBranch).
Plan files and stored entitlements may still carry maxWorkspaces; it is
accepted and ignored.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
What the pilot asked for, from its meeting:
- Code review: a project names the paths changes to which a person reviews
before they reach the target branch (globs, with exceptions). After the
checks pass, the verifier asks the control plane, and the run waits at
integration until an owner or admin approves the exact commit; approving
integrates it without repeating the checks, rejecting hands the comment to
the agent as a new requirement. Continuing cannot get around it: the
verifier asks again before every integration.
- Undo: "take back this change" starts a run that reverses what a run
integrated on the current target branch, three-way, keeping later commits;
only lines later commits changed too go to the agent. It then verifies,
integrates and delivers like any run. Releases get a rollback button for the
version live in their environment.
- Wish optimization: the local Claude account rewrites a draft wish and its
acceptance criteria by built-in and project rules, with no tools at all;
the person compares and decides, nothing is submitted for them.
- Release confirmation: an environment can make every release wait for a
person, not only those the risk rules flag.
- Feishu notifications: a group bot is told of releases awaiting approval and
changes awaiting review (mentioning the decision makers), runs that need a
person, finished runs and failed releases; each once, signed when a secret
is set, with text from runs never acting as card markup.
- Reviewers see the agent's change summary and who submitted the wish, and
whether the checks ran in the macOS sandbox; the wish form offers only the
executors this deployment can run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pausing revoked the executor at once: the agent was killed and the work
of the current attempt stayed only in the executor's local workspace,
so continuing started that attempt over.
A pause of a run whose executor holds the lease now drains it first:
- The run keeps `running` with pauseRequestedAt (the console shows
pausing). Its agent gets no model credential and no new model
request; continuing is refused until the pause completes; cancelling
still stops it at once.
- The executor learns of it from its heartbeat, stops the agent, saves
a checkpoint with its live lease and completes the pause through
/internal/runs/:id/pause. Continuing restores that checkpoint.
- The workflow is stopped only after the pause completes; stopping it
earlier would abort the save. A model request interrupted by the
stop no longer expires the pausing run's lease.
- If the executor does not complete it within two minutes, or stopped,
the heartbeat, the next lease, the coordinator's wait or the
background sweep pause the run anyway.
Runs no executor is working on still pause at once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
While someone has a workspace open, the gateway asks the API for a 15-minute
write token for the project's platform repository on behalf of that person
(membership and role checked each time) and delivers it to the workspace
backend. The backend writes it to a Git config file outside the repository
(a memory volume in Kubernetes) that the clone includes, and on the first
delivery clones the target branch into a folder named after the project. The
workspace cannot mint credentials itself, so access ends with the last
session.
- People commit and push to the target branch like with any Git server; the
platform only accepts fast-forwards, and the next wish starts from that
commit (covered end to end in the local loop test).
- Commits are authored by whoever opened the latest session, from the name and
email in their sign-in; their own git config overrides it.
- Only the gateway can reach the delivery endpoint: it needs Theia's
connection token, and the gateway refuses the path for browsers.
- The provisioner pins the workspace to its repository and lets the pod reach
the Git service; the Kubernetes baseline admits that traffic. External
repositories are not cloned.
- The local shared Theia clones each project into its own folder.
- The Theia image installs Git, and its stage is named theia: the default
build target of that Dockerfile is the gateway.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Runs: a per-file diff of the latest checkpoint, verification evidence with each
command's exit code, duration and output tail (and failed installs), the last
failure that the repair round works on, and the integrated commit when a
project without delivery completes.
- Projects: repository status with a retry for platform repositories, the
project's lessons (list, add a convention, disable, delete) and runs filtered
on the server; IDE texts describe the Git hand-off instead of the removed
save barrier.
- Releases: the approval dialog shows the requirement, project, target
environment (production flagged), verification commands and approval deadline
from a new review endpoint; failed releases say why. Environments locked by a
deployment with an unknown outcome can be unlocked after a confirmation.
- Errors are titled by HTTP status; secondary text and focus rings meet the
contrast requirements; the mobile drawer leaves the tab order when closed and
closes on Esc.
- Sessions: the web BFF refreshes access tokens with the refresh token for up to
12 hours; IDE gateway sessions are renewed while in use (idle timeout 15 min,
at most 12 h) and rechecked by the granted user, so revocation still applies.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Entity carried `[key: string]: unknown`, so a misspelt field compiled and most
records were read as untyped bags. Every stored kind now has an interface in
contracts (workspace, runner task and registration, provider connection,
checkpoint record, resource allocation, integration lease, delivery config) and
the project, run, release and evidence types list all their fields. Entity writes
are generic over the record type, and the project delivery settings no longer
accept a stray target branch.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Storage: read-only queries use a read-only transaction without the tenant
lock, so event streams and dashboards no longer queue behind writers; lists
filter on indexed project, run and status fields and the run list pages with
limit/before. Dispatchers claim outbox items with SKIP LOCKED and a claim
deadline; delivered items and old idempotency records are pruned hourly.
- Migrations are versioned files recorded with checksums in schema_migrations;
002 adds the claim column and run index and migrates preview-stage runs and
free-text waiting reasons. Run events and usage are append-only for the app.
- Identities: static service tokens reach only their routes (coordinator: state,
wait, repair; deployer: lease, transition, releases); the static verifier
identity is gone; Git credentials go only to the lease holder; internal bodies
are validated; framework and body-parser errors use the API error envelope.
- Quotas: only queued or running runs (or ones with an unsettled model request)
hold token reservations; continuing a run reserves its remaining budget again.
- Recovery: owners can list and reconcile model requests with an unknown outcome,
and requests whose proxy died are marked unknown; definite deployment failures
free the environment, admins can unlock an environment after checking the
target, approvals expire with their release, and production approvals need a
second person. The builder's Docker context is operator configuration.
- MCP: list_projects, absolute console links, request_release resolves the run's
evidence and default environment, and tool changes are audited as the user.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Verification ran git inside the tree under test, kept no command output and
treated every infrastructure fault as a test failure; repairs went through an
executor lease the coordinator should not hold; and a project without delivery
could never succeed. This reworks the worker execution path and the control-plane
contracts it depends on.
- Verification exports the exact commit to a directory without .git, installs
dependencies (network allowed) and runs the protected commands under
bubblewrap in kata mode or directly in host mode; evidence records exit code,
duration, digest, a redacted output tail and the isolation used. Production
rejects host evidence. A failed installation waits as infrastructure.
- Waiting reasons are an enum with a redacted detail; dispatcher, GitHub and
model-proxy states map onto it, and the console explains each one with a way out.
- Repairs are requested by the coordinator through /internal/runs/:id/repair;
the control plane derives the failure summary from the verifier's evidence and
enforces the repair budget. Continuing after the budget is spent grants one more
round; a new requirement revision starts a fresh budget.
- Execution identities may only move a run within their own stages and only to
running or waiting; success comes from integration evidence (no delivery
configured) or deployment acceptance. The unused preview stage is gone.
- Integration fast-forwards when the target has not moved, merges and re-verifies
otherwise, retries when a push finds the target moved, and turns merge conflicts
into a repair round that merges the current target for the agent to resolve.
- Successful runs that needed a repair leave a project lesson; active lessons are
injected into later prompts, and admins can list, add, disable and delete them.
- Executor progress (messages, commands, file changes, plan updates) is stored as
normalized events; previously agent messages were recorded as the literal word
"output". Provider failures keep the work as a checkpoint and wait as
provider_error instead of failing the run.
- Workers declare WF_SANDBOX_MODE=host|kata (host refused in production),
heartbeat with retries until the lease could have expired, and retry safe
control-plane reads with backoff.
- tests/local-loop.test.ts runs the loop end to end with real Git, the in-process
control plane behind its internal routes and a scripted agent.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds prettier 3.9.8 (exact) with a shared config (single quotes,
120 columns, trailing commas), .prettierignore, .editorconfig and the
`format` / `format:check` scripts, then formats all TypeScript,
JavaScript, CSS, JSON and YAML sources.
Purely mechanical: no behaviour change. Typecheck passes, the vitest
suite and the 74 IDE node tests produce the same results as before
(socket-binding tests still cannot run inside this sandbox).
Previously the longest source line was ~3000 characters; reviewing the
following semantic changes now produces readable diffs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Imports the previously untracked working tree as-is so that the review
changes that follow (requirements -> design -> implementation) can be
reviewed as diffs and reverted if needed. No content changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>