Back to Blog
claude-code weekly-update release-notes worktrees mcp community

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

Olivier Legris ·

TL;DR

The main story this week is Anthropic finally saying the quiet part out loud: Claude Code is built to work in large codebases, and the best results come from how you shape the harness around it. The new article spells out the playbook — start with a clear CLAUDE.md hierarchy, keep skills for on-demand expertise, use plugins to spread good setups, and add LSP integrations when symbol-level navigation matters.

Translation: Claude Code works better when the codebase is legible, not when you cram more context into every session. The limits increase and release notes matter, but this is the headline.

1. The main story: Claude Code in large codebases

Anthropic’s new article is the real headline this week: How Claude Code works in large codebases: Best practices and where to start.

The practical takeaway is not subtle:

  • CLAUDE.md should be hierarchical — root for the big picture, subdirectory files for local conventions.
  • Skills are for on-demand expertise — don’t load everything into every session.
  • Plugins should distribute good setups — if one team found a useful harness, make it portable.
  • LSP matters when you need symbol-level precision in big or mixed-language repos.
  • Assign a DRI or agent manager — otherwise the setup stays tribal and drifts.

That “portable setup” idea is already showing up in Anthropic’s own plugin pack: legal and small-business are now first-class plugin surfaces, not just random community hacks.

That’s the article I’d point people to first. The rest of the week’s news mostly supports it: Anthropic wants Claude Code to be something you shape around the codebase, not something you brute-force with more context.

2. The release notes that matter

The release train kept moving, and the useful changes were still the boring ones — the kind that stop the tool from acting haunted.

  • v2.1.141 added terminalSequence hook output, ANTHROPIC_WORKSPACE_ID, CLAUDE_CODE_PLUGIN_PREFER_HTTPS, PostToolUse continueOnBlock, and Rewind summarization.
  • v2.1.142 made fast mode default to Opus 4.7, expanded the claude agents flag set, surfaced root-level SKILL.md plugins, and fixed the MCP_TOOL_TIMEOUT cap.
  • v2.1.143 was the biggest patch: plugin dependency enforcement, worktree.bgIsolation: "none", stop-hook loop capping, macOS TCC fixes for background agents, and a Windows PowerShell default change for Bedrock/Vertex/Foundry users.

My read: the platform is getting more explicit about dependencies, boundaries, and background behavior. Good. That’s what real users need.

Sources: v2.1.141, v2.1.142, v2.1.143

3. Community projects worth exploring this week

I crawled r/ClaudeAI for fresh projects, and these are the ones worth your time:

  • Autoharness / GitHub — stops pretending prompt tweaking is the whole job. It changes the harness, runs evals, and keeps what scores better.
  • google-surf-mcp / npm — search and fetch in one MCP, with PDF handling and cheap abstract mode. Useful. Not clever-for-the-sake-of-it.
  • claude-rpg-skill / GitHub — persistent canon for long-form RPG narration. Odd, but genuinely structured.
  • i-have-adhd / GitHub — action first, numbered steps, no fluff. Plenty of people will prefer this over the default tone.

This is the part I’d keep an eye on next: the community is filling in the missing layers around review, orchestration, search, and reusable project context.

4. Fresh signals from this week

Three more things are worth a quick callout.

  • /insights still works as a self-coaching loop. Run it, start a fresh session, and turn the trace into concrete changes.
  • Anthropic’s new knowledge-work plugins include legal and small-business packs. The legal plugin handles contract review, NDA triage, compliance, and templated responses; the small-business plugin covers payroll, cash flow, CRM, invoicing, and onboarding. That is Anthropic packaging domain workflows the way they want teams to use Claude now.
  • Anthropic’s finance templates are a packaging signal. The May 5 drop shipped 10 ready-to-run agent templates — pitch builder, KYC screener, earnings reviewer, model builder, and more — as plugins, skills, and Managed Agents recipes.
  • Issue #59733 is the bug to watch. Consecutive permission prompts can silently replace each other in v2.1.141-143. That is exactly the sort of thing that breaks trust in concurrent subagent workflows.

5. What I’m watching

  1. Whether the June 15 billing split changes automation habits — this is the clearest operational shift.
  2. Whether v2.1.143 closes the permission-prompt regression — because broken prompts kill trust fast.
  3. Whether Opus 4.7 sticks as the default fast mode — or everyone quietly falls back to 4.6.
  4. Whether the community keeps building around harnesses, skills, and MCP glue — that looks like the next layer of the ecosystem.
  5. Whether the phantom-token bug finally gets a clean fix — because bad quota math is still a serious problem.

6. Community events

The community graph keeps growing. The latest sync shows 223 events and 247 leaders.

Coming next week (May 18–24):

Coming later:

Host your own on Luma →