← All guides

Restart Claude Code Sessions at 200K Tokens (Save Up to 80%) (2026)

Every message in a Claude Code session resends the full conversation history as context. Past 200K tokens the marginal cost per message grows fast; past 300K you pay 10-15x for the same work.

Bleeding money on Claude Code or OpenClaw?

We apply the full cost checklist live and set up monitoring. See training and cost-audit options →

The fix: when your session crosses 200K tokens (ccusage shows this), stop, ask Claude to write a handoff doc (what is done, what is next, relevant file paths), run /new, paste the handoff, and continue. One developer documented an 80% monthly drop — $1,600 to $320 — from this single behavior change. Restart discipline is the highest-ROI habit on the whole cost list.

Why long sessions get expensive

Claude Code is stateless per call: each message resends the entire conversation so far as context. Early in a session that is cheap. But context grows monotonically, and past 200K tokens the per-message cost climbs sharply — a 300K+ session can cost 10-15x more than the same work split across fresh sessions. You are paying to re-read the whole history on every turn.

The restart pattern

  1. When ccusage shows your session crossing 200K, stop.
  2. Ask Claude to write a handoff doc: what is done, what is next, relevant file paths, and any open questions.
  3. Save it, run /new, paste the handoff, and continue where you left off.

The handoff takes about 30 seconds to produce and reloads only the context that matters, instead of dragging 300K tokens of history into every future message.

Automate the ceiling

You can also force summarization earlier in ~/.claude/settings.json:

{
  "compactThreshold": 200000,
  "autoCompact": true,
  "subagentModel": "claude-haiku-4-5"
}

compactThreshold: 200000 compacts context at 200K instead of the default 300K+, and subagentModel routes spawned sub-tasks to Haiku. Reports put this at a further 30-50% on top of the manual restart discipline.

OpenClaw users: the same settings.json applies to agents routed through the gateway. Keep OpenClaw sessions from ballooning by using /new between unrelated tasks and letting autoCompact cap the context.

Need help?

If your bill is bleeding and you would rather not tune this yourself, we apply the whole checklist and set up ccusage monitoring in one session. See training and cost-audit options →

Need OpenClaw fixed live?

Remote rescue sessions for gateway, auth, tunnel, VPS, and model access problems.

See Rescue Session

Read next

Caveman Mode for Claude Code: Cut Output Tokens 61-75% (2026)
Caveman Mode is a CLAUDE.md snippet that strips preambles, summaries, and filler to cut Claude Code output tokens 61-75% — about $100-140/month saved with no loss of code quality.
OpenClaw Costs: How I Went From $1,600/mo to $180/mo (10 Fixes That Actually Worked)
One developer was billed $1,800 in two days on a $200 plan. Another burned $5,600 of compute on a $100 Max subscription. Here are the 10 fixes, ranked by real savings, that cut bills by 70-90%.
5 OpenClaw Mistakes Costing You Money Right Now
Five OpenClaw settings silently drain your budget. The heartbeat alone costs $50-150/month. Fix all five in under 10 minutes.
OpenClaw Costs $600/Month? Here's How to Get It Under $20
Cut your OpenClaw API bill from $600/month to under $20. Seven config changes covering model routing, prompt caching, and context optimization.