Clear Context & Context Conservation FAQs

Question 1

Does spawning a subagent use more tokens?

Accepted Answer

Spawning a subagent has a small overhead (approx. 20k tokens), but it provides a completely fresh 1M token window, making it the most effective way to handle extremely large tasks.

Question 2

How does this skill clear context without manual input?

Accepted Answer

It uses a subagent delegation pattern where the main agent saves its state and spawns a new subagent with a fresh context window to continue the work, effectively resetting the context without stopping the workflow.

Question 3

Does this work in unattended or dangerous mode?

Accepted Answer

Yes, the skill is designed to detect and propagate these execution modes so the continuation agent knows to proceed without asking for human confirmation if the parent was in an automated mode.

Question 4

Will I lose my progress when the context is cleared?

Accepted Answer

No, the skill specifically saves a comprehensive session state including active files, pending tasks, and key decisions to ensure a seamless handoff to the continuation agent.

Question 5

What is the recommended threshold for triggering an auto-clear?

Accepted Answer

The skill defines an emergency threshold at 80% context usage, though it begins planning optimizations at 40-50% usage to ensure there is enough overhead to complete the handoff.

Clear Context & Context Conservation

Características Principales

Casos de Uso

Clear Context & Context Conservation

Características Principales

Casos de Uso