Skip to content AI News: Claude Code now warns you before an old conversation eats your usage limit →
AI News · Oct 20, 2026 · Claude Code

Claude Code now warns you before an old conversation eats your usage limit

Claude Code 2.1.304 came out on October 19. For people on a Pro or Max plan the most useful change is a warning before you resume an old conversation that would use a noticeable part of your 5-hour limit. The release also adds a guided setup for auto mode and fixes a worktree exit that could delete commits, and an update three days earlier says the standalone Claude Design closes by December 14.

WhatClaude Code releases 2.1.302 and 2.1.304
WhoClaude Code users on any plan
Get itclaude update, or restart the app
Try it2 prompts
Claude Code now warns you before an old conversation eats your usage limit

What happened

Anthropic published Claude Code 2.1.304 on October 19, 2026, the fifth release in six days. Most of its 76 change log lines are fixes, but a few change how the tool behaves day to day, and one line in version 2.1.302 from October 16 matters to anyone who uses Claude Design. Run claude update in the terminal to get it.

What's new

  • A warning before a costly resume. On Pro and Max plans, resuming a conversation you left a while ago reads its history again, and on a long thread that can take a visible bite out of your 5-hour usage limit. Claude Code now warns you when that share would be noticeable and offers two choices: resume anyway, or start a new conversation, where Claude can look up the old one if you refer to it.
  • /auto-mode-setup. A guided setup that reads your project and recent sessions to teach auto mode, the mode that approves safe actions on its own, about your environment. It now also works with Amazon Bedrock, Google Vertex AI, Microsoft Foundry, the Claude apps gateway and sessions with telemetry off.
  • A safety prompt for mounted drives. rm -r of a whole mounted drive or a folder at its top level, such as /Volumes, /media or WSL's /mnt/c, now gets the same confirmation that deleting /Applications already did.
  • A worktree fix that protects commits. Exiting a session started with claude --worktree could remove the worktree and its branch without asking when HEAD was detached or on another branch, which could lose commits. It now asks.
  • Clearer limits. /usage now says when a rate limit on usage data ends instead of "try again in a moment".
  • For teams. Code Review gets three review levels, Quick, Standard (the default) and Deep, set for the organization or per repository, and an option to review every repository in a GitHub organization, including ones added later.

Also in 2.1.302: idle compaction and Claude Design

Version 2.1.302 added an Idle compaction row to /config, so you can turn off the compaction Claude Code runs on a conversation left idle, and the notice after an idle compaction now says how to turn it off. The same release added a notice to /design-sync and /design-login that the standalone Claude Design at claude.ai/design closes by December 14, 2026. The change log does not say what replaces it, so if you keep design work there, export what you need before then.

What it means for you

  1. Take the warning seriously on long threads. A fresh conversation with a two-line summary of where you were often costs far less than reloading hours of history. The first prompt below writes that summary for you.
  2. Run /auto-mode-setup once per project. Auto mode judges each action by what it knows about your setup, so tell it once instead of correcting it session after session.
  3. Update if you use worktrees. The exit bug could delete a branch with unpushed commits. Until you update, push work branches before leaving a worktree session.
  4. Turn off idle compaction if it surprised you. It is now one row in /config.

Our Claude Code cheat sheet lists the commands, and the Claude Code prompts are written for sessions that stay short.

Try it

Hand off a long session to a new one
We're going to continue this work in a new conversation to save context. Write the handoff note I'll paste there:
- Goal: what we're building, in one line.
- Done: what is finished and verified, with file paths.
- In progress: what is half done and the exact next step.
- Decisions: choices we made and why, one line each.
- Don't repeat: approaches we tried that failed.
Under 20 lines. No code unless a line of it is the next step.
Check a worktree before you leave it
Before I exit this worktree session, check that nothing is lost:
1) run git status and git log --oneline @{upstream}.. (or say there's no upstream),
2) list uncommitted changes and unpushed commits,
3) tell me the branch name and whether HEAD is detached.
If anything is unpushed or uncommitted, stop and ask me whether to commit and push it. Don't delete anything.

Sources

Weekly

New prompts in your inbox

One email a week: the best new prompts and one short guide. Confirm by email and get the free Prompt Cheat Sheet (PDF). Unsubscribe any time. Privacy policy