v0.0.16

CCC v0.0.16 is the Cargo-first release for the CCC fresh runtime.

Install or update:

cargo install codex-cli-captain --force
ccc setup

After setup, fully restart Codex CLI / Codex App when requested, then verify:

codex mcp list
ccc check-install --text
ccc status --text

Highlights:

• WAVE orchestration prompt projection for explicit $ccc work.
• ODYSSEY planning persistence with host update_plan mirror/applied gates.
• Graph-card and graphify-backed planning context refresh.
• Host-visible subagent dispatch envelopes, fan-in receipts, and live-dispatch truth gates.
• Hook-driven LSP safety proof, bounded LSP receipts, and post-edit diagnostics gates.
• Raider bounded execution, stable edit anchors, focused test evidence, and Arbiter/reverify closeout gates.
• LOC guard set to 400 pure LOC for focused files.
• Bounded status/activity/readiness projections that omit raw repo, rule, graph, and LSP payloads.

The normal install/update path is crates.io. Legacy release-bundle fallbacks remain pinned to older releases for environments that intentionally require them.

v0.0.15

CCC v0.0.15 release for the existing v0.0.15 tag.

Release identity:

• Tag/artifact identity: v0.0.15 at fd7ca6ab2d7ecab0003002eec0bf2cfda5c72828.
• Source candidate: 79ce2002f9865ead11605d1ad2b63ed3a9c31660.
• Release repo public docs correction: 33e104eddaa40a699c3a244c991e10c9f84519f6 on origin/main.

Important boundary:

• The existing v0.0.15 tag points to fd7ca6ab2d7ecab0003002eec0bf2cfda5c72828.
• The public docs correction commit 33e104eddaa40a699c3a244c991e10c9f84519f6 is on release repo origin/main and is not the tag target.
• This GitHub Release does not authorize package publish or cargo publish.
• External harness removal is not done.

v0.0.14

v0.0.14

CCC 0.0.14 focuses on a cleaner operator flow for Codex CLI: start with $ccc,
let CCC plan and route the work, keep progress quiet, and verify completion from
current evidence.

Updated

• $ccc is the stable public entrypoint for CCC-managed Codex work.
• The installed hook surface is quieter and keeps wccc/task-card details out of
  normal operator output unless they are needed.
• wccc planning now focuses on the operator's task and mirrors the plan into
  Codex's update_plan surface when available.
• Captain routing guidance is tighter so the host Codex orchestrates work,
  consumes fan-in, and avoids doing specialist work directly when delegation is
  available.
• Runtime completion handling was repaired so terminal fan-in plus review
  evidence can close the run instead of expanding extra task-card rows.
• Install/update parity checks now verify plugin cache, hooks, skills, custom
  agents, Graph Context, and cargo-installed binary state for 0.0.14.
• Release README surfaces were simplified for a clearer first-run path.

Commands

Use this inside Codex CLI:

$ccc 한국어로 작업하고 보고해줘. Check the current CCC install health and report what is ready.

Run these in your terminal:

cargo install codex-cli-captain --force
ccc setup
ccc check-install --text
ccc status --text

Assets

This release includes macOS, Linux, and Windows tarballs plus
ccc-0.0.14-checksums.txt.

v0.0.13

Codex-Cli-Captain 0.0.13 release.

Highlights:

• Tightens CCC LongWay, fan-in, reclaim/review, and host-boundary release proof.
• Refreshes Graphify/native graph freshness, LSP surface proof, install/check-install/status/app-panel evidence, and package hygiene.
• Documents token/context efficiency, Captain-owned verification, hidden internal wccc planning direction, and future orchestration gates without claiming unimplemented features.

Assets:

• darwin-arm64
• darwin-x86_64
• linux-arm64
• linux-x86_64
• windows-x86_64
• checksums

Source commit: 03b950d745beb6b021004124aaf144d3e23f96ae

v0.0.12

v0.0.12

0.0.12 is the public release for codex-cli-captain at HoRi0506/Codex-Cli-Captain-Release.

The source repository release page may 404 by policy, and that remains expected when the public release surface is the release repo.

Release State

• codex-cli-captain v0.0.12 is published on crates.io.
• source main is pushed at 2aa2bfb5a142843154f2fa56bfb4450d2292c072.
• the public release includes the expected asset set listed below.

Public Artifacts

• ccc-0.0.12-darwin-arm64.tar.gz
• ccc-0.0.12-darwin-x86_64.tar.gz
• ccc-0.0.12-linux-arm64.tar.gz
• ccc-0.0.12-linux-x86_64.tar.gz
• ccc-0.0.12-windows-x86_64.tar.gz
• install.sh
• install.ps1
• ccc-0.0.12-checksums.txt

Release Notes

• v0.0.12 is the published public release for the 0.0.12 line.
• the release repo is the canonical public download surface for the published artifacts.
• the checksum asset is part of the published release and should be used to verify downloads.
• Graphify is bounded to read-only artifact evidence plus scout/source fallback unless active backend proof is recorded separately.
• Native code graph is bounded to local .ccc/graph/store.json read/update evidence unless install-backed source-truth proof is recorded separately.
• External LSP is bounded to CCC-local readiness plus local explicit-file protocol behavior; full server-backed diagnostics/references/definition and lifecycle remediation are not claimed by this release body.

Residual Risks

• Windows dynamic/native smoke may still be static-only if no runnable Windows environment was used.

v0.0.11

v0.0.11

0.0.11 is the Odyssey transition baseline for Codex-Cli-Captain.

• Public install flow: the primary path is now cargo install codex-cli-captain, followed by ccc setup and ccc check-install.
• Release-bundle fallback availability and checksums: the pinned v0.0.11 install.sh and install.ps1 fallback installers remain available with matching bundle verification material.
• $cap / LongWay / status / projection / app-panel improvements: the public operator flow was tightened around the core CCC task surface instead of internal release-work wording.
• Odyssey transition baseline and mission fields: 0.0.11 keeps the current mission-field work as the baseline for later Odyssey follow-up, not final completion.
• Routing / fan-in / recovery / Ghost dispatch proof visibility: the current release surfaces the operator-facing proof and handoff state more clearly.
• Memory / hooks / LSP / runtime readiness surfaces: install and readiness guidance now centers on the visible runtime and environment checks users need.
• Skills / SSL / custom-agent / plugin-cache parity validation: the current CCC install surface and its managed assets are checked more consistently.
• Remaining follow-ups: deeper Odyssey completion work, broader parity cleanup, and further internal packaging hardening remain after 0.0.11.

v0.0.10

v0.0.10

v0.0.9

CCC 0.0.9 release repo documentation update. Cargo is the primary 0.0.9 install path. Legacy public fallback installers remain targeted at v0.0.8; this release does not publish or claim new bundle assets.

v0.0.8

v0.0.8

0.0.8 is the source-level release candidate follow-up to the Cargo-first 0.0.7 release. This note records prepared source/package metadata, implementation evidence for the low-mini default alignment slice, review/verification routing to Verifier/Arbiter by default, LongWay runtime progress percent output on status/app-panel/progress surfaces, the deterministic latency/throughput drift guard, the app-panel fallback fix, the source-level Negative Evidence Memory slice, the Optional UI visual evidence ledger, and the bounded Oracle UI/UX audit gates. The installed CLI/runtime surfaces now report 0.0.8, updateParity is current after setup backfilled the shared config version, and source/package validation is green. The repaired release asset matrix now passes as well, so implementation validation is complete; publication/tag/upload remains a separate release operation if it has not already been done. The broader UI/UX audit stays explicitly deferred outside 0.0.8; Oracle remains read-only.

Publish Blockers Before 0.0.8

• fix ccc setup so safe missing or stale scalar top-level ccc-config.toml version values migrate to the current package version while unsupported object/table values stay conflict-protected; this is now covered by the release-pass evidence
• repair the current source test failures for CLI subagent text, status payload keys, delegation-plan key contracts, workspace .ccc/.gitignore mutation-guard behavior, Ghost guard semantics, and host-handle text expectations; this is now covered by the green source/package validation evidence
• reclassify Waiting for <uuid> host progress labels as host-owned Codex output; 0.0.8 may claim callsign rendering only on CCC-controlled status/projection/check-install/app-panel/subagent text surfaces, with displayAliasContract.host_toast_alias_supported=false
• update release-work docs so they say the installed CLI/runtime surfaces now report 0.0.8, updateParity is current after setup backfilled the shared config version, and the repaired release asset matrix now passes; keep publication/tag/upload as the remaining release operation if needed
• rerun ccc setup, ccc check-install --json '{}', full source/package validation, and the black-box runtime matrix until the implementation validation path is complete

Planned Scope

• record CCC-native concise output defaults as completed implementation evidence for safe status, lifecycle, fan-in, app-panel, and operator-facing surfaces using the repo-local Caveman clone only as reference material; the compact-rendering slice is internal Rust behavior and is not a separate user-facing compact-mode or external Caveman runtime dependency
• preserve prompt-token optimization as a behavior-preserving source-level contract: compact/trimmed prompt and custom-agent surfaces keep role, routing, safety, approval, sandbox, fan-in, and release guardrail semantics while golden/proxy regressions bound or improve word-count proxies. This is source-level validation only; implementation validation is complete at source/current-runtime/release-asset matrix level, and publication/tag/upload remains a separate release operation if not already done.
• make ccc_subagent_update Ghost policy-critical blocks atomic across the named persisted CCC state/artifact surfaces before PermissionDenied
• keep CCC guard distinct from Ghost: guard is the deterministic control-plane policy gate, while Ghost contributes policy or sentinel evidence that can trigger or justify guard decisions without being the guard itself
• align documented mini-role model/reasoning/fast policy with runtime defaults, setup/backfill behavior, generated custom agents, SSL metadata, planned rows, status, app-panel, and check-install surfaces; Explorer/Scout, Documenter/Scribe, Sentinel/Overseer, companion_reader/Probe, and companion_operator/SCV now default to gpt-5.4-mini with low reasoning and fast_mode = true unless an explicit per-task override is supplied
• require CCC version updates to migrate or backfill ccc-config.toml, including version, generated_defaults, role model/reasoning/fast defaults, concurrency settings, and CCC-owned hook readiness settings; the implemented 0.0.8 slice now covers the current-binary generated-default backfill path for missing managed role sections and the stale CCC-owned generated-default refresh path while preserving user-owned overrides
• require active runtime parity before release close: after the version bump/install/setup/restart path, the installed binary, active MCP server identity, plugin cache, packaged $cap, and managed custom-agent sync must all identify the 0.0.8 build before live $cap routing behavior is treated as 0.0.8 proof
• audit and remediate $cap and per-agent skill overload by splitting routing from task execution, bounding command/action batches, reducing duplicated prompt or skill surface, and validating against performance degradation or behavioral drift; review/verification routing now defaults to Verifier/Arbiter and the deterministic latency/throughput drift guard regression is part of the closure evidence
• close Scout's SCV overassignment routing drift finding for the implemented behavioral slice: early git/gh/release inference now passes through a narrowness gate, so only narrow git/GitHub/release/operator command cards route to companion_operator, while broad docs/code/review/release implementation stays with Scribe/Raider/Arbiter as appropriate; user-facing status/app-panel text now shows CCC callsigns/stable IDs and assignment reasons without raw host transport labels such as explorer or worker by default
• keep the broader UI/UX agent improvement audit for product-design / Oracle / ccc_oracle deferred outside 0.0.8, while shipping bounded audit gates backed by source evidence: Oracle remains a read-only review lane, domain-specific briefs are required, screenshots or rendered artifacts trigger visual QA evidence-path requirements or explicit absence/blocker handling, and accessibility/layout/evidence findings stay explicit while implementation and mutation remain with execution specialists. Model design limits remain acknowledged constraints rather than fatal blockers.
• implement the Optional UI visual evidence ledger as a source-level, CCC-native memory diagnostic for Oracle/UI routes when screenshots or rendered artifacts exist. The ledger records screenshot path, viewport, bbox or region reference, before/after relation, accessibility findings, layout findings, and evidence paths. It is optional and non-blocking when no UI evidence is supplied, and it does not authorize Oracle mutation; implementation ownership stays with execution specialists.
• keep the desired $cap / auto-enter interaction flow as a LongWay-derived concise progress-update plan: $cap and auto-entry should preserve the LongWay route, recover or replan on route drift, never bypass LongWay with host-side narration, and keep progress updates tied to the current phase/item with completed/total and percent from persisted LongWay phase/checklist/task-card truth; runtime status/app-panel/progress percent output is implemented, while host-side auto-continuation remains unclaimed unless separately validated
• implement workspace .ccc LongWay/run storage for fresh runs: new run state is written under the enclosing working repo .ccc when cwd is inside a Git repo, or under the Codex-start cwd .ccc fallback; .ccc is created when missing, .ccc/ is added to workspace .gitignore idempotently, Unix central ~/.config/ccc/workspaces/... access is preserved as a compatibility/global alias to the same run state, stale or divergent central paths are rejected, non-Unix new-run central aliasing is explicitly unavailable, and older cwd-local, Codex-home, and central configured run stores remain lookup/status fallbacks
• close the source-level Codex CLI 0.132 follow-up batch for codex doctor --json runtime-parity validation, Plugin CLI / marketplace metadata parity, hook-contract re-review for the 0.131/0.132 contract changes, permission/profile/effective workspace-root surfacing in ccc status and ccc check-install, and multi-agent namespace/service-tier alignment; implementation validation is complete at source/current-runtime/release-asset matrix level, with publication/tag/upload separate if needed
• close the source-level display/UX wording slice for host/subagent waiting surfaces and command-execution wording where CCC controls the output; structured payloads still preserve raw ids for machine use, and installed/runtime parity is now current after setup backfilled shared config version
• validate Ghost visibility and telemetry so the policy work is observable through calls, output, and status
• keep app-panel in 0.0.8 as the retained MCP Apps render/resource surface. Codex app usage is no longer the driver, but the explicit structured content, resource URI, CLI artifact/output path, and ccc_render_app_panel MCP contract still provide parity that ccc status and ccc check-install do not replace
• audit whether Graphify, memory, and hooks are actually used well, and keep the implementation and docs organized by module/file/directory if gaps need fixes
• audit and, if needed, fix routing/status projection so documenter/Scribe work, Arbiter/Verifier review fan-in, Ghost/Sentinel policy evidence, and guard-required review gates are shown distinctly rather than collapsing review fan-in into Raider/code-specialist routing
• keep restart/cache reload guidance after ccc setup when marketplace, skill, hook, or managed custom-agent surfaces change
• keep the app-panel reproduce/monitor item closed for 0.0.8: the retained app-panel surface has focused validation coverage, and the prior broader-suite caveat is resolved as keep after the packaging mismatch fix
• keep public status labeling honest for the guard/Ghost/review slice: Arbiter/Verifier fan-in sho...

v0.0.7

v0.0.7

0.0.7 is the Cargo-first public release that aligns the runtime crate, packaged plugin metadata, managed-agent assets, release repository installers, and operator-facing docs.

Release Readiness

• plugin registration and install visibility now line up across source metadata, packaged plugin manifests, and the public release docs
• Ghost/watchdog surfaces are included in the release asset manifest checks so the packaged control-plane story stays visible
• the model/routing matrix is aligned to the current 0.0.7 release shape, including Oracle/model-evaluation guard coverage
• parallel agent utilization remains part of the release-facing routing story, with no claim of unbounded fan-out
• capability and tool surfaces stay documented as packaged CCC surfaces rather than ad hoc operator affordances
• setup and handoff docs now describe the Cargo-first path first and keep the legacy release-bundle fallback boundary explicit
• UserPromptSubmit hook readiness stays documented as an opt-in surface, not as a silent default
• operator command reliability and prompt token optimization are included in the release validation surface

Validation

• cargo test -p codex-cli-captain: 502 unit tests and 11 package tests passed.
• cargo fmt --check --all: passed.
• cargo metadata --format-version 1 --no-deps: reports codex-cli-captain 0.0.7.
• cargo package -p codex-cli-captain --allow-dirty --no-verify: packaged 88 files.
• cargo publish -p codex-cli-captain --dry-run --allow-dirty: verified and reached dry-run upload.
• cargo publish -p codex-cli-captain --allow-dirty: published codex-cli-captain v0.0.7 to crates.io.
• cargo install codex-cli-captain --version 0.0.7 --root /private/tmp/ccc-cargo-install-0.0.7 --force: installed the public crate; /private/tmp/ccc-cargo-install-0.0.7/bin/ccc --version returned 0.0.7.
• scripts/release/verify-release-asset-matrix.sh: passed for macOS arm64/x86_64, Linux arm64/x86_64, and Windows x86_64 bundles.
• GitHub release card: https://github.com/HoRi0506/Codex-Cli-Captain-Release/releases/tag/v0.0.7

Asset Checksums

• ccc-0.0.7-darwin-arm64.tar.gz: sha256:c5365dcb1ef269e6d107ee6c0882fa266b8fb2053874b93e3f2633d18b499226
• ccc-0.0.7-darwin-x86_64.tar.gz: sha256:d8de90427f8b556ed223dcd21caa1c70363fc56070b0a7020c94ccfe62e1bfd3
• ccc-0.0.7-linux-arm64.tar.gz: sha256:872e286b28096188f989d0c78e750a7eaf65f99b7f8259380c86da0b4631f38e
• ccc-0.0.7-linux-x86_64.tar.gz: sha256:4f7f875dccf82e9f2ea769fecff83bdcb9e300793a7e3de38e2f9af3c3c717c4
• ccc-0.0.7-windows-x86_64.tar.gz: sha256:edd7213ef66b1b4f616dcdfd9ca3968c601fb15998431b103ca57ff11e4db7be