off
Turn rolling-context off for this session (or --global for the whole machine) — full history goes upstream uncompressed, no restart needed
Turn rolling-context back on for this session (or --global for the whole machine) — active from the next request
How it fires
How this command gets triggered: by you, by Claude, or both.
/onContext preview
What this command does when you run it.
Turn rolling-context back on for this session (or --global for the whole machine) — active from the next request
description: Turn rolling-context back on for this session (or --global for the whole machine) — active from the next request
Run this command and show the user its output verbatim, EXCEPT the `<<rolling-context:...>>` marker line, which is machinery — do not repeat it back, quote it, or explain it. Add no commentary beyond one short line if something looks wrong.
With no arguments this turns compression back on for the current conversation only. If the user asked to turn it back on everywhere rather than just here, append `--global`.
Arguments given by the user: $ARGUMENTS
python "${CLAUDE_PLUGIN_ROOT}/proxy/switch.py" on $ARGUMENTSA transparent proxy that gives Claude Code rolling context compression — old messages get automatically summarized while recent messages stay fully verbatim. You never hit the context wall, and you never lose important details. Zero config.
Repo: NodeNestor/claude-rolling-context
Turn rolling-context off for this session (or --global for the whole machine) — full history goes upstream uncompressed, no restart needed
Restart the rolling-context proxy now (e.g. to pick up a plugin update the start hook deferred because other sessions were mid-request)
Show whether rolling-context is on or off, and what the proxy has compressed so far