code.claude.com web signal

Claude Code Fast Mode defaults to Opus 4.7 in v2.1.142

anthropic coding tools claude-code coding-tools ai-agents

Key insights

  • Claude Code 2.1.142 silently upgrades all Fast mode users from Opus 4.6 to the more capable Opus 4.7 with no configuration change required.
  • Seven new `claude agents` flags now cover directory access, MCP config, plugin directories, model selection, effort, and permission modes for scripted runs.
  • Bundled daemon reliability and MCP server fixes in 2.1.142 indicate Anthropic is still actively stabilizing Claude Code's agentic infrastructure layer.

Why this matters

Fast mode defaulting to Opus 4.7 raises the capability floor for every Claude Code user on 2.1.142 without requiring migration work, compressing the time between model releases and widespread adoption. The seven new `claude agents` flags transform the CLI from a developer tool into a production-grade orchestration interface, enabling engineering teams to script agent behavior with precision previously requiring a full SDK integration. Together these changes signal that Anthropic is treating Claude Code as a serious headless automation runtime, not just an interactive assistant, which reshapes how platform and DevOps teams should be evaluating agentic AI tooling in their stacks.

Summary

Claude Code 2.1.142 ships two changes for power users: Fast mode now defaults to Opus 4.7 instead of Opus 4.6, and the `claude agents` CLI gains seven new flags for scripted workflows. The flags -- `--add-dir`, `--settings`, `--mcp-config`, `--plugin-dir`, `--permission-mode`, `--model`, and `--effort` -- cover directory access, model selection, effort level, and permission scopes for headless agent runs. Essentially: Anthropic is tightening the Claude Code agent CLI for teams building automated pipelines. - Fast mode upgrades to Opus 4.7 on 2.1.142 automatically, no configuration required. - The seven new agent flags enable precise control over model, effort, and permissions in non-interactive workflows. - Daemon and MCP server fixes are bundled, signaling ongoing stabilization of the agentic infrastructure layer. For teams embedding Claude Code in CI/CD pipelines, this release narrows the gap between CLI experimentation and production-grade agent deployment.

Potential risks and opportunities

Risks

  • Teams with auto-updating Claude Code deployments may see unexpected behavioral shifts if Fast mode silently swaps from Opus 4.6 to 4.7 mid-sprint without explicit version pinning.
  • Misconfigured `--permission-mode` or `--add-dir` flags in shared CI/CD environments could grant scripted agents unintended directory or MCP server access, expanding the blast radius of a compromised pipeline.
  • Production pipelines already built on the 2.1.x series before 2.1.142 face reliability risk if bundled daemon and MCP fixes introduce regressions that have not yet been validated at scale.

Opportunities

  • MCP server vendors (Zapier, Browserbase, Toolhouse) gain a cleaner enterprise integration path via the new `--mcp-config` flag, lowering adoption friction for Claude Code in larger orgs.
  • Platform and DevOps teams at mid-to-large engineering orgs can now build standardized agent-spawning wrappers around the new flags, reducing per-team Claude Code configuration overhead across shared infrastructure.
  • Claude Code competitors (Cursor, Cline, Aider) face pressure to match CLI-level agent control flags as Anthropic narrows the gap between interactive development tooling and production scripting workflows.

What we don't know yet

  • Whether Opus 4.7 fast-mode pricing differs from Opus 4.6 -- Anthropic has not published updated cost figures for the 2.1.142 fast-mode tier.
  • Which specific permission levels are supported by the new `--permission-mode` flag and whether they map to existing Claude Code sandbox permission tiers.
  • Whether the MCP server fixes in 2.1.142 address the specific stability failures reported by enterprise users across the 2.1.x series or only a subset.