video video 23.9 113 |
|---|
Osmo: a computer-use environment built from a one-line request
The real Osmo 0.4 personal organizer running on an Ubuntu 24.04 desktop, as an agentenv computer environment. An agent completes the task only through screenshots, mouse and keyboard, and a verifier grades the saved files with no model.
Claude Code built this environment from a one-line request in about 20 minutes, with only REA's build skill and MCP tools; How it was made has the request and the steps. Osmo starts on its calendar, with an address book of three synthetic contacts. The agent has to add a fourth, Delphine Moreau, with her cell phone and e-mail. There is no file to open and nothing to save: Osmo writes its contacts to ~/.local/share/osmo/contacts_records.xml after every change. It sees only the screen and acts only with the mouse and keyboard.
Watch
- Agent runs (Claude Code with Claude Sonnet 5.5): run 1, run 2, run 3
- Witness, which proves the task can be done through the computer: witness.mp4
Each video is the computer's own screen recording at 10 frames per second.
The task
In Osmo, add a new contact to my address book: Delphine Moreau, cell phone 555-0163, e-mail delphine.moreau@example.com.
bundle/artifacts/add-contact-check/verify.py reads the app's files through the computer's data/get view and passes only if every check holds:
| Check | Kind | File |
|---|---|---|
name |
text_contains |
.local/share/osmo/contacts_records.xml |
phone |
text_contains |
.local/share/osmo/contacts_records.xml |
email |
text_contains |
.local/share/osmo/contacts_records.xml |
kept |
text_contains |
.local/share/osmo/contacts_records.xml |
Osmo's contacts file is XML whose records have no attributes, so no selector can pick out one record. The checks read the whole address book's text with text_contains: it must hold "DelphineMoreau" (Osmo writes the first and last names next to each other), "555-0163" and "delphine.moreau@example.com", and must still hold Hannah Okafor's e-mail, so overwriting her contact instead of adding a new one fails. REA's draft suggested no checks for this file; Claude Code wrote these after reading the file in a throwaway export.
Results
3 of 3 runs passed, about $0.99 per run.
| Run | Outcome | Turns | Cost | Video |
|---|---|---|---|---|
| 1 | passed | 17 | $1.19 | video |
| 2 | passed | 17 | $0.96 | video |
| 3 | passed | 20 | $0.81 | video |
Run it
You need Docker. agentenv-framework builds the computer: Ubuntu 24.04 with the app installed from Ubuntu's archive (osmo 0.4.4).
pip install agentenv-framework==0.9.1431
hf download earakely-scale/OsmoFromRequestComputerEnv-REA --repo-type dataset --local-dir osmo-request
agent-env run osmo-request/bundle --task add-contact --agent claude-code --model <model>
The agent needs a model provider configured for agentenv. --task smoke only boots the computer, with no agent. bundle/README.md describes the bundle in detail.
How it was made
Claude Code built this environment from a one-line request, given only REA's build skill and REA's MCP tools:
Build me an Osmo environment where the agent adds a new contact to the address book.
It asked only the skill's upfront questions, wrote no app-specific scripts, and finished in about 20 minutes. The steps were REA's usual ones:
- Capture. REA launched Osmo on a Linux desktop and recorded its package, windows and opened files while the edit was made. It also recorded the app's state folders before and after.
- Export. REA turned the capture into an agentenv
computer_app. It installs the app, seeds the starting files, starts the app, and waits for its main window. It also serves typed views of the app's files for verifiers. - Task. The task's checks were validated against the capture: they fail on the starting state and pass on the captured end state.
- Witness. In a fresh computer, the contact was added through computer actions alone, and the checks were read at four stages. They held on the first try:
| Stage | Checks |
|---|---|
seed |
fail, as expected: the name, phone and e-mail are absent; the existing contact check passes |
after_edit |
pass |
near_miss |
fail, as expected: the new contact's phone was edited to 555-0136 |
after_reset |
fail, as expected: data/reset restored the seed and Osmo relaunched on it |
The agent runs came after the build: Claude Code with Claude Sonnet 5.5 (--model anthropic/claude-sonnet-5-5 --no-emulate, on an amd64 host) solved the task 3 times, each run recorded.
What's inside
bundle/ the agentenv bundle: envs/ (app module, seed files), tasks/, artifacts/ (verifier), evals/
media/ witness and agent-run recordings (MP4) with short GIF previews
results.json the runs above, with each check's result
Limits
- The checks read the address book as one run of text with no separators, so they cannot prove that the phone and e-mail belong to Delphine's record rather than another contact's. Only Hannah Okafor's contact is checked as kept, so overwriting one of the other two still passes.
- The prompt has no save step: Osmo saves after every change, a setting the seed keeps.
- The seed also holds Osmo's settings, an empty
lockfileand WebKit storage files, which the capture picked up. Osmo started cleanly in the witness and in every run. - The computer installs whatever
osmoUbuntu 24.04's archive holds at build time (0.4.4 for these runs); it is not pinned. - Three runs is a small sample: the solve rate shows the task is solvable, not how hard it is.
Licences
The bundle code, the task and the synthetic seed files are Apache-2.0. Osmo itself is not included: the computer installs it from Ubuntu's archive (osmo 0.4.4) at build time, under its own licence (GPL-2.0-or-later).
- Downloads last month
- 134
