off
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)
How it fires
How this command gets triggered: by you, by Claude, or both.
/restartContext preview
What this command does when you run it.
Restart the rolling-context proxy now (e.g. to pick up a plugin update the start hook deferred because other sessions were mid-request)
description: Restart the rolling-context proxy now (e.g. to pick up a plugin update the start hook deferred because other sessions were mid-request)
Run this command and show the user the log lines it prints, verbatim. Add no commentary beyond one short line if something looks wrong.
The start hook never downgrades a running proxy and never replaces one that has requests in flight from other sessions — it defers such upgrades. This forces the restart: it still waits up to ~6 seconds for in-flight requests to finish, then replaces whatever is serving with this plugin's version.
export ROLLING_CONTEXT_FORCE_RESTART=1; (powershell -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/hooks/start-proxy.ps1" 2>/dev/null || bash "${CLAUDE_PLUGIN_ROOT}/hooks/start-proxy.sh" 2>/dev/null); tail -n 6 "$HOME/.claude/rolling-context-hook.log"A 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
Turn rolling-context back on for this session (or --global for the whole machine) — active from the next request
Show whether rolling-context is on or off, and what the proxy has compressed so far