Claude Code 2.1.198 Makes Claude in Chrome Generally Available, Lets Background Agents Commit, Push, and Open Draft PRs, Adds `/dataviz` Skill, and Brings Claude Platform on AWS to the Gateway

Claude Code 2.1.198 Makes Claude in Chrome Generally Available, Lets Background Agents Commit, Push, and Open Draft PRs, Adds `/dataviz` Skill, and Brings Claude Platform on AWS to the Gateway

lschvn

Claude Code v2.1.198 shipped on 2026-07-01T20:45:36Z, one day after v2.1.197 made Sonnet 5 the default model. The release makes Claude in Chrome generally available, lets background agents commit/push/open a draft pull request when they finish code work in a worktree, adds a /dataviz skill for chart and dashboard design, and brings Claude Platform on AWS to the Gateway. The release follows a week of Claude Code activity that started with the v2.1.195 background-agent reliability pass and continued through the v2.1.196 org-default model and MCP trust fix and the v2.1.197 Sonnet 5 default. v2.1.198 is the broadest of the four: it is a feature release that lands end-to-end automation, a GA browser-side assistant, a new Gateway upstream, and a quality-of-output upgrade for the Explore subagent, alongside the usual bug-fix tail.

The Sonnet 5 launch was the bigger individual event this week, and the Claude Code Sonnet 5 default piece covered the v2.1.197 model swap and the cyber safeguards in detail. v2.1.198 is the release that builds the product around Sonnet 5: the GA Chrome experience, the background-agent workflow that runs while the developer is away, the /dataviz skill for the dashboards that the agent now ships, and the Gateway upstream that lets the same session run on Claude Platform on AWS.

Claude in Chrome is now GA inside Claude Code

The headline change is the general availability of Claude in Chrome. The product has been in research preview since August 2025 and was gated behind a feature flag, a waitlist, and the beta-feature warnings on the Claude for Chrome page. v2.1.198 takes the gates off inside Claude Code: the same install path that worked for the beta is now the stable path, the in-product permissions gate is honored across concurrent CLI sessions (closing a regression where the gate was off for second-session CLI), and the tab-group isolation default is preserved. The release keeps the same beta-feature warnings on the Claude for Chrome marketing page because the page documents the standalone Chrome extension; the in-Claude Code integration is what moves to GA.

For Claude Code users, the practical change is that the agent that drives the terminal can now drive a Chrome tab without leaving the session. A user can ask Claude Code to fill a form, click through a multi-page flow, or extract structured data from a page, and the agent handles the browser side the same way it handles the terminal side. The permission model is the same as the beta: tab-group isolation by default, an explicit in-product permission prompt for sensitive actions, and the same browser-context risk warnings. The release does not introduce a new permission tier; it just removes the gates that made the feature inaccessible by default.

Background agents now ship the diff

The biggest product change in v2.1.198 is end-to-end automation for background agents launched from claude agents. Before this release, a background agent that finished code work in a worktree stopped to ask whether to commit, push, or open a pull request. The v2.1.198 release flips the default: the agent commits the changes to its worktree branch, pushes the branch, and opens a draft pull request on the upstream repository. The new Notification hook surface exposes two events for external tools to subscribe to: agent_needs_input (fired when the agent blocks on a question) and agent_completed (fired when the agent finishes, successfully or otherwise). The hook events are the integration point for dashboards, chat pings, and follow-up agents; the auto-PR flow is the integration point for the developer's working repo.

The same release also hardens the background-agent reliability surface. v2.1.198 fixes a regression where background tasks in web, desktop, and VS Code task panels got stuck on Running after they finished or after the session was resumed; a bug where background agents repeatedly showed Reconnecting… every 52 seconds on macOS while the agents view was open; and a deadlock where claude --bg silently created an unattachable session when combined with --print / -p (the conflicting flags are now rejected up front). Agent teams get a fix where a teammate that dies on an API error now reports failed to the lead, and messaging a stuck teammate wakes it to retry immediately. The release also cleans up a leaked worktree registration: locked .git/worktrees/ entries from killed agents are now removed automatically.

/dataviz skill, Gateway on AWS, Explore agent upgrade

Three smaller but practical additions round out the release. The new /dataviz skill gives Claude Code design guidance for charts and dashboards and ships with a runnable color-palette validator. The skill loads on demand when a session is asked to produce a chart or a dashboard and applies the same accessibility, contrast, and color-encoding rules that Anthropic uses internally; the validator accepts a proposed palette and reports whether it clears the contrast and color-blindness thresholds the skill encodes. The skill is additive and lives next to the other built-in skills like /init and /review.

The Claude Code Gateway now accepts Claude Platform on AWS as an upstream provider, exposed under the anthropicAws identifier. Model-not-found responses from one upstream advance the failover chain to the next, so a session that points at multiple providers (for example, Claude Platform on AWS in production and Bedrock in staging) falls through to a working provider when the requested model is unavailable on the first one. The release also fixes a dead-end where Claude Platform on AWS and Mantle sessions landed on 'Please run /login' when the STS token expired: awsAuthRefresh now runs automatically. Remote Control stays disabled when ANTHROPIC_BASE_URL points at a non-Anthropic host, matching the existing behavior under CLAUDE_CODE_USE_BEDROCK / _VERTEX / _FOUNDRY.

The built-in Explore agent, which is the subagent that Claude Code launches for read-only file exploration, now inherits the main session's model (capped at Opus) instead of running on Haiku. The change is a quality-of-output improvement: a Sonnet 5 main session that delegates a codebase-wide exploration to the Explore subagent now gets a Sonnet 5 answer instead of a Haiku answer. The Opus cap is a cost guardrail so a session that picked Opus as the main model does not silently cascade into an Opus-powered Explore pass on every sub-call. Subagents and context compaction also now inherit the parent session's extended thinking configuration, so the delegation does not lose the effort level the main session picked.

Smaller fixes worth flagging

The v2.1.198 release notes close a long tail of small fixes. Brief network drops mid-response (ECONNRESET) now retry with backoff instead of aborting the turn. Excessive background classifier requests when sandboxed processes repeatedly accessed the same network host are fixed. The /diff panel now refreshes when the user switches branches or commits outside the session. Markdown tables no longer overflow and wrap their right border when rendered in fullscreen mode. The /desktop command no longer fails with Cannot determine working directory after entering and exiting a worktree. The workflow progress view no longer drops the earliest agents from the list while the phase counter stays correct in SDK and desktop-app sessions. .claude/rules/ conditional rules now load when the target file is reached via a symlinked path. Plan mode now auto-allows read-only tool calls when a session starts in plan mode. The /branch default fork name is now derived from the first real prompt instead of the compaction summary. Syntax highlighting accuracy in code blocks, diffs, and file previews improves by upgrading to highlight.js 11. Keyboard shortcut hints now show opt/cmd instead of alt/super when connected from a Mac over SSH. The API retry UX shows the error reason after the second attempt and replaces the spinner tip with a status-page link when the API is overloaded. /login now opens the sign-in dialog from the claude agents view instead of saying it is not available. Subagents now treat messages from the agent that launched them as normal task direction; an agent's message is still never treated as the user's approval.

Why this matters for Claude Code users

The v2.1.198 release is the second of two consecutive Claude Code releases that ship Sonnet 5 as the new default. v2.1.197 was the model swap; v2.1.198 is the product that runs on top of the swap. The GA Chrome experience, the background-agent auto-PR workflow, the /dataviz skill, and the Gateway anthropicAws upstream are the four changes that a working Claude Code user notices on a Tuesday morning after claude update. The reliability tail (network-drop retry, STS auto-refresh, worktree registration cleanup, hook events for external tools) is what a team running Claude Code in CI or against a fleet of repos notices over the next month. Both land in the same release, and the release is the broadest feature Claude Code has shipped since the v2.1.196 org-default model and MCP trust fix the day before v2.1.197.

The release also pulls Claude Code closer to a "set it and forget it" workflow for tasks that take longer than a single session. A team that delegates a refactor to a background agent now gets a draft PR in their inbox instead of a stop-to-ask prompt. A team that wants to track background agents across multiple repositories can wire the new Notification hook events into a dashboard. A team that runs Claude Code against a Chrome tab now has the GA version of the feature instead of a research preview. The release is the first one in 2026 where the headline changes are about delegation and integration rather than about the model itself, and it sets the template for the next release cycle: the model is settled, and the work is on the product around it.

Frequently Asked Questions

Claude Sonnet 5 Goes Default in Claude Code 2.1.197 with a 1M-Token Context Window, $2/$10 Per Mtok Introductory Pricing, and Cyber Safeguards On by Default

Anthropic announced Claude Sonnet 5 on 2026-06-30 ([Introducing Claude Sonnet 5](https://www.anthropic.com/news/claude-sonnet-5)), and Claude Code [v2.1.197](https://github.com/anthropics/claude-code/releases/tag/v2.1.197) (released the same day) made it the default model. The launch is the first Sonnet-line model that closes the agentic gap with Opus 4.8, ships a native 1M-token context window, and lands on introductory pricing of $2 per million input tokens and $10 per million output tokens through August 31, 2026 (then $3/$15 per Mtok). Sonnet 5 is the new default for Free and Pro plans in Claude and is the default model in Claude Code, available immediately on update. The release ships with cyber safeguards enabled by default (the same safeguards as Opus 4.7 and 4.8, less strict than the Fable 5 set), a refreshed tokenizer that inflates token counts 1.0 to 1.35x, and rate-limit increases across Chat, Cowork, Claude Code, and the Claude Platform to absorb the higher token usage of the new effort-level controls. The Anthropic system card and the Claude Code release notes both ship the same day, so the Claude Code audience gets the new model the same day it is announced.

Rolldown 1.1.4 Disables `experimental.lazyBarrel` by Default Again, One Month After 1.1.0 Made It Default-On

Rolldown [v1.1.4](https://github.com/rolldown/rolldown/releases/tag/v1.1.4), published 2026-07-01T14:02:02Z, ships one feature change and 19 bug fixes. The feature change is a partial reversal of the [v1.1.0 default-flip](https://github.com/rolldown/rolldown/releases/tag/v1.1.0) that landed on 2026-06-03: `experimental.lazyBarrel` is now disabled by default again, after four weeks of correctness reports against the default-on behaviour. The release also hardens the dev-mode path by forcing `lazyBarrel` off whenever `experimental.devMode` is set (PR [#10060](https://github.com/rolldown/rolldown/pull/10060)), on top of the existing force-off for `treeshake`. The default-flip revert (PR [#10071](https://github.com/rolldown/rolldown/pull/10071)) and the dev-mode fix both author as one line each: "disable `experimental.lazyBarrel` by default" and "fix(dev): disable lazy barrel in dev mode", and the root-cause tracking is the new [issue #10085](https://github.com/rolldown/rolldown/issues/10085) "Tracking strictExecutionOrder correctness and architecture issues", opened the day after the release. The release follows [Rolldown v1.1.3](https://github.com/rolldown/rolldown/releases/tag/v1.1.3) (2026-06-24) and is the first release since 1.1.0 to touch the lazyBarrel config surface.

Related articles

More coverage with overlapping topics and tags.

Claude Code Issue #74066: Users Report Cross-Workspace Context Bleed on Sonnet 5, Anthropic Has Not Yet Responded
ai

Claude Code Issue #74066: Users Report Cross-Workspace Context Bleed on Sonnet 5, Anthropic Has Not Yet Responded

An open bug filed against Claude Code on 2026-07-04 by an [Enterprise ZDR](https://docs.anthropic.com/en/docs/build-with-claude/zero-data-retention) user describes a working session on Sonnet 5 that suddenly starts referencing an unrelated Minecraft temple build, then doubles down on the wrong task in its recap. The reporter (GitHub: [@milesrichardson-edb](https://github.com/milesrichardson-edb), issue [anthropics/claude-code#74066](https://github.com/anthropics/claude-code/issues/74066)) is on Enterprise Zero Data Retention, the tier Anthropic specifically advertises as session-isolated. Triage on the reporter's local session JSONL at `~/.claude/projects/<encoded-cwd>/<session-id>.jsonl` finds the leaked text is not in the transcript, ruling out a local context bleed by file overlap. Four other users in the comments (with work histories going back to last year) describe near-identical behavior across Claude Code, Claude Mobile, and Claude deep research. The most plausible architectural fit is shared KV-cache state in inference ([per @yv3nne in the comments](https://github.com/anthropics/claude-code/issues/74066#issuecomment-4880448776)), but no Anthropic engineer has commented on the issue in the 22 hours since it was filed, and the issue reached the top of [Hacker News](https://news.ycombinator.com/item?id=42481789) on 2026-07-04. The tone in the thread is split: half suspecting a real platform cache reuse, half suspecting a [sonnet-5-specific hallucination triggered by a Pygments lexer](https://github.com/anthropics/claude-code/issues/74066#issuecomment-4880334711). Both readings are credible.
Claude Code 2.1.199 Adds Stacked Slash-Skill Invocations, Fixes Subagent Error Reporting, the Background-Agent Daemon Crash Loop on Linux, and the Streaming-Response Discard Bug
ai

Claude Code 2.1.199 Adds Stacked Slash-Skill Invocations, Fixes Subagent Error Reporting, the Background-Agent Daemon Crash Loop on Linux, and the Streaming-Response Discard Bug

Anthropic released Claude Code [v2.1.199](https://github.com/anthropics/claude-code/releases/tag/v2.1.199) on 2026-07-02, one day after the v2.1.198 feature release (Chrome GA, background-agent auto-PR, /dataviz, Gateway on AWS) and two days after v2.1.197 made Sonnet 5 the default model. v2.1.199 is a bug-fix release with 24 entries: one new feature (stacked slash-skill invocations load up to 5 leading skills in one prompt), and a long list of reliability fixes for subagent error reporting, the background-agent daemon on Linux, streaming-response preservation on mid-stream API errors, SSL/TLS error handling behind corporate proxies, plan mode tool-call handling, and a per-env retry policy that no longer caps the user-tunable retry count at 15. Most of the items are in the background-agent / subagent area, which is consistent with the v2.1.197 + v2.1.198 direction of treating delegation as the product surface for Sonnet 5.
Claude Sonnet 5 Goes Default in Claude Code 2.1.197 with a 1M-Token Context Window, $2/$10 Per Mtok Introductory Pricing, and Cyber Safeguards On by Default
ai

Claude Sonnet 5 Goes Default in Claude Code 2.1.197 with a 1M-Token Context Window, $2/$10 Per Mtok Introductory Pricing, and Cyber Safeguards On by Default

Anthropic announced Claude Sonnet 5 on 2026-06-30 ([Introducing Claude Sonnet 5](https://www.anthropic.com/news/claude-sonnet-5)), and Claude Code [v2.1.197](https://github.com/anthropics/claude-code/releases/tag/v2.1.197) (released the same day) made it the default model. The launch is the first Sonnet-line model that closes the agentic gap with Opus 4.8, ships a native 1M-token context window, and lands on introductory pricing of $2 per million input tokens and $10 per million output tokens through August 31, 2026 (then $3/$15 per Mtok). Sonnet 5 is the new default for Free and Pro plans in Claude and is the default model in Claude Code, available immediately on update. The release ships with cyber safeguards enabled by default (the same safeguards as Opus 4.7 and 4.8, less strict than the Fable 5 set), a refreshed tokenizer that inflates token counts 1.0 to 1.35x, and rate-limit increases across Chat, Cowork, Claude Code, and the Claude Platform to absorb the higher token usage of the new effort-level controls. The Anthropic system card and the Claude Code release notes both ship the same day, so the Claude Code audience gets the new model the same day it is announced.

Comments

Log in Log in to join the conversation.

No comments yet. Be the first to share your thoughts.