Grok Build now tells Dozer what it's doing
Grok Build 1.0.52 reports when it's working, waiting for you or done, and Dozer Sandbox 0.35 shows it in the dashboard, as it does for Claude Code and pi.
Grok Build 1.0.52 reports its status, and Dozer Sandbox 0.35 runs that version. Start a Grok Build sandbox and leave it to work; the dashboard shows when it's busy, when it needs you, and when it's finished.
doz try grokWhat you see#
While Grok Build works, its tab says working, and a dot beside the sandbox in the sidebar says something is going on.
When it stops to ask you something, such as permission to run a command, a notice at the top of the dashboard says so, with an Open button that takes you straight to the session, whichever page you're on.
When it finishes, the tab says done. All sessions shows the same on every tile, so with several agents running you can see which one is still busy and which is waiting for you.
Where it comes from#
xAI's changelog for 1.0.52 lists "support for OSC 7501". That's a terminal escape sequence for program status, proposed by Mitchell Hashimoto: a program asks the terminal whether it understands the sequence, and if it does, reports its state each time it changes.
Inside every sandbox, Dozer answers that question for each session and keeps the latest report, whether or not the dashboard is open. Nothing is read from the screen or guessed: Dozer shows exactly what Grok Build reports.
Agents that report their status#
Claude Code, pi and now Grok Build report their status. So do Factory Droid and Docker Agent, which also arrive in 0.35. When another tool adds support, Dozer turns it on in that tool's recipe once we've seen it work.
Upgrade to 0.35, then doz try grok.