Claude Code Daily Briefing - 2026-09-05

Release Summary

VersionDateKey Changes
v2.1.2619/4/skill-doctor, bashOutputMaxChars/taskOutputMaxChars, --append-subagent-system-prompt-file, organization policy status display, and 70+ other changes
v2.1.2609/3Full-screen diff panel (/diff), fix for a permission rule invalidation bug, and 70+ other changes (covered in the 9/4 briefing)
v2.1.2599/2managedMcpServers, --permission-prompts none, and 40+ other changes (covered in the 9/3 briefing)

v2.1.261 landed just one day after v2.1.260 (9/3). It brings new features like /skill-doctor, which shows whether loaded skills are actually being used and their context cost, and bashOutputMaxChars/taskOutputMaxChars, which let command and background task output be received inline up to 128K characters, alongside more than 70 fixes and improvements.

Full release notes


New Features & Practical Usage

/skill-doctor — surfaces unused skills and their context cost (v2.1.261)

A new /skill-doctor command shows which loaded skills are actually going unused, along with how much context each one is costing. You can use this to prune skills you don’t need.

/skill-doctor
# Shows loaded skills, each one's context usage, and whether it's actually being invoked

When you accumulate plugins and skills over time, it’s easy for skills you never actually call to quietly eat into your context on every turn. /skill-doctor lets you find and remove those, freeing up both context headroom and prompt-cache efficiency. Full release notes

bashOutputMaxChars/taskOutputMaxChars — receive command and background task output inline up to 128K characters (v2.1.261)

Previously, output from command execution and background tasks that exceeded a certain length would get written to a file, with only a summary passed inline. New bashOutputMaxChars/taskOutputMaxChars settings let you raise that inline limit yourself, up to 128K characters.

// settings.json
{
  "bashOutputMaxChars": 131072,
  "taskOutputMaxChars": 131072
}

If you want to analyze long build logs or test output directly instead of being routed through a file, these settings let you raise the inline limit as high as you need. Full release notes


Developer Workflow Tips

--append-subagent-system-prompt-file — pass long subagent prompts without hitting command-line length limits (v2.1.261)

Until now, appending content to a subagent’s system prompt meant passing it as a command-line argument, which made it easy to hit the shell’s argument length limit. A new --append-subagent-system-prompt-file option reads the content from a file instead.

claude --append-subagent-system-prompt-file ./prompts/reviewer-guidelines.md

If you want to attach a large document, like your team’s code review standards or architecture guidelines, to a subagent in full, you can now manage it as a separate file and pass it in without worrying about command-line argument limits. Full release notes

How is MCP actually being used in production? — an Ask HN thread rounds up the answers (9/4)

In response to a question about why MCP generated so much buzz at launch yet real production use cases are hard to come by, practitioners shared what they’re actually doing. The consensus: MCP is being used for internal ops diagnostics, SaaS integrations, voice agents, and customer-facing chatbots, mainly because it cuts down on tool-discovery and integration overhead compared to wiring up plain APIs or CLIs directly.

If you’re designing a new MCP server for Claude Code, this is worth reading as evidence that narrowing your tool scope to a specific operational or customer-facing scenario tends to work better in practice than building a general-purpose API wrapper. GeekNews


Security & Limitations

Claude service status — no new incidents 9/4-9/5, all services operational

Checking status.claude.com directly, there have been no newly logged incidents as of 9/4-9/5 since the 9/3 incident covered in the 9/4 briefing (elevated error rates on Claude Sonnet 5, Mythos 5.1, Fable 5.1, and Opus 5, among others, all since resolved), and every service — including claude.ai, Claude Console, Claude API, Claude Code, Cowork, and Government — is Operational.

As of the StatusGator check (2026-09-05 02:08 UTC), there were 4 user reports in the past 24 hours, citing error messages, API overload (529s), and unresponsive requests from Brazil, France, and Oklahoma, US. These look like scattered reports concentrated in specific regions and time windows rather than a pattern pointing to a broader outage. Claude Status · StatusGator


Ecosystem & Plugins

wigolo — a local-first web search tool that bundles 18 search engines into a single MCP interface (9/5)

Provides search, page reading, crawling, data extraction, caching, similar-document search, and research capabilities for AI agents through a single MCP interface. Searches query all 18 engines at once, merge the results, re-rank them with a local model, and attach an excerpt plus source location and citation ID to each result.

If you’re wiring a research pipeline into Claude Code over MCP, this all-in-one local tool is worth considering as a gateway instead of stitching together multiple search engines yourself. GeekNews

CLIProxyAPI — a local proxy that exposes AI subscription accounts like Claude Code through standard APIs (9/4)

Connects OAuth-logged-in accounts from ChatGPT Codex, Claude Code, Gemini, Grok Build, Antigravity, and others to a local proxy, exposing them through several standard API formats. This lets you call your subscription account’s models from existing SDKs, API clients, or other coding agents without issuing a separate API key.

Reusing a subscription account’s OAuth through third-party tools is convenient, but as the Google Antigravity terms controversy below shows, vendors can change policy to explicitly ban this kind of reuse — worth keeping in mind. GeekNews


Community News


Minor Changes

All items below are from v2.1.261 (9/4).



Interesting Projects & Tools