Back to Blog
claude-code weekly-update release-notes security dynamic-workflows community

What's Up Claude Code: Week of May 25th

Olivier Legris ·

TL;DR

This week was a mix of real progress and obvious sharp edges. Anthropic shipped v2.1.157 with meaningful security fixes, better plugin ergonomics, and cleaner worktree behavior, then followed it with v2.1.158, which brings auto mode to Bedrock, Vertex, and Foundry for Opus 4.7 and 4.8. The bigger product signal is Dynamic Workflows: it’s now a public research preview with real docs and limits, not just hype.

The blunt read: the platform got stronger, but it’s not boring yet.

1. The releases that matter: v2.1.157 and v2.1.158

v2.1.157 is the release I’d actually care about if I were running Claude Code day to day.

It fixes a real safety bug where sandbox network prompts were showing up in auto/bypass-permissions mode, closes the rm -rf $HOME trailing-slash bypass, and stops background-agent worktrees from getting orphaned. It also makes plugins dropped into .claude/skills auto-load without marketplace registration, which is a nice little friction drop for local plugin development.

Useful bits that are easy to miss:

  • claude plugin init <name> scaffolds a plugin directly into .claude/skills.
  • /plugin now has better autocomplete.
  • Unprocessable images attached via paste, MCP, or dialog no longer crash the request.

Then v2.1.158 adds auto mode to Bedrock, Vertex, and Foundry for Opus 4.7 and Opus 4.8. That’s a real operational shift if you run Claude unattended on cloud providers: set CLAUDE_CODE_ENABLE_AUTO_MODE=1 and you’re in a much less manual workflow.

Sources: v2.1.157 release notes · v2.1.158 release notes · May 30 changelog summary

2. Dynamic Workflows is the product signal

The most important strategic move this week is Dynamic Workflows.

Anthropic is now treating multi-agent orchestration as a first-class Claude Code feature, not a hack people assemble themselves. The public docs say it supports up to 16 concurrent and 1,000 total subagents per run, and it’s available across paid plans and the major platform surfaces. The ultracode setting is the interesting bit: it lets Claude decide when to fan out automatically instead of waiting for you to type a workflow prompt.

That’s the useful framing here: this is moving from “one assistant session” toward “Claude as a control plane.”

But the early rough edges are already visible:

  • scriptPath dispatch can drop args.
  • User-global ~/.claude/workflows files don’t always resolve by name.
  • HN feedback is already flagging surprise token burn and no mid-run steering.

So yes, this is real. No, it’s not something I’d trust blindly in a critical path yet.

Sources: Dynamic Workflows launch · official workflow docs · scriptPath/args issue · HN discussion

3. The caution flag: Opus 4.8 / 2.1.158 is still noisy

There’s enough fresh noise around Opus 4.8 and v2.1.158 that I wouldn’t call this train settled.

Recent reports include assistant text getting swallowed after tool use, plus a broader tool-loop reliability cluster around parse failures and Bash weirdness. The practical takeaway is simple: if you’re leaning on 4.8 for real work, keep a fallback model handy and don’t assume every “finished” turn actually finished cleanly.

If you hit odd behavior, Sonnet 4.6 is still the escape hatch.

Sources: #64129 · May 31 tool-loop cluster

4. Community project worth looking at

The one fresh community project I’d actually point people to this week is Skill for Humanity.

It ships 171 structured reasoning skills and a /think router that maps the problem to the right method instead of making you guess. That turns “think harder” into an actual workflow, which is the part I care about.

If you want reusable reasoning patterns instead of another pile of prompts, this is worth a look.

5. Community events

The calendar is still moving. The latest sync shows a few good meetups worth watching.

This week (May 25–31):

Next week (Jun 1–7):

Later in June:

Later:

Host your own on Luma →

6. What I’m watching

  1. Whether Dynamic Workflows gets predictable enough to use without babysitting.
  2. Whether the 2.1.157/2.1.158 release train settles down.
  3. Whether .claude/skills auto-load becomes the default way local plugins are shared.
  4. Whether auto mode on Bedrock, Vertex, and Foundry is safe enough for unattended work.
  5. Whether the Opus 4.8 tool-loop cluster gets a clean fix fast.