earakely-scale/PaperlessNgxEnv-REA

paperless

paperless

An AgentEnv bundle with its recorded runs, published with agentenv-hf.

Tables

• paperless_tasks: one row per task of the bundle, with its prompt, envs, verifiers and steps.
• paperless_episodes: one row per recorded run, with its status, model, reward and scores, the prompt and response, and the agent's transcript as chat messages when its trajectory format is one agentenv-hf reads.

raw/paperless.jsonl holds each run's record and native trajectory, and bundles/paperless/ the bundle itself.

Run it

pip install agentenv-framework huggingface_hub
hf download earakely-scale/PaperlessNgxEnv-REA --repo-type dataset --local-dir agentenv-dataset
agent-env run agentenv-dataset/bundles/paperless

Paperless-ngx on AgentEnv, from a REA capture

What this is. An environment of Paperless-ngx 2.20 (GPL-3.0), built from one recorded browser session against a self-hosted instance seeded with synthetic data. REA projected the capture into an environment manifest (41 tools) and an environment state, the entities the capture's reads showed, and rea environment-export wrote the bundle you can run from this dataset. Reads the state can render are answered from it, write tools whose effect the capture confirmed change it, and data/reset restores it. Nothing executes Paperless-ngx. Tasks are graded deterministically, with no judge.

v0.2.0 rebuilds this environment from the same capture with a REA build that serves a state, confirmed writes and list queries; the tag v0.1.0 keeps the earlier replay-only version.

What's in it

• 41 tools (35 GET, 3 POST, 2 DELETE, 1 PATCH) over 108 recorded exchanges on http://127.0.0.1:3213; no recorded group excluded. 36 are offered; the other 5 are write tools the environment cannot apply (post_documents_selection_data, delete_documents_notes_by_id, post_documents_notes_by_id, post_tags, patch_tags_by_id), left out rather than faked.
• Path parameters: 21 numeric. REA's four format rules (numeric, uuid, hex, iso-date) applied unconditionally; the four opt-in rules (after-uid-literal, opaque-token, sibling-variance, prefix-variance) were requested and are labelled per parameter. With the four format rules alone the manifest has 41 tools.
• State: 33 entities of 13 types. 22 read tools answer from it and 13 replay their recorded responses. 2 list tools also answer filters, search, sorting or paging from it. Served write tools: delete_tags_by_id (delete).
• Unknowns the manifest states explicitly: authorization model, response semantics beyond recorded exchanges, state transitions between tools.
• 12 retrieval tasks (evals/paperless-retrieval.toml): each asks one factual question about a seeded object, with a distinct answer that the app does not ship by default; reward 1 if the response contains the recorded value, else 0. Plus smoke, which deploys the environment and checks it through the MCP endpoint.
• 24 retrieval episodes, plus the smoke run, by openai/gpt-oss-120b:groq, zai-org/GLM-5.3-Flash:zai-org through the Hugging Face router, with their chat transcripts.
• Provenance: capture ev_8d7f7da6eb5cdd44da2be33be1860bd2d2d5d881ea2fe57e8d366307b1e39f43 (scoped HAR sha256 ab61f99d59b8a29032dadcf0aa5f682e94509e9fad91fe38506c5f822438884b, 203,943 bytes), manifest view ev_06a09dc06047cae98bd9503a8a72e59d65491f21a648dac5f5744f03956f1c4e, confidence inferred, authority historical-reference. The REA build is rea-agents 6.7.0 from main 335c042d with open pull requests merged: morluto/rea#5600 at fe8ab584 (which carries #5351 and #5352), #5664 at 03b66df9, #5787 at edc09dba, #5800 at 6db41d29 and #5699 at ac3ca8a3. The bundle installs it from the tarball it ships, so the environment runs without waiting for an npm release.

What the state means, and does not

Reads the state can render, item, list and document views of the entities the capture's responses showed, answer from it. List reads filtered, searched, sorted or paged answer from it too wherever the capture's recorded calls explain what each query parameter does, including values no call recorded; a parameter the recordings do not explain, or a flag's unrecorded value, replays. Other reads replay the recorded response whose path and query values best match the arguments, with replay.exact_match saying whether it matched exactly; a replayed read does not change after a write. A served write was confirmed by the capture itself: replaying the session against the extracted state, a later recorded read reproduced its effect and none contradicted it. A create generates ids and clock values deterministically, so the same calls after a reset give the same state; an update changes the members the call sends; a delete removes the entity. Each takes only the body members the recorded call showed and refuses others with a message that names the accepted ones. Its effect shows in the reads the state renders, lists included wherever a list lists its whole collection or a learned query answers the call; a list call nothing explains keeps its recorded members, dropping a deleted entity but not adding a new one. The data plane at /agentenv takes data/reset (restore the extracted state), data/add and data/get (return it), which is how write tasks are graded.

Not modelled: side effects a write has beyond its own entity (counters, copies in other collections, related entities), preconditions the application enforces before a write, list query parameters the recorded calls do not explain, paging members such as page counts and next links when a call asks for another page size or page, and anything the capture never showed. The manifest's unknowns list what a capture cannot establish.

Tasks and grading

Retrieval

task	tool	arguments	field	answer
qa-01-get_documents_notes_by_id	get_documents_notes_by_id	id=1	[0].note	Rui Castellanos re-measured the seaward stack; cart number 7 is retired.
qa-02-get_documents_metadata_by_id	get_documents_metadata_by_id	id=1	media_filename	ledger/2026/Granite Ledger Quarterly Stone Count.txt
qa-03-get_documents_by_id	get_documents_by_id	id=1, full_perms=true	title	Granite Ledger Quarterly Stone Count
qa-04-get_storage_paths_by_id	get_storage_paths_by_id	id=1	slug	lighthouse-rota-archive
qa-05-get_workflows_by_id	get_workflows_by_id	id=1	name	Route Granite Ledger Scans
qa-06-get_mail_accounts_by_id	get_mail_accounts_by_id	id=1	username	intake@saltmarsh-depot.example.test
qa-07-get_users_by_id	get_users_by_id	id=4	email	ada.finch@example.test
qa-08-get_mail_rules_by_id	get_mail_rules_by_id	id=1	name	Lamp Oil Delivery Notes
qa-09-get_document_types_by_id	get_document_types_by_id	id=1	slug	stone-count-report
qa-10-get_tags_by_id	get_tags_by_id	id=1	name	Inbox Triage
qa-11-get_groups_by_id	get_groups_by_id	id=1	name	Quarry Auditors
qa-12-get_saved_views_by_id	get_saved_views_by_id	id=1	name	Granite Ledger Audits

Episodes

model	retrieval episodes	passed	pass rate	mean tool calls	mean input tokens
openai/gpt-oss-120b:groq	12	12	100%	1.0	16,306
zai-org/GLM-5.3-Flash:zai-org	12	12	100%	1.0	19,022

Every episode is in the episodes config with its transcript; scores are the deterministic verifier scores.

Every recorded episode passed.

Run it yourself

uv tool install agentenv-framework --with 'agentenv-hf @ git+https://github.com/earakely-scale/agentenv-hf-plugin@v0.3.0'
agent-env hf run earakely-scale/PaperlessNgxEnv-REA --bundle paperless --task smoke          # Docker, no model
agent-env hf run earakely-scale/PaperlessNgxEnv-REA --bundle paperless --eval paperless-retrieval --model openai/gpt-oss-120b:groq

The evals need a model endpoint: set [model] base_url and api_key in .agentenv/config.toml (the Hugging Face router works with any hf_ token). The bundle's agents/replay-qa is a small OpenAI-compatible tool-calling agent; any A2A agent can replace it.

How it was made

1. Paperless-ngx ran in Docker on a throwaway VM, bound to loopback, seeded through its own API with synthetic records (4 correspondents (Granite Ledger Quarry Office, Blue Heron Kitchen, Copperfield Annex Lettings, Saltmarsh Depot Stores), 5 tags (Inbox Triage, Tide Tables, Lamp Oil, Audit Seaward Stack, Winter Rota), 3 document types, 2 storage paths, 3 custom fields, 5 plain-text documents with custom-field values, 3 notes, 2 saved views, 2 groups, 2 users (ada.finch, tomas.vey), 1 IMAP mail account (never polled), 1 mail rule, 1 workflow and the application title Saltmarsh Depot Archive); people and projects are invented.
2. Playwright drove a login, the main pages and a scripted read, write, read sequence through the app's JSON API; the HAR was scoped to the API, the login exchange dropped, secret-looking body fields scrubbed, headers and cookies removed.
3. rea inspect-web-network-capture retained the exchanges as Evidence; rea inspect-analysis-view projected the environment-manifest view; rea environment-export wrote this bundle and the state it serves; gen_tasks.py derived the retrieval tasks from the manifest and the recorded bodies; agent-env run recorded the episodes; agent-env hf publish wrote this dataset. Scripts: https://github.com/earakely-scale/rea-environments.

Compared with PortSimEnv on AgentEnv

	PortSimEnv-AgentEnv	Paperless-ngx (this dataset)
Environment	A simulation: a container quay, ships, cranes, weather, with A2A ship agents	An application's API rebuilt from one captured session
Observation	Tool results computed by the simulator as the week unfolds	Answers rendered from the extracted state, or recorded responses, cited to Evidence
Action space	Planning tools (check_plan, confirm_berths, advance, message_agent)	36 tools mirroring the application's endpoints
State	Full: a virtual clock, triggers, frozen windows, agents that answer	A state extracted from the capture (33 entities); served writes change it; data/reset restores it
Reward	Deterministic, against a CP-SAT optimum or a re-planner anchor; continuous 0 to 1	Deterministic: recorded-value match for retrieval; 0 or 1 per task
What it measures	Planning under uncertainty and negotiation	Tool discovery, parameter inference and faithful retrieval in a real API, and changing its state
Data provenance	Real 2024 port calls and weather; simulated workloads	Synthetic seed data on a self-hosted Paperless-ngx; nothing real
How it was built	Hand-written plugin, months of work	Generated from a capture in one scripted pass
Where it is strong	Long-horizon decisions with hard rewards	Breadth: any app you can capture becomes an environment

The two are complementary: PortSimEnv shows what a hand-built simulation can grade; this dataset shows how far a capture alone gets you, and the manifest's unknowns and the state's limits above say what it still leaves out.

Licence and credits

Bundle code and tasks: Apache-2.0. Recorded content: responses generated by a self-hosted Paperless-ngx instance over synthetic data; Paperless-ngx is GPL-3.0 software by the Paperless-ngx contributors and is not redistributed here beyond the recorded JSON responses. REA is MIT software by morluto; AgentEnv Framework is Apache-2.0 by Scale AI.