File System Access
What enables persistent state and files as shared memory between agents.
In one sentence
The agent’s ability to read and write files. It is what enables persistent state, work on real projects, and the pattern of using files as shared memory between iterations and agents.
Before
State only in session memory
What it does
Reads and writes files
After
Persistent and shared state
Example
The agent writes progresso.md with what it has already converted, duvidas.md with what needs a human, and the cartas/ folder with the output. In the next iteration, it reads the same files. This way, two agents and five sessions can work on the same thing without stepping on each other.
In practice
- Define the naming convention before granting access. Without it, two agents will step on each other.
- The agent writes to a working folder, never directly to the final destination.
- The progress file is shared state: whoever writes it, writes the whole thing.
How to make it tangible
A working folder with read and write permission, plus a file naming convention.
Connects with
Translated from Portuguese with AI assistance.