Skip to content

test(computer): load files into a multi env's computer as an environment named after it - #767

Merged
earakely-scale merged 4 commits into
mainfrom
wloo/load-artifact-computer
Nov 20, 2026
Merged

earakely-scale merged 4 commits into
mainfrom
wloo/load-artifact-computer

Conversation

@williamloo-scale

@williamloo-scale williamloo-scale commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Second PR of a stack that replaces osworld_initialize with native agent-env steps. #749 (computer_exec) is merged.

OSWorld's download setup puts files on the computer before the agent starts, at paths under the home (452 of the 458 files OSWorld's tasks download are under /home/user/; the other 6 are relative). On a multi env (computers beside websites, as CUA-gym tasks have), this needs no new step field. A multi env already sends an environment artifact to the child of its environment_name. When that name is one of its computers, the files are written at their paths under the computer's session user's home, through its driver's data/add, in the shape snapshot_computer_env exports.

So an imported task's download files are an environment artifact named after the task's computer, keyed by their paths under the home, loaded with a plain load_artifact on the multi env:

# artifacts/desk_files/artifact.toml, beside Desktop/a.csv and notes/b.txt
type = "environment"
environment_name = "desk"
{"id": "files", "type": "load_artifact", "env_id": "office", "artifact_id": "desk_files"}

With several computers, each gets its own environment artifact, by its name, in one environment universe.

What it does

  • E2E test tst/integration/computer/computer_files_test.py, run by agent-env run:
    • deploys a multi env of one ubuntu-24.04 computer with the reference driver;
    • loads an environment artifact named after that computer;
    • reads both files back from their paths under the home with computer_exec.
  • AGENTS.md says that on a multi env, an environment artifact named after one of its computers, or after an app of one, loads into that computer. It also says that computer_exec in the background exits 127 for a program that isn't there.

An earlier version of this PR added a computer field to load_artifact, with a load_files helper and computer_of. Review found that the multi env's existing routing by environment name already covers this, so those changes are gone. load_artifact, ComputerEnv and computer_exec are unchanged from main.

Testing

On an Ubuntu 24.04 VM (c6i.4xlarge):

  • tst/integration/computer/computer_files_test.py passes (115 s).
  • tst/unit/task_step, tst/unit/env/envs/test_multi_env_computers.py and tst/unit/env/envs/test_computer_env.py: 4,242 pass.
  • Two tests in test_mcp_cli_builder.py fail there, and fail the same way on main: the CLI they generate runs under the VM's system Python, which has no httpx.

The stack

  1. feat(task-steps): computer_exec, a command run inside a computer through its driver #749: computer_exec (merged).
  2. This PR: files into a multi env's computer.
  3. A task importer that emits these steps for a task's init_config instead of osworld_initialize. Its download setup becomes an environment artifact named after the task's computer.

The rubric-judge verifier (cua_verifier) is a separate stack.

🤖 Generated with Claude Code

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; no blocking issues were found.

Summary

The PR now adds an integration test for loading files into a multi-environment computer through an environment artifact named after that computer. Runtime code is unchanged from the base branch.

  • The computer-files example loads files into desk and reads them.

Reviews (6) · Last reviewed commit: "Load a multi env's computer's files as a..." · Reviewed by Greptile

williamloo-scale and others added 2 commits November 18, 2026 16:10
…ugh its driver

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…er by name

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@williamloo-scale
williamloo-scale force-pushed the wloo/load-artifact-computer branch from 80bce75 to 04e634f Compare November 19, 2026 00:11
@williamloo-scale williamloo-scale changed the title feat(task-steps): load_artifact loads files into a multi env's computer by name (FD-5492) feat(task-steps): load_artifact loads files into a multi env's computer by name Nov 19, 2026
@williamloo-scale

Copy link
Copy Markdown
Contributor Author

@greptileai review

Base automatically changed from wloo/computer-exec-step to main November 19, 2026 19:29
earakely-scale and others added 2 commits November 19, 2026 14:47
Resolve the conflicts with the squash-merged #749: main's computer_exec and AGENTS.md, with this
PR's computer_of split, computer_problem and its AGENTS.md text.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A multi env already loads an environment artifact named after one of its computers into that computer, its files at
their paths under the session user's home, so load_artifact needs no computer of its own. The end-to-end test loads
the download setup's files that way, with plain env_id; load_artifact, ComputerEnv and computer_exec are main's again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@earakely-scale earakely-scale changed the title feat(task-steps): load_artifact loads files into a multi env's computer by name test(computer): load files into a multi env's computer as an environment named after it Nov 19, 2026
@earakely-scale
earakely-scale merged commit 9b6d98c into main Nov 20, 2026
34 of 35 checks passed
@earakely-scale
earakely-scale deleted the wloo/load-artifact-computer branch November 20, 2026 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants