Skip to main content

Context management

Check context usage and its breakdown, compact earlier content when needed, and continue your task.

During a long task, you can check how much context is in use, see its breakdown, and compact earlier content when needed before continuing.

Context windows and compaction

The context window is the information capacity available to the model in one request. System prompts, tools, and Skill information use context alongside conversation messages. Usage can therefore be greater than zero even after only a few messages. Qoder monitors context usage and can turn earlier content into a shorter working summary when needed. Compaction does not delete the task history, but the summary used in later requests may omit details from earlier content.

View context usage

  1. Open a task that already has a conversation.
  2. Click the context-usage percentage below the message input to open the context window panel.
  3. Check the total usage at the top and the category percentages below it to understand the current context breakdown.
The panel can include the following categories. The entries shown depend on the current task:
CategoryWhat to check
System promptsContext usage associated with system prompts
System toolsContext usage associated with system tools
SkillsContext usage associated with Skills, with a count shown in parentheses
MessagesContext usage associated with task messages
OtherUsage associated with other context content
These values describe the estimated context breakdown. They are not a Credits bill or tool-call counts. The number beside Skills does not indicate how many Skills were invoked in the current turn. An entry shown as <1% still uses some context.

Compact the current task

To organize context for more work on the same task, you can compact it manually:
  1. Wait for the current Agent response to finish.
  2. Open the context-usage control below the message input and choose the compact action when the button is available. Alternatively, enter /compact in the task input and send it.
  3. Wait for compaction to finish, then send your next request in the same task.
Compaction takes a short time and consumes a small amount of Credits. Qoder can also compact automatically when more context space is needed. If the panel button is unavailable, check its explanation:
  • The context is too short to need compaction. Continue the task. You do not need to compact repeatedly just to lower the percentage.
  • The task is running. Wait for the current response to finish.
  • Compaction is already running. Wait for it to complete.
Some models or tasks may not provide a context-usage control. The button states above apply to the context panel.

What compaction changes

  • Earlier detail is organized into a shorter working summary for subsequent requests.
  • The task history remains available, and you can continue the conversation in the same task.
  • Important decisions, constraints, file references, and progress are preserved where possible, but details can be generalized or omitted.
Compaction is lossy. Store requirements, API contracts, and acceptance criteria that must remain exact in project files instead of relying only on a conversation summary.

Continue or start a new task

Continue the current task when its objective and acceptance criteria are unchanged, and compact when its context needs organizing. Start a new task when the work is unrelated or existing assumptions would interfere with it.

Before and after compaction

  • Before compaction, make sure key requirements and unfinished work are clearly recorded.
  • After compaction, ask Qoder to briefly restate the objective, constraints, and next step. Supply anything that is missing.
  • Check recent messages and the task monitor and recap to confirm relevant files and remaining work before continuing.