Claude Code 2.1.290–2.1.291: what changed (WebSearch refill, WebFetch offset, Chrome settings lock)

Since the 2.1.273–2.1.278 fiche, the Claude Code CHANGELOG has moved up to 2.1.291. Here's what matters for operators. In 2.1.290, the interactive WebSearch budget refills at 100 calls/hour instead of stopping at 200, and WebFetch now says how much text it didn't read past 100,000 characters and takes an offset. Project settings can no longer turn on Claude in Chrome or set CLAUDE_CODE_DISABLE_ATTACHMENTS, and in-process teammates' agent_id now means something different. 2.1.291 fixes two regressions. This is a short catch-up, not a full rundown.

2.1.291: take this if you're on 2.1.290

Both bullets are fixes:

Fixed a regression in 2.1.290 where cloud sessions could drop answers to permission prompts Fixed a regression in 2.1.288 where the last messages of a session could be lost when quitting

If you run cloud sessions, or you quit sessions on anything from 2.1.288 up, upgrade to ≥ 2.1.291.

2.1.290: WebSearch refill + WebFetch offset

Changed the interactive session's WebSearch budget to refill over time (100 calls/hour; CLAUDE_CODE_WEB_SEARCH_REFILLS_PER_HOUR sets the rate, 0 turns it off) instead of ending after 200 calls

The fixed 200-call ceiling from 2.1.212 has become a budget that refills. One caveat: on our 2026-10-06 check, the env-vars and tools-reference pages still described the old 200-per-session cap (CLAUDE_CODE_MAX_WEB_SEARCHES_PER_SESSION). Our Spec on changing the WebSearch limit covers the refill variable and that docs gap.

Fixed WebFetch silently dropping page text past 100,000 characters; it now says how much was unread and takes an offset to read on

Long pages used to get cut off without any notice. Now Claude is told what it missed and can read the rest. That's a separate thing from switching WebFetch off, which is its own Spec.

2.1.290: Chrome + attachments project-settings lock

Changed Claude in Chrome so that a project's settings files can no longer turn it on; use --chrome, /chrome or your user settings

Changed CLAUDE_CODE_DISABLE_ATTACHMENTS so a repository's .claude/settings.json or .claude/settings.local.json can no longer set it; shell, user and managed settings still can

Same idea in both: a repository you clone can't change these for you anymore. If your team turned on Chrome or turned off attachments from a checked-in settings file, move that to user settings, or to managed settings for org-wide policy. For the extension itself, see Claude for Chrome. Related Chrome fixes in 2.1.290: /chrome → "Reconnect extension" now restores browser tools, and a browser_batch call gets 90 seconds instead of 60.

2.1.290: teammate agent_id

Changed an in-process teammate's agent_id in Agent results to its agent ID (its name@team address stays in teammate_id); TeammateIdle hooks no longer fire from its subagents or forks

If your hooks or scripts parse Agent results and expected name@team in agent_id, read teammate_id instead. Background: Agent Teams vs subagents.

One-liners from 2.1.290: claude attach <name> and claude logs <name> accept part of a session name. /claude-api managed-agents-onboard sets up Managed Agents files. Bash now asks before running pyright, which no longer counts as read-only. The rest of the long fix list stays in the CHANGELOG.

Upgrade readout

For the September standouts (server-side auto classifier, AGENTS.md, claude.ai sync), see the 2.1.273–2.1.278 fiche. We don't repeat them here.

Sources (checked 2026-10-06, 08:06 CEST)

• Claude Code CHANGELOG.md (raw): 2.1.290–2.1.291 bullets, plus the 2.1.212 origin of the 200 cap. The CHANGELOG doesn't date versions, so release days are [GAP]
• Docs-lag line only: env-vars · tools reference
• Live prior: /guides/claude-code-2-1-273-278-2026-09-19