AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 23, 2026, 13:00 JST

Claude Code v2.1.299 auto-summarizes idle chats over 200,000 tokens

Send on LINE
Claude Code v2.1.299 auto-summarizes idle chats over 200,000 tokens

3 Key Points

  1. What happened

    v2.1.299 summarizes conversations over 200,000 tokens after roughly 54 minutes idle, about six minutes before the one-hour prompt cache lapses; the setting is idleCompaction.

  2. Why it matters

    The summary replaces a full re-read of the conversation when the user returns, which the piece presents as a lighter first message after an absence.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The three releases span v2.1.299 through v2.1.301, published October 14–15, 2026 UTC, and the release notes add up to 329 items, with 190 in v2.1.299, 88 in v2.1.300, and 51 in v2.1.301. The idle summarization is the headline change, but the same version also alters what becomes invisible after a summary: skills can drop out of Claude's view and be restored with /reload-skills, and subagent names assigned before the last summary must be addressed by agent ID. A second summary trigger appears in v2.1.301 when switching to a smaller-context model, where the outgoing model summarizes the overflow first, and that summary may consume usage credits unless the version's fix applies.

The permission changes sit alongside the summarization work. In v2.1.299, rm commands assembled inside scripts Claude Code cannot read are no longer confirmed by default, and MCP permission rules no longer let mcp__a cover a__b or a_. v2.1.301 also fixes WorktreeCreate hooks that deleted a hook-created worktree at exit without confirmation even when unpushed commits might exist.

The piece's reading is that Claude Code is shifting management of conversation length and cache lifetime from the user to the tool itself. That reading rests on the idle summary in v2.1.299, the cache-write measurement by lifetime in v2.1.300, and the model-switch summary in v2.1.301; it would be falsified if the next three releases add nothing on summarization or caching. For context, the piece compared trigger settings as of October 17, 2026: Codex uses a token threshold via model_auto_compact_token_limit, and Aider uses a history token cap via --max-chat-history-tokens; neither setting list showed an idle-time trigger, while Gemini CLI was unconfirmed.

FAQ
How do I turn off the idle summarization?
Set idleCompaction to false in settings.json. You can also change the token floor with the environment variable CLAUDE_CODE_IDLE_COMPACT_MIN_TOKENS; both require v2.1.290 or later.
How can I check whether the summary actually happened?
Use the OpenTelemetry api_request event added in v2.1.300, which splits cache writes into cache_creation_5m_tokens and cache_creation_1h_tokens; if the one-hour figure is small on the first message back, the summary worked.
What changes with rm confirmation?
In v2.1.299, rm commands built inside scripts Claude Code cannot read are no longer confirmed by default. Set CLAUDE_CODE_STRICT_INLINE_SHELL_RM_PROMPT=1 to restore the confirmation.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAgentic AI Foundation adds four projects, hits 10 total