Edgar ArakelyanandClaude Opus 5.5
fc4c381dd7
* feat(desktop): keep an agentenv computer up and drive it through REA's MCP tools - A Python helper keeps one agentenv computer up per build with run_bundle(keep=True) and reports its address, MCP URL, control token and sandbox id; it tears the computer down when stdin closes. - AgentEnvComputer owns the helper, waits for readiness, holds one MCP session to the computer's computer_* tools, records through the computer-recording routes, and removes the sandbox's containers by label when agentenv cannot confirm teardown. The token never leaves it. - start_build_computer starts a computer from a request (archive package, apt repository or .deb, opened on demand with REA in /opt/rea) or from a bundle folder; act_on_build_computer forwards screenshot, click, drag, scroll, type, key and wait and returns the driver's images unchanged; close_build_computer tears it down. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(desktop): remove a build computer's container by name when agentenv cannot confirm teardown agentenv's local provider runs an ordinary computer as agent-<sandbox id> without the agentenv.sandbox label, so the label-only fallback found nothing and reported a running computer as removed. The fallback now lists containers by exact name and by label. The real test holds its recording open long enough for a first frame, checks the container by name, and runs rea inside the computer; the guide and tool descriptions say the app opens from the Applications menu and that a screenshot after opening a menu should come from a wait. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(desktop): own failed build-computer starts, keep ids past oversized screenshots, bound recordings - A start is owned from the helper's spawn. One that fails and whose teardown is unconfirmed stays held under a computer_id close can retry; closeAll refuses new starts, cancels and joins starts in progress, then closes every held computer. - When the first screenshot is too large, the error carries REA's result with the computer_id, and start_build_computer takes screenshot region, format and quality. - Recordings are refused before reading when the manifest's total exceeds the allowance, then fetched one segment at a time, each read bounded and checked against its size and sha256. - The helper keeps the tail of its output (a new tail retention mode in ProviderProcessSupervisor), so a build's own error is not crowded out. - A helper that reported no computer exits on its own before SIGTERM, so no phantom owner is kept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(desktop): bound a build computer's action log Every action kept its full arguments for the computer's whole life, so a long session grew REA's memory without limit. The log now keeps the latest 256 actions within 256 KiB, cuts each string to 1 KiB and each list to 64 items (naming what it cut), and keeps the total and the last applied index of each kind of action, so rules over the whole session hold after entries drop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
4.5 KiB
4.5 KiB
Verification
Run on 2026-11-05 on macOS 26.5 with Node v24.22.1 and Python 3.11. Docker and agentenv were not used by the gates or the boundary tests.
Tests
src/domain/desktop/appBuild.test.ts: the bundle for an archive package, an apt repository with its key and a.debwith a downloaded REA; the Node.js pin matches REA's; refused desktop entries, credentialed or non-http URLs and relative bundle paths.src/domain/desktop/computerActions.test.ts: key translation, argument pass-through and refusal of an argument the action does not take.tests/boundary/mcp/buildComputerMcp.test.ts, through the public MCP tools with REA's real helper, a fakeagent_envpackage onPYTHONPATHand a fake driver serving readiness,computer_*tools over streamable HTTP, recording anddata/get: start with readiness polling, the image pass-through, argument pass-through and key translation, a driver refusal, a refused argument, close and a later unknown id; a request bundle with REA's payload, compiled by the fake runner; the missing payload and runner settings; a runner failure with its output; removal by name and label; an unconfirmed teardown retried after Docker recovers; cancellation of a start stopping the helper; a long build's failure reported from the end of its output; a first screenshot too large for the response that keepscomputer_idfor act and close; the first screenshot's options. No result carries the control token.tests/boundary/providers/buildComputerRecording.test.ts: recording start, end and one fetch per segment under REA's request id, the action log, a long session's log kept within its allowance with every action counted and the driver still getting each argument whole, a segment that differs from its manifest, a recording over the allowance refused before any read, and an answer outgrowing its segment's size.src/application/desktop/DesktopBuildActionLog.test.ts: the log names only the arguments it cut, cuts text without splitting a character, and records the outcome of an action dropped while it was pending.tests/boundary/providers/buildComputerLifecycle.test.ts: shutdown cancels and joins a start in progress and refuses later starts; a failed start whose teardown is unconfirmed stays held under the id its error names, keeps its primary failure, and is released by a retried close and by shutdown.src/process/ProviderProcessOutput.test.ts: the supervisor's tail retention keeps each stream's latest bytes, reports checkpoints over dropped bytes as incomplete, and drops a UTF-8 character the cut would split.tests/boundary/providers/buildComputerReal.test.ts: opt-in withREA_BUILD_COMPUTER_REAL=1,REA_AGENT_ENV_COMMAND,REA_DOCKER_COMMANDandREA_BUILD_COMPUTER_REA_ARCHIVE; skipped here.
Checks against agentenv
python -m agentenv_protocol.computer._declarefrom agentenv-framework 0.9.1431 declared both a Mousepad archive bundle and a.debbundle with a downloaded REA: packages, downloads per architecture, both run scripts and the demand launch.install-rea.shran as root with the network off in a local Ubuntu 24.04 container against a Node.js-shaped and an REA-shaped archive: it unpacked both into/opt/rea, putnodeandreaonPATHand removed the archives.
Real computer
Run on 2026-11-05 on Ubuntu 24.04 amd64 with Docker, agentenv-framework
0.9.1431 and Node v24.22.1. REA's archive was packed from this tree with
npm pack, then npm ci --omit=dev --omit=optional in its rea-prod folder,
18.5 MB as .tar.xz.
tests/boundary/providers/buildComputerReal.test.tspassed in 25 s with the image built; the first run, which builds it, took 109 s.- Through
rea mcpover stdio:start_build_computerfrom the Mousepad request came up in 31 s with its first screenshot as a PNG. Mousepad opened from Applications, Other,mousepad; a typed line was saved withctrl+sthrough the Save As dialog; actions took 6 to 60 ms beside the driver's own typing and waits.rea --versionanswered 6.8.0 in the computer for its user and root.close_build_computertook 0.5 s withteardown: "agentenv"and left no container. The exported Inkscape bundle started cold in 59 s and closed the same way; a start cancelled at 60 s left nothing up. - With the helper killed, close removed the computer's container by its name,
agent-<sandbox id>: agentenv labels only its VM and closed-network containers. - No result or log held the control token.