Four upstream breaking-fixes in CC 2.1.133 documented across configure, chain-patterns, doctor, and mcp-patterns. First group in the M132 milestone (CC 2.1.133 adoption). All four are upstream-side fixes — no OrchestKit behavior change required at our floor (≥ 2.1.138), but doc surfaces now reflect the new guarantees.
| Issue | Feature | CC | Category | Skill ref |
|---|---|---|---|---|
| #1703 | parallel_session_refresh_token_race_fix | 2.1.133 | breaking | configure, chain-patterns, doctor |
| #1705 | mcp_oauth_proxy_mtls_fix | 2.1.133 | breaking | configure, mcp-patterns, mcp-config |
| #1706 | mapped_network_drive_add_dir_fix | 2.1.133 | breaking | configure |
| #1707 | remote_control_stop_interrupt_fix | 2.1.133 | breaking | configure |
// 3 worktree-isolated /ork:implement // sessions running concurrently. // Refresh token rotates in session A. // Sessions B + C race against the // rotation and end up holding the // now-invalidated old token. // All three dead-end at 401. [A] 401 Unauthorized ← rotated [B] 401 Unauthorized ← raced [C] 401 Unauthorized ← raced // Recovery: claude /login + resume // every session manually.
// Rotation is serialized across all // sessions sharing the credential. // All three see the same fresh token. [A] continues ← fresh token [B] continues ← same fresh token [C] continues ← same fresh token // No 401 cascade. // Worktree-isolation workflow is // stable for concurrent agents.
// claude.ai Remote Control: Stop btn
[Stop] → CLI nominally interrupted
→ message queue NEVER advances
→ session wedged until killed
// Same path as local Esc
[Stop] → current tool/prompt aborts
→ message queue resumes
→ session immediately usable
HTTP(S)_PROXY / NO_PROXY / mTLS breaking// MCP transport: proxy-aware // MCP OAuth: bypasses proxy // // Steps that bypassed the proxy: // - discovery // - dynamic client registration // - token exchange // - token refresh // // Net: corp-proxy users could // never auth against OAuth- // protected MCP servers.
export HTTPS_PROXY=http://proxy.corp:3128 export NO_PROXY=localhost,.internal export NODE_EXTRA_CA_CERTS=/etc/ssl/ca.pem export CLAUDE_CODE_MCP_CLIENT_CERT=... export CLAUDE_CODE_MCP_CLIENT_KEY=... claude // Discovery, DCR, token exchange, // token refresh — all routed via // the same proxy + mTLS config // that already handles MCP // transport.
--add-dir works for Windows mapped network drives breakingPS> claude --add-dir Z:\share\project // CLI accepts the flag. // Read tool on Z:\share\project\f.ts [error] path not in allowed directories // Misidentified mapped drive as // "not local filesystem" in the // internal permission check.
PS> claude --add-dir Z:\share\project // Read / Write / Edit all succeed. // Also covers SDK additionalDirectories // for programmatic hosts. // UNC paths (\\server\share) // work the same way.
| Path | Lines | Why |
|---|---|---|
| src/skills/configure/references/cc-version-settings.md | +53 | NEW ## CC 2.1.133 Settings parent header + 4 subsections (one per issue) |
| src/skills/configure/references/mcp-config.md | +21 | NEW ## CC 2.1.133 changes with MCP OAuth proxy/mTLS subsection |
| src/skills/doctor/references/remediation-guide.md | +14 | "All concurrent sessions 401 simultaneously" recovery entry |
| src/skills/chain-patterns/references/worktree-agent-pattern.md | +2 | CC 2.1.133 concurrent-session stability callout |
| src/skills/mcp-patterns/SKILL.md | +2 | CC 2.1.133 MCP OAuth proxy/mTLS callout (OrchestKit in-tree equivalent of building-mcp-server-on-cloudflare) |
| src/hooks/src/lib/cc-version-matrix.ts | +5 | 4 new feature entries at minVersion: '2.1.133' |
| plugins/ork/... | mirror | Regenerated by npm run build |
| docs/site/content/docs/reference/skills/... | mirror | MDX regen for configure / chain-patterns / doctor / mcp-patterns |
CC floor is at 2.1.138 in engines.claudeCode, so 2.1.133's behavior is already guaranteed at runtime. What was missing: human-readable prose surfacing each fix in the right skill. configure owns CC version-settings, chain-patterns owns worktree-isolation guidance, doctor owns recovery flow, mcp-patterns owns OAuth/transport guidance.
npm run build — plugins/ regenerated; count drift = 0 (107/37/188 unchanged)npm run test:skills — structure + rule validation passnpm run test:agents — 37/37 valid frontmatternpm run test:manifests — 108 skills delivered, 0 orphansnpm run test:security — 14/14 passnpm run typecheck — cleanFirst group in M132 (CC 2.1.133 adoption). M131 (CC 2.1.128–2.1.132) is closed; this kicks off the next milestone.
## CC 2.1.133 Settings header introduced