v8.2.0

Startup Performance

• Cold And Warm Starts Do Less Repeated Work: ccbd reuses validated pane,
  topology, provider-profile, storage, and identity evidence across the startup
  critical path while preserving lifecycle and ownership checks.
• Tmux And Storage Operations Are Bounded: startup snapshots and atomic
  storage helpers avoid repeated subprocess and filesystem work without adding
  an always-on polling loop or changing per-agent launch ordering.
• Copied Or Moved Projects Recover Safely: an unmounted lease left by a
  different project anchor is treated as residue and replaced with a fresh
  generation, while a mounted foreign lease still fails closed; reattached
  runtime records adopt the current project identity.

Communication Reliability

• Codex Delivery Stays Session-Bound: managed asks bind delivery and reply
  collection to the intended request anchor and durable session identity,
  including after a provider context clear.
• Accepted Transport Acknowledgements Cannot Loop: an accepted empty
  reply-delivery acknowledgement is consumed as transport completion instead
  of being requeued as an empty provider answer.

Provider And Configuration Reliability

• Grok Fullscreen Overrides Minimal Mode: explicit --fullscreen startup
  arguments suppress CCB's default --minimal, while default and unrelated
  argument launches keep minimal mode. This resolves Issue #255.
• Claude Authentication Kind Is Preserved: managed Claude homes retain the
  inherited credential type instead of rewriting it into an incompatible
  login form.
• Config Choices Remain Explicit: model and thinking selections stay bound
  to the selected agent across multi-window overlays instead of reverting to
  inherited values after save.

Mobile And Gateway Reliability

• Recovery And Conversation Refresh Are Stable: foreground recovery,
  retained chat state, active selection, and working indicators converge
  without refresh flicker or stale outcomes replacing current state.
• Attachments Cover Real Mobile Work: image, document, and video selection,
  Tab-based attachment queueing, linked host-file download, and attachment
  progress/error states are supported through the authenticated gateway.
• Terminal And Conversation Interaction Is Smoother: terminal input opens
  from the latest output, expanded bubbles hand scrolling back predictably,
  and background refreshes preserve the visible timeline.
• Opt-In Push Delivery Is Hardened: device-bound FCM registration,
  deduplication, and foreground/background lifecycle handling are available to
  deployment-configured builds; the signed public APK keeps Firebase disabled
  by default and fails closed without operator-owned configuration.

Release Surface

• Desktop, npm, And Android Versions Are Synchronized: Linux and macOS
  artifacts, @seemseam/ccb, CLI metadata, Mobile version code, APK download
  links, checksums, and localized version badges all target 8.2.0.
• Community Asset Packaging Is Current: the updated PNG community image is
  included and verified by the release builder.
• Fresh Installs Preserve The Python Launcher: release installs keep the
  shared interpreter resolver intact when the executable directory is inside
  the install prefix, preventing recursive launcher invocation during smoke
  checks and custom-prefix installs.

v8.1.7

Communication Reliability

• Kept managed Codex ask and reply delivery bound to the intended session and
  request anchor.
• Fixed accepted reply-delivery acknowledgements being treated as empty task
  replies and repeatedly queued.
• This emergency release includes desktop artifacts and the npm package only;
  CCB Mobile is unchanged and is not included.

v8.1.4

Mobile Connection Recovery

• Gateway Recovery Is Centrally Supervised: foreground resume, route
  activation, repository probes, terminal transport, and task notifications
  now report through one bounded connection state machine instead of starting
  competing recovery loops.
• Stale Outcomes Cannot Replace Current State: generation fencing and
  atomic route verification discard late probe, activation, and reconnect
  results after profile or route changes.
• Background Notifications Release Their Sockets: notification streams
  suspend with the app lifecycle, close their active connections, and resume
  through serialized subscriptions without duplicate listeners.
• Authentication Failures Stay Actionable: authorization failures are
  classified separately from transient transport failures so reconnect policy
  cannot hide a required re-pair operation.

Codex Native Subagent Isolation

• Child Rollouts Cannot Capture CCB Requests: managed Codex session
  discovery, watchdog recovery, and persisted binding updates now reject native
  subagent rollouts and recover the authoritative top-level session.
• Parent Turn Binding Stays Immutable: once a CCB request is anchored to its
  parent Codex turn, child task identifiers cannot replace that binding or
  finalize the request.
• Child Collaboration Output Stays Private: native subagent activity,
  messages, and foreign-turn completion events are excluded from CCB reply
  collection in both the Python runtime and Rust accelerator.
• Real Provider Path Verified: an authenticated managed Codex test using the
  built-in spawn_agent path confirmed that the caller receives only the
  parent agent's final result.

Grok Native CCB Skills

• Ask And Clear Skills Projected Per Agent: managed Grok homes now receive
  independently owned native ask and ccb-clear skills when skill
  inheritance is enabled, without replacing conflicting user-owned skills.
• Normal Starts Use Native Maximum Permission: managed Grok now starts with
  --permission-mode bypassPermissions, aligned with other auto-permission
  providers. Safe ccb -s starts omit both bypass mode and the CCB skill allow
  rules; skill inheritance still controls only the two projected command rules.
• System Login Is Refreshed Into Managed Homes: Grok startup refreshes
  inherited auth/config state from the user-owned Grok home before the managed
  visible session launches.
• Ask Uses The Visible Native Session: incoming CCB requests are delivered
  to the target Grok pane and complete only from that prompt's native
  turn_completed/end_turn event; reply delivery returns to the caller's
  visible Grok pane instead of disappearing into a detached headless session.
• Real Cross-Agent Path Verified: a two-Grok authenticated source-runtime
  test passed visible Grok-to-Grok ask and result recovery, native EndTurn
  completion, named ccb clear grok2, and post-clear isolation checks.

Sidebar Config Entry Reliability

• Current Helper Replaces Stale Panes In Place: managed sidebar panes record
  the installed helper content identity, and both daemon topology refresh and
  foreground startup repair stale helpers without restarting agent panes.
• Release Installs Replace Runnable Old Helpers: installation now compares
  bundled helper content and rebuilds live-source helpers when Rust inputs are
  newer, rather than treating any runnable binary as current.
• Settings Launch Is Observable: the gear action resolves the CCB executable
  from the same install tree, accepts the full two-cell hit area, and reports
  opening state, the local URL, or the concrete startup error in the sidebar.

Claude Legacy Hook Migration

• Old Project Hooks Self-Heal: managed Claude preparation removes only the
  legacy CCB commands that run extensionless finish/activity Bash launchers
  through Python, while preserving user hooks, valid Python scripts, current
  direct launchers, and every unrelated project setting.

Config Control Agent Removal

• Selected Agents Can Be Removed Visually: the V1/V2 config editor removes
  the selected Agent leaf, collapses its binary split by promoting the sibling
  subtree, cleans the stale Agent overlay, and supports undo before activation.
• Hot Removal Preserves Unrelated Sessions: guarded hot reload delegates to
  the existing remove_agent transaction, reflows only the affected Window,
  realizes the target binary topology, preserves other Agent panes, and reports
  busy Agent drain as saved pending work instead of a generic failure.

Release Surface

• Release Metadata Synchronized: VERSION, source CLI metadata,
  package.json, Mobile app metadata and download links, workflow dispatch
  defaults, README variants, and release notes are aligned for 8.1.4.

v8.1.3

Mobile Interaction Reliability

• Live Replies Stay In One Bubble: streamed and refreshed conversation
  state now merge into the existing working bubble while preserving element
  identity, eliminating refresh flicker, duplicate replies, and false working
  indicators.
• Selection And Notifications Stay Stable: agent/window selection survives
  project refreshes, retained invalidations no longer trigger refresh storms,
  and completion notifications settle against authoritative conversation state.
• Terminal History Remains Pane-Authentic: the first terminal snapshot
  includes bounded tmux scrollback without duplicating screen content, later
  repaints retain the user's history position, and keyboard input requires an
  explicit activation gesture.
• Embedded Pairing Scanner Ships In Release: Android pairing uses the
  embedded ML Kit scanner and release minification preserves the scanner's
  required classes.

Provider Reliability

• Codex Control Entries Filtered: provider-local control transcript rows no
  longer appear as user conversation content in Mobile.
• Grok Completion Requires Turn Evidence: managed Grok requests wait for
  native turn-completion evidence instead of finalizing on intermediate output.

Release Surface

• Release Metadata Synchronized: VERSION, source CLI metadata,
  package.json, Mobile app metadata and download links, workflow dispatch
  defaults, README variants, and release notes are aligned for 8.1.3.

v8.1.2

Mobile Conversation And Terminal Reliability

• Invalidation Recovery Hardened: snapshots, invalidation cursors, live
  conversation refreshes, task-completion notifications, and attachment echo
  reconciliation now recover consistently without duplicate or stale items.
• Conversation Navigation Restored: expanded bubbles scroll correctly and
  project-backed file links resolve through the authenticated gateway.
• Terminal Controls Simplified: compact terminal controls remove redundant
  shortcuts and duplicate headers while preserving navigation and input.

macOS Installer Certificate Recovery

• Legacy pip Is Refreshed Safely: reused managed environments with pip older
  than 24.2 refresh pip before optional dependencies are installed, enabling
  current system-certificate behavior.
• truststore Is Capability-Gated: pip 22.2 through 24.1 opts into system
  trust only when the truststore backend is actually available.
• HTTPS Fallback Coverage Expanded: common macOS DNS, proxy, timeout,
  connection, and certificate errors trigger the configurable HTTPS mirror
  retry without adding HTTP indexes or disabling TLS verification.

Release Surface

• Release Metadata Synchronized: VERSION, source CLI metadata,
  package.json, Mobile app metadata and download links, workflow dispatch
  defaults, README variants, and release notes are aligned for 8.1.2.

v8.1.1

Mobile Realtime Recovery

• Invalidations Replace Active Polling: the server-wide gateway now
  publishes a bounded SSE invalidation journal for project, activity, and
  conversation changes. CCB Mobile refreshes authoritative REST state from
  those signals without send-follow polling or active-project polling.
• Snapshots Survive Reconnects: bounded read-only snapshots preserve the
  selected host, project, agent, and recent conversation state through gateway
  interruptions. The app exposes reconnect status, recovers automatically,
  keeps completion notifications working, and does not replay stale sends.
• Legacy Gateway Processes Are Adopted: Mobile host startup recognizes and
  safely takes over the previous foreground gateway process when its script,
  command, and listener match, avoiding duplicate listeners during upgrades.

macOS Installer Reliability

• Managed Python Environments Are Reused: release updates preserve and
  validate the existing managed .venv, so a working watchdog installation
  is no longer deleted and downloaded again on every update.
• pip Has A Guarded Mirror Fallback: install-time pip commands respect
  CCB_PIP_INDEX_URL and, on macOS TLS or network failures, retry through the
  configurable TUNA PyPI fallback. The fallback can be disabled with
  CCB_PIP_FALLBACK_INDEX_URL=0; no global pip configuration or TLS bypass is
  written.

Release Surface

• Release Metadata Synchronized: VERSION, source CLI metadata,
  package.json, Mobile app metadata and download links, workflow dispatch
  defaults, README variants, and release notes are aligned for 8.1.1.

v8.1.0

Configuration Control And Lighter Defaults

• Visual Config Control Added: the sidebar's top-left ⚙ action and
  ccb config ui now open a loopback-only project control panel for windows,
  pane splits, providers, models, thinking levels, API overrides, workspaces,
  Rich mode, sidebar settings, validation, diff review, save, and guarded hot
  reload.
• Blank Projects Start With One Agent: when project and user config are
  absent, CCB now mounts exactly one agent named demo and selects the first
  locally available supported CLI, preferring Codex, Claude, and Gemini. An
  explicit project or user config remains fully authoritative for custom
  single- or multi-agent topologies.
• Config Documentation Refreshed: the English homepage and all localized
  READMEs now show the settings entry, the real control-panel UI, and the new
  lightweight default; localized files live under README/ with Chinese at
  README/zh.md.

Provider Integration And Reliability

• Grok CLI Integrated: Grok is available as a managed native CLI provider
  with isolated home/session state, readiness and completion handling,
  diagnostics, tests, and public README badge coverage.
• Kimi Readiness Updated: Kimi Code v0.23.1 startup detection no longer
  depends on the removed K2.7 brand banner.
• OpenCode Fresh Sessions Honored: explicit fresh/new-context launches no
  longer auto-continue an older OpenCode session.
• Claude And Gemini Hook Interpreter Fixed: managed completion and
  activity hooks execute the CCB bash launchers directly, allowing their
  shebang and _ccb-python resolver to select a compatible Python runtime and
  avoiding the extensionless-launcher failure reported in GitHub issue #249.

Mobile Performance And Resilience

• Gateway Profiles Persisted: preferred Mobile gateway profiles and paired
  credentials survive temporary gateway outages instead of being discarded.
• Project Discovery Kept Responsive: server project health is cached and
  the previous project list remains visible while refreshes warm, reducing
  repeated health checks and transient empty states.
• Terminal UI Work Reduced: working-indicator repaints and terminal input
  state scans are reduced without changing input or activity behavior.

Release Surface

• Release Metadata Synchronized: VERSION, source CLI metadata,
  package.json, Mobile app metadata and download links, workflow dispatch
  defaults, README variants, and release notes are aligned for 8.1.0.

v8.0.19

Mobile Host Startup

• Mobile Host Health Window Extended: ccb update mobile now gives
  the server-wide loopback health endpoint a longer per-request and overall
  startup window before declaring the mobile host unhealthy. This prevents
  false failures when many mounted projects make /v1/health take longer than
  the previous 0.5 second request timeout.
• Mobile Host Health Regression Covered: tests now cover a healthy
  mobile host whose health response arrives after the old too-short timeout.
• Release Surface Synchronized: VERSION, package.json, mobile app version
  metadata, update links, README variants, and release workflow defaults are
  aligned for 8.0.19.

v8.0.18

Codex Auth Projection And Mobile Host Health

• Codex Auth Sidecars Projected Safely: managed CODEX_HOME
  materialization now mirrors auth.json, config.toml,
  company-codex-api-key, company-codex.config.toml, and safe
  auth/key/token sidecar filenames referenced by config.toml.
• Auth Projection Manifest Added: managed homes write
  .ccb-auth-projection.json with source/target existence, size, and SHA256
  metadata only, without storing credential plaintext.
• API Authority Isolation Preserved: explicit Codex API authority removes
  inherited auth sidecars so global login state and agent-local API config do
  not mix.
• WSL Codex Doctor Improved: ccb doctor marks Codex binaries resolved to
  Windows interop executables with reason=wsl_windows_interop_executable.
• Mobile Host Health Hardened: server-wide mobile project discovery now
  tolerates stale project records instead of failing the whole list.
• README Contact Polish Added: the public Role list is folded and the
  contact WeChat image has been refreshed.
• Release Surface Synchronized: VERSION, package.json, mobile app version
  metadata, update links, README variants, and release workflow defaults are
  aligned for 8.0.18.

v8.0.17

Ask Stability And Mobile Update

• Ask Reply Detection Hardened: Codex prompt delivery now uses a
  no-progress timer based on compact session evidence instead of failing only
  from elapsed submit time, reducing false failures on slow WSL/mac session
  writes.
• Missing Session Diagnostics Added: when the official Codex session/log
  cannot be found past the no-progress window, CCB returns attributable
  non-success diagnostics instead of silently waiting; shutdown evidence is
  reported as provider-crashed failure.
• Mobile Frontdesk Submit Routed Through Ask: CCB Mobile frontdesk messages
  now submit ccbd ask jobs rather than writing directly to panes.
• Mobile Update Watch Waits For Real Terminal State: ccb watch no longer
  has a default 10 second timeout, so ccb update mobile and other long
  update flows can wait for the real terminal condition. Explicit
  CCB_WATCH_TIMEOUT_S remains supported.
• README Contact Polish Added: the public Role list is folded and the
  contact WeChat image has been refreshed.
• Release Surface Synchronized: VERSION, package.json, mobile app version
  metadata, update links, README variants, and release workflow defaults are
  aligned for 8.0.17.