Datasets:
File size: 2,929 Bytes
fe75e07 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 | # LibreOffice Writer computer app
Exported by REA's `export-desktop-application` from a capture of the `libreoffice-writer` package
(capture Evidence `ev_1a2f115d7f48e97d667aab935e3b22b50ada35105ac3d2188e4708e8ea86ab00`). It was checked against agentenv-framework
0.9.1431.
- `envs/libreoffice-writer/` is a computer app on the `ubuntu-24.04` base with the `reference` driver, for
`amd64` and `arm64`. It installs `libreoffice-writer` from the distribution archive, launches `sh -c exec 'libreoffice' '--writer' "$HOME"/'Documents/notice.odt'` at boot and is ready
when a window of class `libreoffice-writer` appears.
- Owned paths: `~/.config/libreoffice`, `~/Documents`.
`data/get` returns their files and a typed JSON view of each; `data/reset` restores the seed.
- Seed: 37 file(s) from the user's home before the capture, with the captured home path
respelled in text files.
- `tasks/smoke.json` deploys the app.
Run the task with `agent-env run <this folder>`, or only the deploy with `--task smoke`.
The seed is synthetic test data made for this showcase; it holds no one's real files.
## Task `move-delivery`
`tasks/move-delivery.json` deploys the app, has the agent work through the computer from the prompt below, and grades
the outcome with `artifacts/move-delivery-check/verify.py`, which reads the app's `data/get` views and needs
no model. `evals/libreoffice-writer.toml` names it, so a run of the bundle runs it.
> In the delivery notice open in LibreOffice Writer, move the delivery to Monday 24 November (same time, 8am to 10am) by changing the date under the title, then save the notice.
Checks, each of which must pass:
- `new-date`: `{"kind":"value_equals","file":"Documents/notice.odt","pointer":"/entries/[name=content.xml]/view/root/children/[name=office:body]/children/[name=office:text]/children/[name=text:p][@text:style-name=Subtitle]/children/0","value":"Delivery on Monday 24 November, 8am to 10am"}`
- `title-kept`: `{"kind":"value_equals","file":"Documents/notice.odt","pointer":"/entries/[name=content.xml]/view/root/children/[name=office:body]/children/[name=office:text]/children/[name=text:p][@text:style-name=Title]/children/0","value":"Delivery confirmation"}`
- `signature-kept`: `{"kind":"value_equals","file":"Documents/notice.odt","pointer":"/entries/[name=content.xml]/view/root/children/[name=office:body]/children/[name=office:text]/children/[name=text:p][@text:style-name=Signature]/children/0","value":"Jo Marsh, Orders, Corner Shop Ltd"}`
REA kept the task because its checks fail on the seed (`new-date`) and all
pass on the captured end state.
To measure a solve rate, run the task k times (3 by default) with the agent and model to measure, and count the runs
whose summary line says `passed`; a run that says `failed` did not finish and is run again rather than counted:
agent-env run <this folder> --task move-delivery --agent claude-code --model MODEL
|