memory-management

Prevent context overload by running a compact protocol that saves session state to dated memory files, checks session status, and switches models before compaction to preserve continuity and prevent data loss.

The best way to save session memory before spawning a sub-agent is to write work to dated memory files, schedule a one-shot check-back cron, and ensure the main session owns follow-ups to enforce async safety.

Session compaction works by running session_status checks, switching from sonnet to opus for safe compaction, and confirming readiness before and after the process to maintain conversation continuity without losing pending tasks.

Trigger automated actions for token limits at 75% context usage, while warning at 50%. Main sessions and sub-agents follow different threshold behaviors, with sub-agents enforcing fail-fast behavior near context limits.

Yes, you can schedule one-shot crons for check-backs before promising timed work or spawning sub-agents, ensuring the main session retains follow-up control and preventing runaway session state.

Sub-agents fail fast near context limits by design to prevent runaway session state. Save work to memory files and schedule check-back crons before spawning sub-agents to safely manage background tasks.