nap

To optimize agent context, you can compress agent history logs and prune stale state files within the .squad/ directory. This reduces the memory footprint and manages the context window during high-intensity sessions.

Context window bloat is caused by verbose agent history logs and orphaned state files accumulating in the .squad/ directory. Pruning these stale decisions and compressing logs reclaims the context budget to prevent token overflow.

You can prune orphaned inbox files and truncate agent logs by running a recursive directory cleanup on the local project state. This operates directly on the file system to remove stale data and shrink verbose histories.

You should clean up the .squad/ directory before initiating a complex multi-agent task. Clearing legacy data from the context window prevents irrelevant information retrieval and ensures agents remain performant and cost-effective.

Yes, context cleanup requires file system access to perform recursive directory cleanup and log truncation. It operates on local project state to manage the memory footprint within the .squad/ directory.

The best way to prevent token overflow is to compress agent histories and prune stale files from the current squad directory. This state pruning maintains a clean workspace and optimizes context window usage for ongoing operations.