earakely-scale/QElectroTechFromRequestComputerEnv-REA

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

The real QElectroTech 0.9 electrical diagram editor 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 29 minutes, with only REA's build skill and MCP tools; How it was made has the request and the steps. QElectroTech opens a small electrical diagram, Documents/motor-starter.qet, at launch: a pump starter with three components, a push button S1 (Start pump), a contactor coil K1 (Pump contactor) and a lamp H1 (Pump running). The agent has to change the coil's label to KM1 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, 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 QElectroTech, change the label of the contactor coil K1 in the diagram Documents/motor-starter.qet to KM1 and save it.

bundle/artifacts/rename-contactor-km1-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
coil-label-km1	text_equals	Documents/motor-starter.qet
coil-function-kept	text_equals	Documents/motor-starter.qet
three-components	member_count	Documents/motor-starter.qet

A .qet file is XML. The checks find the coil by its element uuid, the id QElectroTech gives each placed component, and read its elementInformation fields: label must be "KM1" exactly and function must still be "Pump contactor", and the diagram must still hold three components (member_count). All three checks came from REA's draft. Claude Code discarded one more suggestion, which read the label together with its field's name as "KM1label", and two guards on the coil's terminal markers.

Results

3 of 3 runs passed, about $0.78 per run.

Run	Outcome	Turns	Cost	Video
1	passed	15	$1.12	video
2	passed	14	$0.59	video
3	passed	15	$0.63	video

Run it

You need Docker. agentenv-framework builds the computer: Ubuntu 24.04 with the app installed from Ubuntu's archive (qelectrotech 0.9, with qelectrotech-data and libqt5sql5-sqlite).

pip install agentenv-framework==0.9.1431
hf download earakely-scale/QElectroTechFromRequestComputerEnv-REA --repo-type dataset --local-dir qelectrotech-request
agent-env run qelectrotech-request/bundle --task rename-contactor-km1 --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 QElectroTech environment where the agent changes a component's label in a small electrical diagram and saves it.

It asked only the skill's upfront questions, wrote no app-specific scripts, and finished in about 29 minutes. The steps were REA's usual ones:

1. Capture. REA launched QElectroTech 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 edit was made 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 coil is labelled K1; the kept checks pass
after_edit	pass
near_miss	fail, as expected: the label was typed as KM2
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 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 coil is found by its uuid, so a new coil placed instead of K1 gets another uuid and fails. The other two components' labels, S1 and H1, are not checked.
• The bundle installs qelectrotech-data, QElectroTech's element library, and libqt5sql5-sqlite, the Qt SQLite driver its element cache uses, beside the app as extra packages.
• The seed also holds QElectroTech's element cache (~/.qet/elements_cache.sqlite) and its log for the day of the capture (~/.qet/20261106.log), which the capture picked up.
• The computer installs whatever qelectrotech Ubuntu 24.04's archive holds at build time (0.9 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. QElectroTech itself is not included: the computer installs it from Ubuntu's archive (qelectrotech 0.9, with qelectrotech-data and libqt5sql5-sqlite) at build time, under its own licence (GPL-2.0-or-later).