Datasets:

earakely-scale
/

KMyMoneyFromRequestComputerEnv-REA

license: apache-2.0
pretty_name: KMyMoney computer-use environment from a one-line request (REA)
tags:
  - computer-use
  - cua
  - gui-agent
  - rl-environment
  - agentenv
  - desktop
  - linux
  - rea
  - personal-finance
  - accounting
  - budget
  - from-request

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

The real KMyMoney 5.1 personal finance manager 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 33 minutes, with only REA's build skill and MCP tools; How it was made has the request and the steps. KMyMoney opens a small synthetic household finance file, Documents/household.kmy, at launch, behind its Tip of the Day dialog: a Household Checking account at Maple Grove Credit Union, three payees and four transactions, among them an October 20 payment to Riverside Electric. The agent has to record a $87.45 payment to Riverside Electric from Household Checking, dated November 3, 2026, in the Utilities category, and save the file. 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
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 KMyMoney, record a payment of $87.45 to Riverside Electric from the Household Checking account, dated November 3, 2026, in the Utilities category, in my household finance file Documents/household.kmy, then save the file.

bundle/artifacts/record-electric-payment-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
`nov3-transaction`	`value_equals`	`Documents/household.kmy`
`amount-from-checking`	`value_equals`	`Documents/household.kmy`
`payee-riverside-electric`	`value_equals`	`Documents/household.kmy`
`utilities-category`	`value_equals`	`Documents/household.kmy`
`one-transaction-added`	`member_count`	`Documents/household.kmy`
`oct20-payment-date-kept`	`value_equals`	`Documents/household.kmy`
`oct20-payment-amount-kept`	`value_equals`	`Documents/household.kmy`

A .kmy file is gzip-compressed XML, and REA reads the XML inside. The checks find the new transaction by its posting date, 2026-11-03, and its two splits by account: the Household Checking split must be -1749/20 (KMyMoney writes amounts as fractions; -87.45) with the payee Riverside Electric, and the Utilities split 1749/20. The file must hold exactly five transactions, and the October 20 Riverside Electric payment must keep its date and amount. REA's draft suggested the date check and the count, and a check on the file's transaction counter, which Claude Code discarded; it had no checks on the new transaction's splits, so Claude Code wrote the amount, payee and category checks.

Results

2 of 2 runs passed, about $1.50 per run.

Run	Outcome	Turns	Cost	Video
1	passed	44	$1.67	video
2	passed	42	$1.33	video

Run it

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

pip install agentenv-framework==0.9.1431
hf download earakely-scale/KMyMoneyFromRequestComputerEnv-REA --repo-type dataset --local-dir kmymoney-request
agent-env run kmymoney-request/bundle --task record-electric-payment --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 KMyMoney environment where the agent records a payment in a small household finance file and saves it.

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

Capture. REA launched KMyMoney 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 payment was recorded through computer actions alone, and the checks were read at four stages. They held on the first try:

Stage	Checks
`seed`	fail, as expected: there is no November 3 transaction; the kept checks pass
`after_edit`	pass
`near_miss`	fail, as expected: the amount was changed to 87.54
`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 twice, 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

KMyMoney shows its Tip of the Day dialog at every boot, and the agent has to close it: the seed's settings don't turn it off.
Only two runs: the build stopped at its $4 solve budget before a third. Two runs show the task is solvable, not how hard it is.
Recording the payment takes many steps in KMyMoney's transaction form: the runs took 44 and 42 turns. Choosing Riverside Electric as the payee offers to copy its last payment, $92.10, so the amount has to be replaced, and its date field is split into month, day and year sections, so a date typed in one go can land wrong.
The checks find the transaction by its date and its splits by the seed's own account ids for Household Checking and Utilities, so a payment dated otherwise, or filed under a category the agent creates, fails.
The seed also carries Documents/household.kmy.1~, the backup copy KMyMoney keeps of an earlier save; the checks read only household.kmy.
The computer installs whatever kmymoney Ubuntu 24.04's archive holds at build time (5.1.3 for these runs); it is not pinned.

Licences

The bundle code, the task and the synthetic seed files are Apache-2.0. KMyMoney itself is not included: the computer installs it from Ubuntu's archive (kmymoney 5.1.3) at build time, under its own licence (GPL-2.0-or-later).