Working in threads
Context & Compact
How full the provider's context is, what Compact does, and when a fresh session beats compacting.
Three different numbers get called "usage", and confusing them is how people end up surprised. Synergoi keeps them apart:
- Context — how full the model's working memory is right now, for this session. This page.
- Thread usage — the tokens this conversation has spent in total. It only ever goes up, and it is not what fills the context.
- Quota — how much of your subscription window is gone. See Quotas, caps & failover.
The context meter
The composer shows the active provider's last reported context occupancy. Open it for used against capacity, and when that reading was taken — a measurement, not an estimate. At 90% of the reported capacity it warns you.
If a provider does not report usage or capacity, the meter says unknown and stays there. An unknown occupancy is never drawn as zero, and a cumulative token count is never substituted for it. The measurement resets when the session does: a new leg, an effective model change, or a provider-reported session restart.
Which providers report it: Claude and Codex have context gauges in the installed adapters. Grok and Cursor show one when the live session advertises it. Antigravity's current bridge does not report context at all. Local models depend on the OpenCode harness and the commands it advertises.
Compact
Compact asks the provider to summarize its own working context, using that provider's real /compact command. It is available when the session advertises the command, the composer is empty, and nothing is queued or running — Synergoi will not slip a compaction in beside your work.
Compaction costs tokens and loses detail; that is the trade. Your transcript in Synergoi is untouched either way — Compact changes what the model is holding, never what you can read.
Codex reports when compaction starts and finishes, so you get a definite answer. Claude's adapter reports gauges rather than a completion signal, so a large drop is labelled compaction inferred, and a command that ends without confirmation is labelled unconfirmed. Neither is dressed up as certainty.
Compact, Clear, or a fresh session
| Action | What it does | When |
|---|---|---|
| Compact | The provider summarizes its own context. Costs tokens, loses detail. | Mid-task and you want to keep going. |
| Clear | The provider's own /clear, where advertised. Reset semantics are the vendor's, and your transcript stays. | Starting something unrelated in the same chat. |
| Fresh session or handoff | A new provider-native session, carrying a Context Pack — the original ask, what changed, what was decided, what is left. | Switching model or provider, or the context is simply spent. |
Provider slash commands must be enabled for Compact and Clear to appear; that switch is in Settings › Providers.
Something wrong or missing on this page? Email [email protected].