DOX gives coding agents local context through AGENTS.md

Agent Zero released DOX, a minimalist framework for hierarchical AGENTS.md files. It does not add a new runtime. It gives coding agents a simple discipline: read local rules before editing and update them after meaningful changes.

DOX puts context in the directories where the agent works

Agent Zero presents DOX as a set of instructions around AGENTS.md files. The root document describes the project and points to local documents in specific parts of the repository. The agent is not supposed to follow one global note. It follows a path of rules from the root to the directory it is about to edit.

DOX is not a package, CLI or server. The setup is deliberately plain: copy the instructions into the root AGENTS.md and let the agent create or maintain child documents. That simplicity is the point. Context lives next to the code it governs, not in an external wiki the agent may ignore.

Local rules solve what a global prompt cannot carry

Coding agents are getting better, but large repositories expose an old limit. Frontend, backend, data pipelines and deploy scripts often have different tests, safety boundaries and approval rules. One root prompt quickly turns those differences into grey paste.

DOX pushes the agent toward the behavior of a careful senior engineer: first learn where you are, which local rules apply and what must not break, then touch the files. In a monorepo with 5 teams, that boring discipline matters more than another polished demo.

The Markdown contract works only if the agent maintains it

The weak spot is the same as with all documentation: it can go stale. If the agent does not update rules after a change, or if humans keep layering contradictory notes, DOX becomes another layer of noise. The workflow depends on deleting old guidance as much as adding new guidance.

Tool support matters too. DOX is useful when the agent actually reads AGENTS.md, follows the path to the target files and can run a documentation pass after the change. Without that, it is just nice Markdown sitting in the repository.

Real repositories will decide whether this becomes a habit

The signal to watch is not the GitHub star count. It is whether teams start writing local agent rules as naturally as they write test instructions or service READMEs.

If DOX sticks, it will not feel like a product. It will feel like a small guardrail for agentic coding: cheap, boring and most visible at the moment it stops the agent from touching the wrong place.

Lilith's verdict

DOX looks almost comically small: just a Markdown contract inside the repository. That is why it may work. An agent that knows which room it is standing in breaks less furniture.