OrchestKit · 2026-05-10 → 05-11 · Release Window

7 Releases in 24 Hours.

CC floor bumped 2.1.132 → 2.1.138 · Two adoption milestones closed at 100% · cc-watch is now self-healing.
7
Releases shipped
v7.86.0 → v7.86.6
2.1.138
New CC floor
was 2.1.132
100%
M131 + M132 + M134
all closed today
2
CVEs patched
CVE-2026-6321/6322

The 24-hour train

7.86.0
5-10 14:07
CC floor 2.1.132 → 2.1.138
7.86.1
5-10 20:33
cc-watch hardening + GH App token
7.86.2
5-11 06:11
codeql-action bump
7.86.3
5-11 06:40
claude-code-action bump
7.86.4
5-11 09:16
M132 Groups F + G
7.86.5
5-11 12:31
M132 Group H · M132 → 100%
7.86.6
5-11 ~13
Vercel Labs thorough sync

Two through five were release-please patch bumps fired automatically as conventional commits landed. One human decision drove the whole train.

107
Skills
27 user-invocable
37
Agents
specialized roles
188
Hooks
120 global · 46 agent · 22 skill
12
CC 2.1.133 matrix entries
Groups F + G + H

M131 — CC 2.1.132 adoption

36/36
closed (100%)

Groups A → E

  • A · CC version matrix · hook/agent format updates
  • B · MCP audit runbook · manifest restructure
  • C · OAuth + plan-mode resume permission
  • D · bash mkdir/touch allow · plugin-url/-dir.zip
  • E · OTEL env isolation · MCP reconnect · SDK localSettings

M132 — CC 2.1.133 adoption

14/14
closed (100%)

Groups F · G · H

  • F · parallel-session token race · MCP OAuth proxy · Remote Control interrupt · Windows mapped drives
  • G · worktree.baseRef setting · sandbox path managed settings · parentSettingsBehavior
  • H · $CLAUDE_EFFORT hooks env · session-scoped /effort · subagent skill discovery

cc-watch pipeline — now self-healing

Anthropic ships X.Y.Z+1 ↓ Daily cron @ 14:00 UTC ↓ cc-release-watch.mjs ├── snapshot detection W1b ✓ ├── cc-triage with retry W1d ✓ │ ├── ≥ floor: LLM │ └── < floor: skip W1h ✓ └── file adoption issues W1e ✓ ↓ peter-evans → release-bot GH App W1a ✓ ↓ PR opens → CI fires → auto-merges 🎉

Yesterday this chain had three silent failure modes. Today all three are guarded by integration tests.

⚠ Behavior change

worktree.baseRef

CC 2.1.133 reverted the 2.1.128 default — EnterWorktree now branches from origin/<default> again, silently dropping unpushed commits.

{ "worktree": { "baseRef": "head" } }

Required Anyone using OrchestKit's worktree-isolation flow must set baseRef: "head" on CC ≥ 2.1.133.

Vercel Labs upstream sync

agent-browser 0.26 → 0.27

  • React DevTools (tree, inspect, renders, suspense)
  • vitals + pushstate + --init-script
  • Network --resource-type filter
  • Dashboard proxy · doctor dedupe fix

json-render 0.18 → 0.19

  • defineDirective custom API
  • New @json-render/directives package
  • 7 directives: $format, $math, $concat, $count, $truncate, $pluralize, $join
  • I18n + standardDirectives

portless 0.12 → 0.13

  • OS startup service (install/status/uninstall)
  • launchd · systemd · Task Scheduler
  • Tailscale readiness preflight fix
  • Apps survive reboots

What's queued

M135 — CC 2.1.136 adoption

The W3 recovery agent pre-filed 20 issues covering CC 2.1.136's 50+ upstream bullets (autoMode.hard_deny, plugin slug case, MCP reconnect summarization, plan-mode Edit allow rule, etc.). Same Group-F/G/H pattern carries it home whenever someone has bandwidth.

0/20
M135 issues
CC 2.1.136 — the big release
0/0
M133 (CC 2.1.138)
empty by design — Internal fixes only