v2.0.0 release and migration

Released 2026-09-13. All eight plugins share version 2.0.0 for Claude Code and Codex. This major release removes Antigravity from co-agent's supported peers.

Tagged source · Full changelog

What changed

• All eight plugins have Codex packages. Generated entries expose the shared workflows; hook execution still depends on host support and trust.
• Co-agent uses Kiro and the opposite host CLI. Antigravity (agy) and the legacy Gemini CLI are retired. Explicit host implementation requires fresh external reviewer readiness.
• Documentation uses a shared English source. Localized guides retain locale routes and functional invocation aliases remain available. Frozen demos retain their original output.
• Repository review automation verifies the current PR. Active Critical/Major findings block merging, missing coverage is an error, and stale results cannot replace the latest review. Kiro review preflights validate its zero-tool agent.

Update your installation

Refresh this marketplace and update the plugins you use through your host's plugin manager. Start a new session or thread to load the updated package. Follow Getting started for host-specific installation guidance.

For co-agent, inspect the effective configuration before running setup or an implementation workflow. Installation does not establish peer authentication, model availability or hook trust.

Co-agent migration

1. Open /co-agent:configure and inspect the reported configuration sources. Remove retired peer settings from the user or project override that owns them. This includes retired entries under panel, harness.implementer_models and harness.implementer_efforts, plus a retired harness.implementer selection. Keep the settings for supported peers.
2. Select supported peers and their own model settings. A model label belonging to a retired provider is not automatically a valid label for another CLI.
3. Run /co-agent:setup in the orchestration project to refresh readiness. Resolve authentication, model-call or configuration failures before gated work.
4. Choose the implementation mode described below. Keep configuration and readiness queries tied to that setup project when tasks enter separate worktrees.

In Codex, select the corresponding installed skill entry; the slash commands above name the shared workflows. The v2.0.0 configuration guide owns the exact settings and helper commands.

Peers and implementation modes

Current host	External review candidates	Eligible external harness writer
Claude Code	Kiro CLI and Codex CLI	Codex, when enabled and READY
Codex	Kiro CLI and Claude CLI	None

The current host is always excluded from external peer calls. Actual participation depends on configuration and setup results.

Harness selects an eligible READY writer when one exists. When none is available, the workflow must explicitly select an authorized host implementation plan using --allow-host-implementation. The planner's JSON then reports mode: host with a null external implementer. This grants no additional write permission.

Both modes require an enabled, fresh READY raw-CLI reviewer. Invalid configuration or readiness stops planning; it does not authorize a fallback. Host implementation keeps the task worktrees, scoped change capture, tests and external review gates. The harness guide links the complete procedure.

Review and usage boundaries

Review, decide and ADR modes can continue solo with a clear notice. Consensus and harness retain their required external review. Optional local PR/push hooks remain separate from repository CI and branch protection.

An account-limit failure leaves required CI review incomplete. Resolve the provider error and rerun the failed review before merging.