README.md

metadata

license: apache-2.0
pretty_name: VYM computer-use environment from a one-line request (REA)
tags:
  - computer-use
  - cua
  - gui-agent
  - rl-environment
  - agentenv
  - desktop
  - linux
  - rea
  - mind-map
  - planning
  - from-request

VYM: a computer-use environment built from a one-line request

The real VYM 2.6 mind-mapping app 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 28 minutes, with only REA's build skill and MCP tools; How it was made has the request and the steps. VYM opens a small mind map, Documents/team-offsite.vym, at launch: Team Offsite in the middle, with Venue (Lakeside Lodge), Agenda (Kickoff talk, Strategy workshop) and Catering (Vegetarian lunch). The agent has to add a branch called Sunset boat tour under Agenda and save. 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
• 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 VYM, add a branch called Sunset boat tour under Agenda in my Team Offsite mind map (Documents/team-offsite.vym) and save it.

bundle/artifacts/add-boat-tour-branch-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
new-branch	text_equals	Documents/team-offsite.vym
agenda-has-three	member_count	Documents/team-offsite.vym
guard-1	text_equals	Documents/team-offsite.vym
guard-2	text_equals	Documents/team-offsite.vym

A .vym file is a zip holding map.xml, and REA reads the entry inside. Branches are branch elements. The checks find Agenda by its heading ([>heading=Agenda]) and the new branch under it by its heading too: it must read "Sunset boat tour" exactly, Agenda must now hold three branches (member_count), and Kickoff talk and Strategy workshop must keep their headings, found by the ids VYM keeps for them in the seed. REA's draft named the new branch by the id VYM generated for it in the capture, which no other run would reproduce; Claude Code switched that to its heading, kept the count and the two guards, and discarded three suggestions on the saved selection, a view setting and a branch counter VYM rewrites on every save.

Results

1 of 1 runs passed, about $2.76 per run.

Run	Outcome	Turns	Cost	Video
1	passed	92	$2.76	video

Run it

You need Docker. agentenv-framework builds the computer: Ubuntu 24.04 with the app installed from Ubuntu's archive (vym 2.6.11).

pip install agentenv-framework==0.9.1431
hf download earakely-scale/VYMFromRequestComputerEnv-REA --repo-type dataset --local-dir vym-request
agent-env run vym-request/bundle --task add-boat-tour-branch --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 a VYM environment where the agent adds a branch to a small mind map and saves it.

It asked only the skill's upfront questions, wrote no app-specific scripts, and finished in about 28 minutes.

Claude Code abandoned its first capture after about 6 minutes and captured again. The steps were REA's usual ones:

1. Capture. REA launched VYM 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.
2. 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.
3. Task. The task's checks were validated against the capture: they fail on the starting state and pass on the captured end state.
4. Witness. In a fresh computer, the branch 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: Agenda has two branches and no Sunset boat tour
after_edit	pass
near_miss	fail, as expected: the branch was renamed "Sunset boat tuor"
after_reset	fail, as expected: data/reset restored the seed

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 once, 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

• Only one agent run: runs 2 and 3 were skipped to keep the solve spend within the build's budget. One run shows the task is solvable, not how hard it is.
• That run took 92 turns. VYM adds a new branch under whichever branch is selected, and the agent added branches in the wrong places and reopened the map to undo them several times before adding it under Agenda from the branch's right-click menu.
• The new branch must be a direct child of Agenda named exactly Sunset boat tour, and Agenda must end with three branches. Venue, Catering and their branches are not checked.
• Debian's copyright file for vym is in an old free-form layout: it gives the program's licence as the GNU GPL version 2, with no "or later", and the Debian packaging as GPL-1.0-or-later.
• The computer installs whatever vym Ubuntu 24.04's archive holds at build time (2.6.11 for these runs); it is not pinned.

Licences

The bundle code, the task and the synthetic seed files are Apache-2.0. VYM itself is not included: the computer installs it from Ubuntu's archive (vym 2.6.11) at build time, under its own licence (GPL-2.0, as Debian's copyright file gives it).