Repository navigation
Conversation
A command the hub runs in the sandbox said nothing until it ended, so the person watched a fixed phrase and a clock for up to two minutes at a time, and for the whole of the first workspace install. A command may now print "progress: <line>" on stderr; the sandbox relays each such line to a small file beside the workspace, out of the sandbox's reach, and removes the file when the command ends. The hub's activity read attaches the line to the run when the sidecar is on its own machine and the line is fresh, and the page shows it in place of its reading of the tool call. The workspace install, which prints nothing the hub can relay, is noted as "installing the app's packages" for its whole length. Lines meant for the person stay out of the command's output, and only commands the hub runs are asked for them.
check-app printed nothing until its checklist was complete, up to 100 s after it started. It now reports starting the app and each page it opens, with how many it has still to open, as progress lines the hub relays to the person; an agent running it itself sees no such lines.
![corbits-triage[bot]](https://avatars.githubusercontent.com/u/275831056?s=60&v=4){kind=small}
Contributor
Author
|
Continued, rebased onto main, with the triage findings fixed, in a replacement pull request from branch feat/command-progress-main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second of two changes toward showing what is happening at least every 10 seconds during long steps. Stacked on #66, since both change the sandbox command runner; its base should move to
mainonce #66 merges.What changed
packages/schemas/src/activity.ts:AgentActivitygains an optionalcommand({ line, at }), andCOMMAND_PROGRESS_FILEnames the file the sandbox and hub share.apps/hub/src/builds/posix-sandbox.ts: a command the hub runs may printprogress: <line>on stderr. The runner relays each such line (at most once a second) tocommand-progress.jsonbeside the workspace, outside the sandbox's reach, and removes it when the command ends. Those lines stay out of the command's output; the rest of stderr is still kept for a failure. Only commands the hub runs getSB_PROGRESS=1, so a command an agent runs itself prints no such lines into what the agent reads.apps/hub/src/builds/sidecar-tools.ts: the workspace install prints nothing the hub can relay, so it is noted as "installing the app's packages" for its whole length, up to the 115 s timeout.apps/hub/src/artifacts/service.ts: the activity read attaches the line to a run when its sidecar is on the hub's machine and the line is under five minutes old, so a command that died leaves nothing stale on screen.apps/web/src/pages/workspace/agent-activity.tsx: the live phrase shows the command's own line in place of the reading of the tool call that started it. Every surface that usesactivityPhrasepicks it up: the specialist's live line, the app pane during setup, and the activity strip.workflows/coder/check/check-app.ts: reports starting the app and each page it opens, with how many it has still to open.Why
A command the hub ran in the sandbox said nothing until it ended, so the person watched a fixed phrase and a clock for up to two minutes at a time, and for the whole of the first workspace install. On 2026-11-02 that read "Running a quick check 11m" and, during setup, nothing at all.
How it was verified
tsc --noEmit -p .and-p apps/webpass;oxlint --deny-warningsand Prettier pass on the changed files.bun --conditions=intx-src testpasses forapps/web/src/pages/workspace,apps/hub/src/buildsandapps/hub/src/artifacts(28 tests, 1 new).createPosixBuildExecutor: a probe command's two progress lines reached the file while a real stderr line stayed in its failure output; check-app on a filed design emitted 30 page lines, none of which appeared in its checklist; the file was gone after each command.