Claude Code Set Fast Mode to Opus 4.7 — Plus 8 New Agent Flags

by

EDIBLOG · AI · CLAUDE CODE CHANGELOG

Claude Code unlocked background again — Fast mode is now 4.7

Bottom line first. Claude Code’s Fast mode default auto-switched to Opus 4.7. The same changelog batch also shipped 8 new claude agents CLI flags, an option to turn off worktree isolation, and enforced plugin dependencies — all at once.

Fast mode = Opus 4.7 agents: 8 flags worktree.bgIsolation /plugin cost display background hardened

Here’s a fresh batch from the Claude Code changelog. The Fast mode default jumped from Opus 4.6 to Opus 4.7, and three options that strengthen autonomous background execution came along with it. This is the follow-up round right after the May 14 release of the four commands /goal·/loop·/batch·/background.

If the previous round was about “slash commands that don’t stop every turn,” this round is about dispatching background sessions more precisely at the CLI level. It’s all one coherent batch, so I’m covering it in a single post.

01 · FAST MODE SWITCHIt auto-switched from 4.6 to 4.7

Before · ~May 16
4.6
Opus 4.6 · Fast mode default
Hard SWE 59%
Response speed standard
Token price same
→ changelog
auto switch
Now · new default
4.7
Opus 4.7 · Fast mode default
Hard SWE higher
Response speed kept
Token price same

If you were running Fast mode, Opus 4.7 gets picked up automatically from your next session after the update. Only if you’d pinned the environment variable CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE=1 do you stay locked to 4.6. Price is unchanged and hard-SWE performance is up versus 4.6, so it reads as close to a free upgrade.

02 · BACKGROUND AGENTSclaude agents picked up 8 flags

The claude agents command — the one you use to dispatch background sessions from the CLI — gained 8 options in one shot. You can now set permissions, model, effort level, and MCP config per session.

▮ 8 new flags — claude agents
  • –add-dir · extra working directoryFor multi-repo work, surfaces directories beyond the main cwd
  • –settings / –mcp-config · isolated settings & MCPConnect a different MCP server for just this session without touching your base settings.json
  • –plugin-dir · plugin isolationDisable global plugins and load a separate set for this session only
  • –permission-mode · force a permission modeForce acceptEdits / plan / bypassPermissions etc. per session
  • –model / –effort · set model & effort directlyTune sonnet / opus and effort level separately for each background session
  • –dangerously-skip-permissions · YOLO modeFully trusted container environments only — never on a normal workstation

The takeaway is simple. It’s now easy to run several background sessions with different profiles on one workstation at the same time. Session A on plan mode + sonnet, session B on acceptEdits + opus 4.7, session C on dangerously-skip inside a container — decided in a single CLI line.

03 · WORKTREEThere’s now an option to turn off bgIsolation

▮ NEW SETTING

worktree.bgIsolation: “none”

Meaning: instead of creating a separate worktree via EnterWorktree, the background session edits your current working copy directly. The risk of concurrent-edit conflicts now falls on you.

Previously, background sessions went through automatic git worktree isolation for safety. Safe, but it came with the friction of “the results never show up in my main working directory.” This option lets you turn that isolation off. It’s handy for a solo operator who wants to check results fast in a single working directory. In a multi-session concurrent-edit setup, keep it on to stay safe.

04 · PLUGIN/plugin now shows the cost up front

/plugin marketplace browse panel change
found after install
→
shown before install

per-turn token estimate

A plugin’s per-turn / per-invocation token estimate is now surfaced at the marketplace stage. You can spot which plugin eats tokens before installing it.

The other change in the batch is a stronger claude plugin disable. If another active plugin depends on this one, it refuses to disable it. That’s a signal the plugin dependency graph is starting to be exposed to users — reads like the plugin ecosystem has entered a real operational phase.

▮ TEAM IMPACT · OBJECTIVE 2026 / 05 / 17

From a team’s perspective, the biggest change is the Fast mode = Opus 4.7 auto-switch. No action needed — it applies from your next session.

Applies now

Fast mode users get 4.7 automatically from the next session. Check the hard-SWE response quality difference.

Optional

The 8 claude agents flags / bgIsolation are worth learning only for teams running background sessions seriously.

“If slash commands were the doorway to autonomous execution, these 8 CLI flags are the option that turns one workstation into a multi-session control tower.”

— Eddie · 2026 / 05 / 17

Three things to watch over the next week. Hands-on impressions of Fast mode 4.7 · real-world use of the agents flags · how trustworthy the plugin cost display is. All three are operational-phase signals.

Sources · References
Official Claude Code changelog

GitHub — anthropics/claude-code CHANGELOG.md Claude Code Docs — What’s new GitHub — anthropics/claude-code Releases

Opus 4.7 official

Anthropic — Introducing Claude Opus 4.7

Disclaimer: A recap of the official Claude Code changelog. Changes may vary by version and platform. No ads, no affiliates.

This post is part of an English mirror of a Korean dev experiments blog. Cross-posted for the global developer audience.

Leave a Comment