Context Usage Warnings
The two optional in-chat notes that appear when a session's context window is filling up — one at 75% as a heads-up, one at 90% as a warning that the conversation is about to be compacted. Covers how to switch them on, where the on/off controls sit in the chat itself, and why a warning never repeats until a real compaction re-arms it.
On this page
What it is
Context warnings are automatic in-chat alerts that tell you when a session's context window is filling up. Two thresholds exist: 75% (a heads-up that context is getting full) and 90% (compaction is imminent — the session will compact its conversation history soon to free space). Each warning appears as a persistent amber-colored divider line in the chat with a triangle-warning icon and a message like "Context is 85% full (170k / 200k tokens)." The figure in that line is the session's real fullness at the moment the warning fired, not the threshold that triggered it — see How it works. The warnings stay in the chat permanently — they don't disappear when you scroll, and they survive app restarts. After compaction resets the context window, the warnings can fire again on the next ramp-up.
To keep the warnings from becoming noise, two suppression rules apply. First, each threshold fires at most once per fill-up — the warning does not repeat just because the session restarts or switches accounts after a rate limit; it only re-arms after a real compaction frees space. Second, while the agent is deliberately parked waiting on a background task (you'll see an "agent appears to be waiting" note in the chat), the context warning is suppressed entirely — a waiting agent isn't running the turn that would overflow, so the alert would just be a false alarm.
Both thresholds are OFF by default — an automatic nag on every long chat is something you opt into, not something Omniscio imposes. Turn either on in Settings → Sessions → Waiting & Auto-Flow → Advanced session settings → "Warn at 75% context full" / "Warn at 90% context full" (the pair sits in the When sessions stall: more group inside that fold). Once a warning is showing, you can also flip both switches right from the message: a small ⋯ options button sits at the end of the warning line (you can also right-click the warning), opening a popover that explains in plain English what the warning means. Changes save instantly. Turning a warning off only stops future notes — the message already in the chat stays.
The default is off for new installs. If you have been using Omniscio for a while and your saved settings already have these warnings on, they stay on until you turn them off — the change deliberately doesn't reach in and flip a setting you already have. The same is true of the separate session handoff note.
Where to find it
The warnings appear inline in a session's chat, as an amber divider line partway down the conversation — that is where you read them, and the small options button at the end of that line (or a right-click on it) is where you switch them on or off again. The switches themselves live in Settings → Sessions, on the Waiting & Auto-Flow tab under Advanced session settings, and on mobile the options button is the only route since there is no right-click.
How it behaves
How to use it
- Turn a warning on (they ship off). Open Settings → Sessions, open the Waiting & Auto-Flow tab, expand Advanced session settings, and use the toggles "Warn at 75% context full" and "Warn at 90% context full". Once a warning is showing in a chat you have a second, quicker route: click the ⋯ options button at the end of the warning line — or right-click the message — and flip the switches in the popover that appears (it also explains what the warning means). On mobile, use the ⋯ button (there is no right-click). Settings is the route that always works, since with the warnings off there is no warning row to click.
- Watch for amber warnings in the chat. While a session is actively running, Omniscio checks the session's context usage at the end of each turn (in the default mode). When the threshold is crossed, an amber divider line appears inline in the conversation.
- Take action if you see a 90% warning. The session will compact automatically soon. If you want to preserve the current conversation state, consider using the session's compaction summary (click the "Compaction N" row in the chat after it appears — see compaction-summary.md) or copying important context before compaction happens.
- After compaction, the warnings re-arm. If the session fills up again, they fire once more at the same thresholds. A rate-limit account-switch or app restart does not re-fire a warning on its own — only a real compaction re-arms it — so a busy session that resumes repeatedly won't keep repeating the same "100% full" line.
How it works
Omniscio measures how full the context window is at the end of each turn — in the default mode there is no background timer. Two checks feed it. The first is free and runs every turn: an estimate of fullness taken from numbers the session already holds. The second is exact — it asks the session itself for the real figure — and Omniscio only pays for it when something will actually show the result: one of the two warnings is on, or the context indicator is on. With both warnings off and the indicator off, that exact check never runs.
Both numbers feed the same two rules, applied before anything is written into the chat:
- Nothing while the agent is waiting. If the session is parked on a background task (you'll see an "agent appears to be waiting" note), no context warning is posted — a parked agent is not running the turn that would fill the window, so the row would be a false alarm.
- Once per fill-up. Each warning fires at most once per fill-up. That "once" is remembered per session, not per running process, which is why a rate-limit account switch or an app restart does not repeat the warning; only a real compaction, which lowers the context, arms it again.
The percentage in a warning is what the session was actually at when the check ran, not the threshold. With the 75% warning on, a row can read "Context is 85% full (170k / 200k tokens)." — the session had crossed 75%, and 85% was where it stood when Omniscio looked. The 90% warning reads the same way.
Because both warnings ship off, a default install has no consumer for the exact check at all — so unless you turn on a warning or the context indicator, that check simply never happens. A small free speed-up, and nothing is lost: the automatic recovery for a session that runs out of room keys off the compaction itself, not off this percentage.
While "Keep my computer smooth under load" is on (its default), the exact check is also skipped for any session whose free estimate is comfortably below the warning band (under 60%), unless the context indicator is on — so running many sessions at once does not pile up one extra check per session per turn. No warning is missed: the free estimate is checked every turn regardless, and any session in the band gets the exact figure at every turn-complete; only a session below 60% can be working from a slightly older number, and there is no threshold down there to cross. If fullness is unknown the check runs (it fails open). Turning the switch off restores the older behavior: a 90-second background poll plus an exact check at the end of every turn, for every running session. See Keep my computer smooth under load.
A warning appears as an amber divider line in the chat, and that line carries the in-message control: a small ⋯ options button after the timestamp, or a right-click on the row, opens a popover with a plain-English explanation of the warning plus its two switches. (On mobile, use the ⋯ button — there is no right-click.) The control is always reachable because a warning always renders as its own standalone row rather than being folded into the surrounding conversation.
Related
The master toggle that decides whether this check runs at all — and that keeps many sessions from each launching a helper process — is on the Keep my computer smooth under load page. What you see after the window fills and the conversation is compacted is described on Compaction Summary, and the separate, token-measured note that offers to carry work into a fresh session is Session handoff. How the chat handles new rows like these appearing while you are scrolled elsewhere is on Session scroll position.
- Keep my computer smooth under load — the
smoothLoadEnabledmaster toggle that gates this check (turn-complete-only, fullness-gated, skipped when no warning/indicator will show it) so many concurrent sessions don't each launch a/contexthelper - Compaction Summary — the expandable summary card that appears after compaction completes, showing what was in the context before it was compacted
- Session handoff — a separate, absolute-token note (sized per model — 0.75 × the model's context window by default, e.g. 750,000 tokens on a 1M model, 150,000 on a 200k one) offering to carry the work into a fresh session. It is not a third threshold on this feature: these two warnings stay percentage-based and unchanged, while the handoff note is measured in tokens because quality degradation tracks context length, not window fullness
- Session scroll position — how Omniscio handles scroll position when new messages (including warnings) appear
Last verified 2026-10-23