filesystem-context

To prevent agent context token overflow, you can offload oversized tool outputs and persistent context to a filesystem scratch pad, retrieving compact references instead of keeping the full data in memory.

The best way to persist long-horizon plans and agent memory across context refreshes is by storing them in a dedicated filesystem context, ensuring durable context survives session interruptions.

To share memory and coordinate workspaces among sub-agents, use a shared, isolated filesystem to store scratch pads, plans, and findings, allowing multiple sub-agents to access durable context.

You should offload large tool outputs to a filesystem scratch pad when your multi-turn agent workflows exceed the context window size and require retrieving compact references to manage token limits.

Filesystem context management requires optional directories such as scripts, references, and assets to support dynamic skill loading and store scratch, plans, and findings for durable context.