| # Zim Desktop Wiki computer app |
|
|
| Exported by REA's `export-desktop-application` from a capture of the `zim` package |
| (capture Evidence `ev_d45c7017d2d25004cdb8f6d7204b4581a11cc51e2b2146b77fab7d34a724532e`). It was checked against agentenv-framework |
| 0.9.1431. |
|
|
| - `envs/zim/` is a computer app on the `ubuntu-24.04` base with the `reference` driver, for |
| `amd64` and `arm64`. It installs `zim` from the distribution archive, launches `sh -c cd "$HOME" 2>/dev/null; exec 'zim'` at boot and is ready |
| when a window of class `Zim` appears. |
| - The app opens no document at launch, since the seed holds 2 documents (~/Notebooks/Notes/Meeting_Notes.txt, ~/Notebooks/Notes/notebook.zim) and the app opens one only when it holds exactly one. |
| - Owned paths: `~/.config/zim`, `~/Notebooks/Notes`. |
| `data/get` returns their files and a typed JSON view of each; `data/reset` restores the seed. |
| - Seed: 4 file(s) made for the task, as saved at checkpoint `seed`. |
| Text files and dconf keys spell the capture host's name as `localhost`, `user@host` as `user@localhost` |
| and the home as `/home/user`, which the computer respells to its own at boot. |
| - `tasks/smoke.json` deploys the app. |
| |
| Run the task with `agent-env run <this folder>`, or only the deploy with `--task smoke`. |
| |
| The seed was made for this task, not taken from a user's own data; read `envs/zim/seed/` before publishing the bundle. |
| |
| ## Task `add-action-item` |
| |
| `tasks/add-action-item.json` deploys the app, has the agent work through the computer from the prompt below, and grades |
| the outcome with `artifacts/add-action-item-check/verify.py`, which reads the app's `data/get` views and needs |
| no model. `evals/zim.toml` names it, so a run of the bundle runs it. |
| |
| > In my Zim notebook, add a new action item to the Meeting Notes page: "Dana to update the release checklist". Add it as an unchecked checkbox in the Action items list, like the others there, and save the page. |
| |
| Checks, each of which must pass: |
| |
| - `dana-item`: `{"kind":"lines_present","file":"Notebooks/Notes/Meeting_Notes.txt","lines":["[ ] Dana to update the release checklist"]}` |
| - `dana-once`: `{"kind":"line_count","file":"Notebooks/Notes/Meeting_Notes.txt","contains":"Dana to update the release checklist","equals":1}` |
| - `other-items-kept`: `{"kind":"lines_present","file":"Notebooks/Notes/Meeting_Notes.txt","lines":["[ ] Priya to send the revised budget","[ ] Marco to book a room for the offsite"]}` |
| |
| REA kept the task because its checks fail on the seed (`dana-item`, `dana-once`) 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 add-action-item --agent claude-code --model MODEL |
| |
