What a builder gets from each coding agent (our tool server, our approval policy, resume, notes during a turn, a message longer than the command line) was spread over each adapter's arguments, environment and ACP session. cli_agents::grants now states it per adapter, takes resume and long messages from the adapter itself, and tests hold every row to what the adapter actually hands a builder; an adapter without a row fails them, and unchecked cells say NotYet with the gap in words.
A comment containing 4.5 could satisfy the mechanics check and claim that walk speed uses it, while an equivalent calculation without that literal could fail. The numeric-text match is gone: a readable mechanics sheet passes its readability check with a saved unknown for the unmeasured behavior and makes no claim about what the build uses. A check result another builder turn can't resolve no longer sends the builder to retry it; the builder states it as unverified instead, and the summary counts the comparisons that remain unverified.
A round of the builder's own checks now has a 30-minute limit, Pause is looked at before each check and stops a running build step, and every check is said as its own step ("Checking its work (2 of 4): …"), so a check that stalls names itself instead of holding the build for hours. The limit reaches the checks' own program runs, a step is refused before it starts once the round is past its limit or paused, a check that can't run is reported as not run with its reason, and a caught bug leaves the project at "Needs you" instead of "Checking". Real check rounds keep no limit. Addresses the stalls reported in #981 and #1198; a live Windows run is still to do.
Play, screenshots and self-tests start a Python project's one package with a __main__.py as python3 -m <name>, and a Maven or Gradle project's one runnable jar (its manifest names a Main-Class, read without loading the jar) with java -jar. Maven now builds with package, so the jar exists after our own build.
A builder in the API loop, which can't open pictures, is no longer sent to look at screenshots: every brief and check that pointed it at a picture tells it what to use instead (capture.json's layouts, the UI tree, or asking the person). Agent apps keep the picture wording.
Aider gets its task with --message and flags that stop it asking, updating, editing .gitignore or opening a page; a chat outside a build gets --dry-run. A run is refused before launch when no model or key is set up or an OpenRouter model has no OpenRouter key (#72), and Clean room is refused because Aider's reads can't be checked.
Supersedes #1061.
Co-authored-by: Hasnain <161151300+hasnain607@users.noreply.github.com>
Someone signed in with `grok login` can build with their installed `grok` through ACP, with our approver deciding permission requests. Clean room, deep chat and questions are refused before it starts, because Grok can't keep to them; only Grok's sessions send `"type": "stdio"`.
New Python, Go and .NET projects build and launch through one catalogue shared by the build check, the screenshot and Play; a window is found through the program's descendants, then by name.
A person's own project, edited in place with nothing to recreate, is checked by its own build and then its own tests, in any language a toolchain table knows (Rust, Node.js, Python, Go, .NET, Maven, Gradle, Make), instead of the checks made for a recreation (no --screenshot option, self-test or MECHANICS.md added to their code). A project with no tests, or one Craft Anything doesn't know how to build, isn't a failure and the note says so.
A project edited in place (Work on my project, or rebuild --existing edit) keeps the stack its own files use (an engine's project file, then Cargo.toml or package.json dependencies, then other project files), unless the request names another; a Godot folder no longer gets Unity from a request that reads as a game.
GitHub Copilot CLI can be a coding agent over ACP, with its models chosen through the shared agent model catalogue; options that could bypass the app's tool restrictions are refused, and agents share investigation findings safely.
Maki can be added as a coding agent: over ACP (maki acp, with the backend's model after it) or one message at a time with its own adapter (maki -p), which switches its writing tools off outside a build. R2.2.
Adds Simplified and Traditional Chinese UI catalogs, picks the UI language from the system when Language is System, makes prices and a few labels translatable, recognises Chinese words for games and websites in requests, and adds cargo xtask i18n-coverage and docs/localization.md.
A native, pure-Rust app that shows anyone how a piece of software works, with
evidence-backed answers, then helps them rebuild it. It ships a desktop app, a
CLI and an MCP server, all driven by one engine.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>