The Windows beta artifact is attached to the matching stable CCB GitHub release. Download ccb-windows-x86_64.zip and its .sha256 sidecar, verify the digest, extract the ZIP, then run:

.\install.ps1 install -Yes
ccb --print-version

It requires native Windows x64, Python 3.10+, WezTerm, Git Bash, and Herdr 0.8.0 or newer. The installer creates an install-local managed Python runtime. The binaries are unsigned, and ccb update remains diagnostic-only for this beta support tier; install a later Windows build by rerunning its validated install.ps1.

If npm is not convenient in your environment, download the matching package from Releases, unpack it, and install:

tar -xzf ccb-*.tar.gz
cd ccb-*
./install.sh install

Source install is intended only for development or temporary fallback:

git clone https://github.com/SeemSeam/claude_codex_bridge.git
cd claude_codex_bridge
./install.sh install

Source install links global ccb / ask back to the checkout. Regular users should prefer the npm package.

CCB 8.7.10 includes the Flutter CCB Mobile source in mobile/ and publishes the Android APK through GitHub Releases:

• Download CCB Mobile v8.7.10 APK
• App source: mobile/app
• Server gateway source: lib/mobile_gateway

The phone app is a remote controller for real CCB projects running on a server. It can discover mounted projects from the server-wide mobile gateway, switch windows and agents, render agent conversation context, send text through pane-native input, open a terminal view, and upload/download images and documents through the authenticated gateway.

Safety boundary:

• The CCB gateway binds to loopback by default, for example 127.0.0.1:8787.
• For direct LAN access, bind one specific private interface address (wildcard and public addresses are rejected): ccb install mobile --route-provider lan --listen 192.168.31.155:8787. The pairing URL is inferred from --listen; no forwarding process or --public-url is needed.
• Remote access uses Tailscale Serve, not Tailscale Funnel.
• CCB does not store Tailscale passwords, OAuth tokens, admin API tokens, or automatically modify tailnet ACLs/grants.
• The phone receives only the scopes authorized by the pairing profile, such as view, content, terminal, file upload, and file download.

Reuse verified snapshots, deduplicate shared dependencies, recover interrupted staging and forward startup timeout settings.

Full bilingual notes.

Preserve Codex caller identity in native tool shells so bare ask results return to the correct Agent. Verified with actual Codex/OMP and Claude Sonnet 4.6 roundtrips.

Full bilingual notes.

Complete the Codex fullscreen delivery update and repair installed native ccb.exe/ccb.cmd entrypoints. Supersedes the interrupted v8.7.7 publication.

Full bilingual notes.

Fix accepted jobs waiting behind native Codex fullscreen status/shortcut rows and ordinary replies mentioning esc to interrupt, while preserving human drafts, busy/menu guards and FIFO.

Full bilingual notes.

Recognize native Claude pasted envelopes and empty Codex composers with newer status bars; preserve draft protection.

Full bilingual notes.

Full bilingual notes.

Full bilingual notes.

Full bilingual notes.

Full bilingual notes.

• Click or Enter opens files with system defaults on macOS, Linux and WSL; folders stay inside Yazi.
• Shares safe/rich configuration, preserves filenames and provides explicit WSL bridge errors.
• Full bilingual notes and validation scope.
• Prior changes: v8.7.0 input protection and v8.6.19 queues and inspection guidance.

• Run OMP asks in the visible managed pane and use OMP's native completion evidence, so tool-using turns remain active until the final assistant result.
• Keep Config V1/V2 role selection focused on general roles and agentroles.ccb_self; workflow-specific ccb_* roles remain available to V3 rather than appearing in earlier schemas.
• Refocus current public provider guidance on the primary supported CLI families. DeepSeek CLI, Z.ai, and DeepSeek Harness remain implemented and documented in historical release notes, but are no longer presented as current headline support.
• No project, conversation, or configuration migration is required. Native Windows x64 and Herdr remain beta and isolated from the shared Linux/macOS runtime.

• Show Pi and OMP native conversations in CCB Mobile while preserving Provider-private session paths and transcript boundaries.
• Inherit Pi profile assets into Agent-private homes through immutable shared snapshots, and publish concurrent first-start snapshots atomically (PR #328).
• Preserve Git author and committer identity in managed Provider homes, and return Agent control immediately after an accepted ask submission (PRs #329 and #330).
• Refresh the WeChat community QR code. Restart managed Pi Agents to refresh projected profile assets; no project, conversation, pairing, or configuration migration is required.

• Restore bearer authentication for explicit Codex CLI 0.149.0 custom providers while keeping route-only local gateways unauthenticated.
• Add per-Agent Codex model catalog projection and model override support, preserve reconnect and custom tmux configuration behavior, and make Pi clear start a fresh context (PRs #321, #322, #325, and #326).
• Keep Herdr lifecycle synchronization and UTF-8 native startup inside Windows-owned implementations, without adding shared-to-Windows imports (PRs #320 and #323).
• Restart managed Codex Agents and CCB projects after upgrading. No project, conversation, pairing, or configuration migration is required.

• Refresh an existing Agent-private Claude Keychain credential after an external OAuth re-login, so a stopped managed restart does not keep using a revoked token (Issue #319).
• Preserve a Claude-private Keychain refresh when the inherited source credential is unchanged; external Claude Keychain services remain read-only.
• Fail closed for symlinked CCB credential projections and private Keychain inspection errors. No project, conversation, pairing, or configuration migration is required.

• Add the official DeepSeek Harness as the separate Developer Preview provider dsh, using its loopback HTTP/WebSocket service and exact native turn evidence.
• Make managed AGY 1.1.13 select private file token storage immediately, avoiding the keyring timeout without writing to the user's source HOME (Issue #318).
• Roll back Windows PR changes that crossed into shared Linux/macOS runtime code and add a trusted-base native-only PR gate that rejects future cross-platform leakage.
• Keep DSH clear, compact, exact-session restore, credentials, skills, and runtime state inside provider-native, agent-private boundaries.

• Reflow Agent terminal snapshots to the phone viewport while preserving the desktop tmux pane geometry.
• Keep terminal input and reconnection stable across LAN and Relay routes, and close active sessions cleanly during gateway shutdown.
• Keep terminal font size and shortcut order in the shared Terminal settings panel, with full-width inline terminal mode on phones and wide layouts.
• Reattach persisted Windows Herdr namespace and pane references with fail-closed capability checks (PR #304).

• Turn links to ordinary files in the current Agent's .ccb/workspaces/<agent>/... tree into authenticated Mobile download attachments.
• Keep the boundary fail-closed: other Agent workspaces, hidden workspace paths, and all other private .ccb runtime state remain unavailable.
• Preserve the existing Mobile client behavior and pairing model; no project configuration or state migration is required.

• Require exact, external approval before project configuration can execute tool-window commands or custom Provider command templates; use ccb config approve-commands for intentional values.
• Recover managed Codex conversations from the latest valid session when the current session record is corrupt, without silently clearing context.
• Add visible-pane Cursor execution, Pi native history, OMP Provider-config inheritance, and more reliable Windows process and namespace cleanup.
• Expand CCB Mobile with multi-session host terminals, Relay capability-negotiated Provider controls, and stronger native Windows readiness validation.

• Show selected-Agent Provider identity, configured/active/pending model and thinking state, Codex/Claude native session usage, and optional account quota in CCB Mobile.
• Persist supported model/thinking choices through guarded, restart-required host configuration without interrupting active work or exposing Provider credentials.
• Open project-window or Agent terminals directly from Mobile home and customize terminal shortcut visibility and order.
• Add the built-in ccb-compact Skill and ccb compact command with outstanding-work checks and fail-closed Provider command selection.
• Populate Config UI from the complete available Role catalog, retain native-session boundaries in Mobile history, and refresh the WeChat group QR image.

• Keep ccb-clear in every supported managed Agent and add the required ccb-diagnose Skill. Run $ccb_diagnose <agentname> to combine daemon, lineage, queue, inbox, trace, provider-log, and live Pane evidence for one Agent.
• Classify working, waiting-input, stale-prompt, Provider-error, dead/blank, and misframed Pane states; apply only evidence-backed bounded control-plane recovery and verify the Agent afterward.
• Generate a redacted incident draft after diagnosis, but require fresh user authorization before creating any GitHub issue.
• Recover abandoned mailbox deliveries without replaying business work, expose queue depth and active job identifiers in the sidebar, preserve Kiro login/settings through its isolated KIRO_HOME, forward Provider no-terminal timeout settings, and keep old Claude busy-turn records fenced from newly queued requests.
• Probe reconnect readiness against the active Codex Provider route so custom Provider capacity and connectivity failures can continue through the existing guarded recovery path.

• Resolve each configured API, token, URL, route, and account dimension from CCB-local authority first, then read only the missing dimensions from the current external Provider state.
• Refresh inherited state on a stopped Provider generation without writing back to the user's shell, Provider home, IDE, keyring, or remote login.
• Keep one stable CCB conversation and its workspace, queue, and history across authority generations. Same-authority sessions use native resume; supported Codex/Claude/Gemini import or fork when safe, otherwise CCB records a linked continuation instead of hiding history.
• Recover usable sessions affected by the withdrawn v8.5.5 migration shape without clearing them. The withdrawn v8.5.5 package is not reused.
• Install and automatically arm bundled codex-reconnect for managed Codex panes; terminal network and selected-model capacity failures receive one bounded continue recovery when the exact pane and thread are proven safe.
• Raise the default quota for newly issued Relay Host invitations from 200 MiB to 1 GiB per 24-hour window; explicit overrides and existing credentials remain unchanged.
• Refresh the WeChat community QR image and cache key. No configuration or data migration is required.

• Withdrawn from GitHub on 2026-08-05 after a legacy-session migration regression made existing managed conversations unavailable to native resume.
• Use v8.5.6 or v8.5.4; do not install v8.5.5 for managed sessions.

• Treat --chain as a real dependency only: independent asks, communication tests, batches, notifications, and reply-delivery acknowledgements no longer create false callback chains.
• Scan or clean one Agent or all Agents from Config UI with 7/30/90-day retention while protecting active bindings, recent history, and each Provider's newest transcript.
• Keep the current Config UI focused on configuration and history cleanup by temporarily removing the read-only communication-flow observer.
• Add Android LAN preflight and reconnect guidance, Retry/Diagnostics actions, and a 15-second terminal WebSocket heartbeat without reading SSID, BSSID, or other network identity.
• Flutter analysis and all 736 App tests pass; the physical Android Wi-Fi/hotspot/VPN/DHCP-change matrix remains an explicit validation limitation.

• Raise the default quota for newly issued Relay Host invitations from 100 MiB to 200 MiB per 24-hour window; explicit operator quota flags still take precedence.
• Cache the latest callback-edge view and bound repair candidates, preventing old append-only callback history from driving sustained idle CPU and cached-read amplification.
• Pass non-API variables from agents.<name>.env into managed Claude launches while preserving CCB's API credential and endpoint precedence (PR #284).
• Existing Relay Host credentials retain their issued quota; operators must update them separately or issue a new invitation.

• Keep a respawned pane in a 90-second probation window and hold queued work until a new healthy observation confirms recovery.
• Back off unstable recovery through 30s/60s/120s/5m/10m/30m, then open a circuit after six attempts instead of restarting and writing indefinitely.
• Bound each Provider runtime to the newest 50 pane-crash records, clear stale pane history, and skip unchanged helper-manifest writes.
• Repair only stale CCB-managed Claude continuation state without touching authentication; fail closed when the managed Codex app server is unavailable.
• Move stable reply/cancellation policy into managed project memory so normal asks no longer repeat prompt blocks or require per-step cancel-file polling.
• Detach CCB Rich WezTerm from the parent TTY and provide a private Wayland XCursor overlay without replacing the selected cursor theme.

• Aggregate Claude snapshots by assistant message so thinking-only boundaries and tool narration cannot replace the true final reply.
• Recover missing Claude completion hooks only from exact request, Agent, workspace, time, and session evidence; stalled mid-stream responses fail closed.
• Execute new Pi asks in the managed visible pane and complete only from the exact bound agent_settled message.
• Keep long Pi runs free from a fixed default terminal timeout and remove the model-facing cancel-file probe that consumed an extra tool call and uncached tokens.
• Preserve persisted Pi 8.5.0 jobs and the explicit CCB_PI_EXECUTION_MODE=headless rollback path.
• Bypass configured HTTP proxies for local Mobile gateway health checks.

• Bound Pi completion to the latest agent_settled event and OMP completion to agent_end.isTerminal=true, while waiting for process exit and output closure before terminalizing.
• Failed closed on missing native terminal evidence, missing final outcomes, malformed or truncated JSONL, provider errors, and nonzero exits; terminal OMP yield remains a supported successful result.
• Bootstrapped and repaired the npm-managed Python environment during install, so release runtime dependencies no longer depend on an incomplete system Python fallback; linked Git worktrees remain correctly classified as source installs.
• Made the sidebar settings launcher recover its release-managed runtime and reliably open Config UI.
• Synchronized Mobile ask/provider activity with exact server-side state, stable completion notifications, and quieter automatic reconnect behavior.
• Tightened one-way managed Provider asset projection and added packaged Qoder control skills without exposing user-global state to managed mutation.

• Isolated mutable authentication, account, session, and storage state inside each managed Provider home for visible and headless execution.
• Made external credentials one-way inheritance input, so managed refresh or logout cannot modify the user's shell, IDE, another Agent, or another project.
• Guaranteed packaged ask and ccb-clear controls for supported managed Agents even when optional skill inheritance is disabled; managed Codex also keeps reconnect.
• Projected optional skills independently so one broken external entry cannot suppress CCB controls or unrelated valid skills.
• Added a compact, validated Relay pairing QR that fits a 97-column terminal while retaining the owner-only PNG fallback.
• Made Mobile terminal resize and stream recovery race-safe with synchronized snapshots, clean repaint, and automatic handle renewal.

• Opened Config UI with the release-managed interpreter even when the sidebar inherited a stale Python path.
• Added persistent CCB theme selection, including system-default behavior, across Config UI, Rich WezTerm, and sidebar restarts.
• Stabilized Relay terminal snapshots and incremental updates with bounded backpressure and correct wide-character accounting.
• Generated owner-only PNG pairing codes when dense payloads cannot render safely in the current terminal.
• Preserved npm/NVM and Bun package-manager ownership during Provider updates.
• Reported non-writable system installs and unsafe local registry dependencies without attempting an update.

• Added end-to-end encrypted CCB Mobile Relay transport with operator-issued one-time invitations, bounded admission, multiplexed streams, and official or self-hosted deployment modes.
• Moved route selection to ccb update mobile: choose Tailscale, a validated private LAN address, CCB Relay, or a self-hosted Relay while the phone only scans a QR code or enters a pairing code.
• Added trusted in-app Android updates that verify canonical GitHub release metadata, APK size, and SHA-256 before handing installation to the operating system.
• Preserved project identity when a CCB project is moved or renamed, and added system-following light/dark themes across terminal and configuration surfaces.
• Integrated opt-in Codex reconnect supervision into managed homes, retaining bounded terminal error evidence and refusing unsafe pane or session mismatches.
• Kept Relay payloads encrypted end to end; Relay operators can observe connection metadata but not task prompts, replies, terminal content, or transferred files.

• Centralized supported Provider upgrades under ccb update, with exact version checks, explicit decline/skip choices, and no automatic restart of active panes.
• Retired project-scoped Claude/Gemini software caches in favor of the user-installed Claude executable and one user-scoped Gemini cache.
• Added bounded post-update and post-shutdown cleanup that preserves active projects, unknown content, sessions, authentication data, and user-owned caches.
• Added persistent Config UI loopback port and protected token-source settings without exposing token values.
• Added native Qoder CLI CN support with isolated config/session state and corrected Qoder --print / --config-dir execution.
• Preserved shutdown finalizers while the server is stopping and made sidebar release checksum generation portable.
• Switched Rich mode to a compact two-column Yazi layout and synchronized all release surfaces to 8.3.1.

• Bound Kimi, Claude, and Qoder execution to their native turn, activation, session, and completion contracts.
• Added exact active-job follow-ups, correlated execution phases, orphaned-inbound diagnosis, and terminal cancellation outcomes.
• Inherited provider extensions and Copilot plugins with explicit projected-asset ownership safeguards.
• Delegated npm-managed upgrades to npm and made marker-only worktree retirement conservative.
• Kept Mobile chat and terminal modes inside the selected project workspace and synchronized all release surfaces to 8.3.0.
• Fixed sidebar settings launch on WSL and macOS with native browser fallbacks, refreshed desktop-session environment, and visible manual-open status.

• Added end-to-end startup generation fencing, bounded readiness proof, and detailed startup operation/timeline diagnostics.
• Stopped unrecoverable provider-auth restart loops and exposed the required login action through ping, project view, and the sidebar.
• Preserved additive reload identity and idempotent shutdown behavior under the stricter lifecycle authority model.
• Added opt-in Android background connection controls and kept one working reply state per agent.
• Synchronized Linux, macOS, npm, and signed Android artifacts for 8.2.1.

• Reduced repeated ccbd startup work while preserving lifecycle and ownership checks.
• Fixed Grok fullscreen startup, Claude credential-kind preservation, and Config UI model/thinking selections reverting to inherited values.
• Kept Codex ask delivery session-bound and stopped accepted empty transport acknowledgements from requeueing indefinitely.
• Improved Mobile recovery, conversation and terminal interaction, image/document/video attachments, linked-file downloads, and device-bound FCM delivery.
• Synchronized Linux, macOS, npm, and signed Android artifacts for 8.2.0.

• Superseded by later releases. Detailed notes are intentionally omitted.

• Withdrawn and superseded. Detailed notes are intentionally omitted.

• Prevented Codex native subagent rollouts from capturing CCB request binding or replacing the authoritative parent session and turn.
• Kept built-in subagent activity, messages, and completion events inside the parent agent's collaboration flow instead of returning them to the CCB caller.
• Matched the isolation behavior in the Python runtime and Rust accelerator, with an authenticated spawn_agent regression proving that callers receive only the parent final reply.
• Added independently projected native ask and ccb-clear skills to each managed Grok home; normal starts use Grok's native bypassPermissions mode while safe starts keep approval enabled.
• Refreshed inherited system Grok login state before startup and routed CCB requests through each agent's visible native Grok session; authenticated two-agent testing passed visible ask, result recovery, named clear, and post-clear isolation.

• Stabilized Mobile live conversations by merging streamed replies into one working bubble, preserving bubble identity, and avoiding refresh flicker or false working states.
• Kept agent and window selection stable across refreshes, retained pane-authentic terminal scrollback, and required explicit keyboard activation before terminal input.
• Replaced the Android pairing bridge with the embedded ML Kit scanner and preserved its release-build classes through minification.
• Filtered Codex local control transcript entries and required Grok's native turn-completion evidence before a managed request is finalized.

• Hardened Mobile invalidation recovery, snapshots, live conversation updates, attachment echo reconciliation, and task-completion notifications.
• Restored expanded-message scrolling and project file links while simplifying terminal shortcuts, compacting controls, and removing duplicate terminal headers.
• Reused managed Python environments now refresh legacy pip versions for system certificate support and opt into truststore only when its backend is available.
• Expanded guarded HTTPS mirror fallback detection for macOS DNS, proxy, timeout, and certificate failures without disabling TLS verification.

• Added a bounded Mobile gateway SSE invalidation stream so project, activity, and conversation changes refresh authoritative state without active-view polling.
• Added bounded read-only Mobile snapshots, reconnect status and automatic recovery while retaining the selected host, project, agent, recent conversation state, and completion notifications.
• Mobile host startup now recognizes and safely adopts matching legacy gateway processes, avoiding duplicate listeners during upgrades.
• macOS release updates preserve healthy managed Python environments and retry watchdog installation through a configurable mirror after TLS or network failures.

• Added a visual project configuration control panel, opened from the sidebar's top-left ⚙ Settings action or with ccb config ui, with validation, diff review, save, reload dry-run, and guarded hot reload.
• Blank projects now mount exactly one agent named demo, selecting the first locally available supported CLI; explicit project and user configs still support any single- or multi-agent topology.
• Added managed Grok CLI integration, Kimi Code v0.23.1 readiness support, correct OpenCode fresh-session behavior, and reliable Claude/Gemini hook launcher execution.
• Improved CCB Mobile gateway profile persistence, paired-credential retention, project health caching, warm-list visibility, and terminal UI efficiency.
• Reorganized localized READMEs under README/, added the real config-control screenshot, and synchronized package, Mobile, workflow, and release metadata for 8.1.0.

• ccb update mobile now uses more tolerant per-request and overall startup timeouts for the server-wide loopback /v1/health endpoint, avoiding false failures when many projects are mounted.
• Added a regression test covering health responses that arrive after the previous 0.5-second request timeout.
• The default APK URL, README, package metadata, and mobile app version metadata now point to 8.0.19.

• Managed Codex homes now project auth.json, config.toml, company API sidecars, and safe auth/key/token sidecar filenames referenced by config.toml.
• Added .ccb-auth-projection.json evidence manifests that record source and target presence, size, and SHA256 without storing secret values.
• Explicit Codex API authority clears inherited auth sidecars, WSL diagnostics identify Windows interop executables, and server-wide mobile discovery tolerates stale project records.
• The role catalog is now collapsed by default, the WeChat image is refreshed, and mobile release metadata points to 8.0.18.

• Codex ask completion now uses no-progress time, so actively growing long-session files do not fail based only on submission age.
• Missing official session or log evidence returns a diagnosable non-success state, while explicit shutdown is reported as a provider crash.
• Mobile frontdesk submissions use ccbd ask jobs, and ccb watch no longer defaults to a 10-second timeout.

• CCB Mobile Terminal mode adds reconnect diagnostics and recovery while keeping the current agent pane selected.
• Pane-native mobile input now records project activity so project recency reflects Terminal usage.

• Mobile host registry tests now place temporary Unix sockets under a short /tmp/ccb-sock-* path, avoiding AF_UNIX path too long failures on macOS CI.
• ccb update mobile, README links, package metadata, and the mobile release manifest now point to the 8.0.12 APK.
• v8.0.12 introduced a multilingual README set with a shared section structure; localized files now live under README/, with Chinese at README/zh.md.

• The Flutter CCB Mobile source officially moved into this repository, with the Android APK published through GitHub Releases.
• Added server-wide mobile project discovery, pairing, authenticated gateway routes, pane-native message input, conversation context rendering, terminal access, and image/document upload and download.
• Promoted ccb update mobile into the unified Tailscale Tailnet onboarding entrypoint while keeping the gateway loopback-only, avoiding Funnel, not storing tokens, and not automatically modifying ACLs/grants.

• Release artifacts now include the optional Rust ccb-runtime-accelerator; installed Codex agents no longer silently fall back to the Python hot path when the sidecar is expected.
• When a project path makes the Unix socket path too long, the accelerator socket automatically moves to a short per-user runtime socket root.
• Hardened callback repair and Codex binding cache invalidation, with recorded regression, long-idle Codex soak, Claude callback, and mixed-provider integration evidence.

• Regular long-running ask calls now continue waiting for real provider/completion results instead of terminalizing as incomplete/heartbeat_timeout only because of heartbeat diagnostics.
• Codex, Claude, and Gemini pane-backed no-terminal timeouts are now explicit opt-in by default, while explicit reliability timeout policies remain available.
• A 32-minute source-runtime ask smoke confirmed that a task can remain running for more than 30 minutes, then complete with result_message, without heartbeat_timeout or incomplete evidence.