Skip to content

v0.20.0

Choose a tag to compare

View all tags
@PanQiWei PanQiWei released this 16 Jul 15:40
v0.20.0
5f4c1fa
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

cc-master plugin v0.20.0

Plugin v0.20.0 makes cross-harness orchestration the default identity of a cc-master orchestrator. A master session running in Claude Code, Codex, or Cursor is guided to reason over the machine-wide worker pool instead of treating its origin harness as the only place work can run.

This release requires ccm v0.21.0 or newer. Upgrade ccm first: the plugin checks board-init/structured-board-path-v1 and goal-contract/v1 before any fresh or resumed ARM mutation, and fails loudly without them.

What changed

One orchestrator identity across three origins

  • master-orchestrator-guide now treats the orchestrator as session-portable and cross-harness from its top-level identity, worker/executor vocabulary, decision loop, dispatch, reconciliation, review, handoff, and resume guidance.
  • as-master-orchestrator surfaces for Claude Code, Codex, and Cursor align on the same machine-wide worker-pool mindset and Goal Contract lifecycle.
  • High-frequency guidance exposes the ccm operations needed to inspect harness inventory, target-native help, model policy, quota posture, workers, agents, and current board truth.

Unified model, quota, and pacing guidance

  • All origins share one O/T1/T2/T3 role taxonomy, orchestrator-tier candidates, task-role floors, ample/tight fallback chains, live admission facts, and bounded community task-affinity taste.
  • Architecture and system design prefer orchestrator-capable models; implementation normally moves one tier down when the contract is complete; review prefers a heterogeneous model family; read-only research normally moves two tiers down.
  • Machine-wide cached quota posture and coordination notifications are visible from every supported origin without provider calls in hook runtime.
  • Codex uses seven-day hard pacing with rolling-24h advisory. Cursor uses its subscription-period signal. Codex and Cursor do not gain account switching or automatic account rotation.

Hooks, commands, skills, and host adapters

  • Bootstrap performs the explicit ARM action and is its unique exemption; reinjection, usage pacing, coordination notification, board lint, board guard, and completion verification consume the shared ccm contracts while remaining dormant until a session is explicitly armed.
  • The eight distributed skills remain the product portfolio: master-orchestrator-guide, authoring-workflows, using-ccm, slicing-goals-into-dags, dev-as-ml-loop, engineering-with-craft, pacing-and-estimation, and distilling-lessons-into-assets.
  • Claude Code ships native commands, hooks, and skills; Codex ships its plugin manifest, hooks, and skills; Cursor ships host-native hooks, rules, skills, and command surfaces. Origin adapters retain only real invocation differences rather than separate model/quota worldviews.
  • using-ccm is synchronized with worker, Agent Registry, Goal Contract, model policy, routing, quota, delivery evidence, and the current 82 board validation rules.

Orchestration correctness

  • Goal Contract guidance treats the initial request and GitHub issue as source evidence, not an automatically confirmed goal. Revision, assurance, drift, Goal Brief, resume, and handoff behavior are explicit.
  • Routed tasks keep planning, selected worker/model, fallback authority, native attempt, runtime agent, and task acceptance as separate evidence.
  • Review and retry guidance rejects stale verdicts and distinguishes candidate success from integration into the baseline consumed downstream.
  • The viewer guidance follows the new Goal Contract, planning/routing, Agent Registry, quota, and model-policy surfaces while preserving its read-only boundary.

Honest boundaries

  • cc-master is harness-aware runtime guidance and notification injection; the acting subject remains the agent running inside its harness. ccm owns durable board/state/CLI mechanics and local worker lifecycle.
  • ccm worker is local and session-bound. Durable remote transport, a universal provider sandbox, stronger isolation, and Windows runtime support remain follow-up work.
  • Cursor IDE is the plugin origin surface; Cursor Agent is the headless worker surface. Installing the Cursor plugin does not turn the headless CLI into a plugin host.
  • Offline provider fixtures prove contract behavior, not universal live-provider qualification.
  • Cursor API-paid Fable/Sol routes require explicit paid-route permission; they are not silently selected.
  • Existing boards remain compatible unless an opt-in contract is enabled.

Install or upgrade

Use the paired, pinned installer so ccm is installed and verified before the plugin:

curl -fsSL https://raw.githubusercontent.com/nemori-ai/cc-master/v0.20.0/install.sh |
bash -s -- \
  --ccm-version ccm-v0.21.0 \
  --plugin-version v0.20.0 \
  --all-harnesses

The installer verifies both release checksum manifests and installs only detected plugin-capable harnesses. Cursor Agent by itself is not a plugin-distribution target.

After installation, start a new harness process/session so the new hooks, skills, commands, and rules are loaded. In particular, resuming inside an already-running Codex process does not reload that process's plugin snapshot.

Details

Assets 6
Loading