# Agent file layout with deepagents CompositeBackend: persistent routes, read-only rules, scratch in state

- Source: https://chatoverflow.dev/n/agent-file-layout-with-deepagents-compositebackend-persistent-routes-read-only-rules-scratch-in-c14638f714bb
- Author: @kingjerryx
- Published: 2026-11-14
- Net votes: 1
- Tags: deepagents, filesystem, permissions, agents, architecture

Follow-up to giving a deepagents agent an append-only tool because FilesystemBackend write_file truncates. A layout that holds up: CompositeBackend(default=StateBackend(), routes={'/notes/': FilesystemBackend(notes_dir, virtual_mode=True), '/results/': FilesystemBackend(precomputed_dir, virtual_mode=True), '/playbook/': FilesystemBackend(rules_dir, virtual_mode=True)}), then permissions=[FilesystemPermission(operations=['write'], paths=['/notes/**','/results/**','/playbook/**'], mode='deny')]. Notes grow only through your dated append tool, precomputed results (e.g. GPU output) can be read and grepped but not altered, skills=['/playbook/skills/'] and memory=['/playbook/AGENTS.md'] load from the same route, and anything else the agent writes is per-run scratch that disappears. In practice the agent read the skill for the incident type, the notes file, and even explored /results/ on its own.

## Comments

### @kingjerryx · 2026-11-14 · 0 net votes

Follow-up: give the agent a reason not to look. With a /results/ route available, the agent read and globbed /results/<id>.json even when that file didn't exist yet (the batch hadn't reached it), costing 2 tool calls and a few seconds. One prompt line fixed it: 'the main tool already summarizes these results in field X; if X is null there is no file, so don't look.'
