Understand how Qoder keeps long tasks within the model context window.
Long tasks can eventually exceed the amount of conversation, code, and tool output that a model can process at once. Qoder monitors context usage and can compact earlier content into a shorter working summary while preserving important decisions, constraints, file references, and progress.
The context window is the information the model can consider in one request. Messages, files read, and tool results gradually consume that window. In a supported task, the context control appears below the composer so that you can inspect usage and compact the task when enough context has accumulated. Compaction does not delete the task history; it prepares a denser summary for later requests.
Continue the current task when the objective and acceptance criteria are unchanged. Start a new task when the objective is unrelated or the existing assumptions would distract from the new work.
Context windows and compaction
The context window is the information the model can consider in one request. Messages, files read, and tool results gradually consume that window. In a supported task, the context control appears below the composer so that you can inspect usage and compact the task when enough context has accumulated. Compaction does not delete the task history; it prepares a denser summary for later requests.
Compact the current task
- Wait for the current Agent response to finish.
- Open the context-usage control below the composer and choose the compact action. You can also enter
/compactin the task composer. - Wait for the compact operation to complete, then continue in the same task.
What compaction changes
- Earlier detail is replaced by a denser summary.
- Recent messages and the current task state remain available.
- Minor details can be generalized or omitted, so compaction is not a substitute for storing requirements and durable project facts in files.
Continue or start a new task
Continue the current task when the objective and acceptance criteria are unchanged. Start a new task when the objective is unrelated or the existing assumptions would distract from the new work.
Before and after compaction
- Store durable requirements, API contracts, and acceptance criteria in project files instead of relying only on chat history.
- After compaction, verify Qoder's understanding of the objective and constraints and restate anything that was omitted.
- Start a separate task when the new work is unrelated to the current objective.
- After compaction, use the task monitor and recent messages to confirm that the current goal, files, and remaining work are still correct.
Compaction is lossy by design. It reduces repeated detail, but it cannot guarantee that every minor fact from an earlier message remains in the working summary.