# Changelog

## 0.16.14 / Pi 0.1.0-poc.22 / DeepSeek Harness 0.1.0-rc.27 — 2026-11-14

- Restore managed Claude Send after verified foreground completion while a background shell remains. Detailed identity/admission now use the same exact-PID observation as Send; new work, unresolved tools, failed reads and identity conflicts still block input.
- Share the native Composer frame/footer proof at preflight and the text/Enter submission boundaries. Recognize the captured Claude Code 2.1.303 completed-shell footer without bypassing draft equality, stash, unknown overlays, approvals or input ownership. No user draft is cleared and no task is replayed.
- Publish coordinated Pi/DSH prereleases pinned to the actual fixed core **0.16.14**, retaining #508 and #512. DSH rc.27 keeps the exact 0.2.2-rc.3 / Cordis 4.1.0 adaptation; both connectors use `next` and DSH `latest` remains rc.24. This adds no Host support or live-model/channel-delivery claim.

## DeepSeek Harness 0.1.0-rc.26 — 2026-11-13

- Adapt the exact DSH 0.2.2-rc.3 / Cordis 4.1.0 package set, Schemastery 3.19.0, separate native executor and raw-JSON batch tool calls. Keep exact ownership, validation and callback admission guards.
- Pin the already-published AKK core 0.16.13, preserving #508 without distributing the older private development core. Publish this independent connector on `next`; core, Pi and the separate DSH `latest` recommendation are unchanged.
- Provide a reproducible clean-install List/Status smoke using real Host packages and synthetic discovery. The six older accepted versions, real model/task completion delivery, downgrade and cross-version callback handoff were not revalidated.

## 0.16.13 / Pi 0.1.0-poc.21 / DeepSeek Harness 0.1.0-rc.25 — 2026-11-10

- Deliver accepted Claude terminal foreground results even when a returned Bash background launch keeps the registry in shell state. Detached monitors inspect the exact bound PID; a newer unfinished prompt, unresolved tools, stop hooks and identity conflicts still block completion or further input. Foreground completion does not certify background build success.
- Persist completion diagnostics and timeout uncertainty notices while accepted Claude terminal observation continues. Safely resume only eligible legacy Claude timeout stalls after original binding/ledger/generation/route checks, without resending task text. Other executor timeout policies remain unchanged.
- Keep managed callback retries durable through transient failures. Unknown-outcome replay requires a trusted idempotent-delivery capability and an authorized receiver; preserve immutable envelopes, leases, permanent failures and Close/supersession fences. DSH declares this capability only with its existing persistent receiver ledger and flush-before-ack recovery.
- Publish coordinated Pi/DSH connectors pinned to core **0.16.13**, with synchronized Skills and unchanged Host ranges. Both new prereleases use `next`; DSH `latest` remains the separately recommended rc.24/core 0.16.12.

## 0.16.12 / Pi 0.1.0-poc.20 / DeepSeek Harness 0.1.0-rc.24 — 2026-11-08

- Adapt reviewed Codex CLI/app-server **0.167.0** profiles for status, model/permission controls, blocking and asynchronous questions, and exact paginated observation. Validate the existing native task contracts against the actual 0.167.0 pair; retain old reviewed profiles and mixed-pair restrictions.
- Respect the new person-only `humanCommand` approval contract: do not claim human-approval capability or answer person-only/unknown command kinds. For 0.167+ screen-only command dialogs, require the structured native kind through the backend or manual handling in the original CLI. Ordinary backend approvals remain available.
- Preserve exact ownership, uncertain-input protection, 800-code-point public progress, 720-minute hard monitoring, existing inactivity/receipt semantics and List v5 budgets.
- Publish coordinated Pi/DSH connectors pinned to core **0.16.12** with synchronized Skills, unchanged Host ranges and prerelease `next` tags. ClawHub submission acceptance is distinct from later scanning/public availability.

## 0.16.11 / Pi 0.1.0-poc.19 / DeepSeek Harness 0.1.0-rc.23 — 2026-11-02

- Adapt reviewed Codex CLI/app-server **0.166.0** terminal profiles for status, model and permission controls, blocking questions and exact paginated observation. Preserve frontend/backend identity separation, folder-trust handling and unknown-send protection.
- Treat Markdown-rendered async choices as ambiguous when terminal evidence cannot prove their original labels; structured backend answers retain native IDs. Redact the new ChatGPT workspace status field. Accept existing optional flat item lifecycle timestamps without substituting task identity or claiming completion.
- Default ClawHub publication to finish after a confirmed pending attempt acknowledgement. Preserve the receipt and distinguish accepted submission from public scan/download availability; optional waiting remains available and uncertain uploads are never replayed.
- Publish coordinated Pi/DSH connectors pinned to core **0.16.11**, retaining existing Host ranges and prerelease `next` tags.

## 0.16.10 / Pi 0.1.0-poc.18 / DeepSeek Harness 0.1.0-rc.22 — 2026-10-31

- Recognize the complete framed multiline prompt in supported Claude Code terminal questionnaires, including the custom-text entry state. Preserve all prompt rows, semantic option selection and the original screen fingerprint instead of mistaking a wrapped question row for an option.
- Require contiguous framing and a blank boundary before options; retain header, footer, numbering, cursor, option-count and input-ownership checks. Check sensitive words across line wraps. Unproven shapes and multi-select mutation remain manual; this does not add Claude native-peer response support.
- Include the PR #494 captured-question regression and its existing isolated Claude 2.1.295 terminal-response evidence. No new production task or external-channel delivery claim is made by this release.
- Publish coordinated Pi and DSH connectors pinned to core **0.16.10**, retaining their existing Host compatibility ranges, synchronized Skills and prerelease `next` tags.

## 0.16.9 / Pi 0.1.0-poc.17 / DeepSeek Harness 0.1.0-rc.21 — 2026-10-31

- Explain Codex delivery failures with allowlisted stage, decoded target, dispatch certainty, fallback outcome and native RPC method/code. Preserve diagnostics and recovery guidance in durable Send receipts without exposing raw backend errors, prompts or private paths.
- Add independent backend/fallback health observations to compact List v4 and v5. A bounded, private, 24-hour advisory cache can identify an exact mismatch with a recent complete inventory; it never authorizes, rejects, reroutes or automatically resends work.
- Preserve opaque native identifiers, fresh execution checks, transport pinning and uncertain-send recovery. Ordinary List adds no full Send preflight or native subscription, and unknown acceptance still requires receipt inspection rather than blind retry.
- Publish coordinated Pi and DSH connectors pinned to core **0.16.9**, keeping their existing Host compatibility ranges and prerelease `next` tags.

## 0.16.8 / Pi 0.1.0-poc.16 / DeepSeek Harness 0.1.0-rc.20 — 2026-10-30

- Add an explicitly versioned compact List v5 for updated OpenClaw, Pi and DSH connectors. Omit repeated usage prose and duplicate IDs while retaining exact selectors, readable states, dynamic action inputs and structured blockers. Keep the existing whole-response budgets and complete pagination.
- Preserve v4 for existing generic Host SDK and MCP consumers; allow `listProjectionVersion: 4 | 5`, bind continuations to that format and reject unsupported versions before discovery. Raw CLI output, action contract 35, private authority and execution checks are unchanged.

- Publish coordinated Pi and DSH connector updates pinned to core **0.16.8**, retaining their existing Host compatibility ranges and `next` tags. Document separate synchronization of an existing personal OpenClaw Skill without reinstalling the plugin or restarting the Gateway.
- Correct test fixtures for restrictive caller umasks and opaque Desktop identity ordering; retain the permission and connection assertions.

## 0.16.7 / Pi 0.1.0-poc.15 / DeepSeek Harness 0.1.0-rc.19 — 2026-10-29

- Reduce repeated discovery work within one CLI command: share in-flight Claude reader and terminal probes, isolate the memo between commands, inspect known Claude targets directly, and bound parallel process checks. Execution identity and input fences remain fresh and are never cached as authority.
- Make default List a lightweight inventory. Detailed approval/composer/task scans are deferred to Status, explicit `--approval-scan` / `noApprovalScan: false`, and execution preflight. Deferred or unknown observations are not proof that a session is input-ready. Keep unavailable or unresolved operations explicit.
- Preserve the existing default-list treatment of verified unstarted Codex candidates. Only ambiguous same-home/workspace groups receive additional snapshot verification; unavailable evidence keeps candidates visible, and task bodies are excluded from the inventory.
- Keep detailed Claude List confidence consistent with the exact native identity resolved during that same command. This presentation update does not grant cached input authority or promote unavailable identity evidence.
- Publish coordinated Pi and DSH connector updates with exact core **0.16.7** dependencies and synchronized Skill guidance. Existing Host compatibility ranges, callback ownership, persistent recovery and prerelease `next` tags remain unchanged.
- Preserve the PR #484 measurement record as development evidence. Its environment-specific read-only timing samples are not universal latency guarantees; complete Status includes additional safety checks and can remain slower than direct inspection.

## DeepSeek Harness 0.1.0-rc.18 — 2026-10-29

- Add DSH connector author/keywords and a clearer installation/discovery entry. Keep `next` for the prerelease connector and exact core **0.16.6**; no core or Pi release or runtime compatibility expansion.
- Publish an AKK-maintained format-1 market index using exact published npm versions and reviewed DSH peer ranges, avoiding the old bare-package `latest` selection. It is an opt-in third-party source, not a default official market or endorsement.
- Repair npm README cross-directory links and clarify POSIX resident-Web, prerelease, clean-restart, approval and callback boundaries. Reuse the existing AKK demo with its actual controller environment identified.

## 0.16.6 / Pi 0.1.0-poc.14 / DeepSeek Harness 0.1.0-rc.17 — 2026-10-28

- Align Claude List offers with managed Send and native thread-lifecycle admission. Check the applicable transcript-boundary and exact idle-reader requirements, retain bounded readiness diagnostics in compact List, and provide actionable recovery guidance. Execution still captures fresh evidence; List observations do not grant cached input authority.
- Reuse safe Session reattachment for Claude New thread, including Clear’s existing new-thread operation, after a conclusively inactive prior process. Validate the original displayed token and pre-input state under the terminal/Store locks, preserve Session history, advance the binding generation, then refresh and compare native-thread and process-incarnation identity.
- Refuse reattachment when a source transition journal is unresolved, including one appearing during asynchronous ownership verification. Preserve live/unknown-owner, pending-Turn, cross-Store, revision/CAS, approval and draft safeguards; managed operations never silently fall back to physical input. A resumed native thread UUID is distinct from process incarnation and may legitimately remain unchanged.
- Retain public parameters, action contract **35**, compact List **v4**, Watch schema **3** and Store writer protocol **11**. This release adds no new live destructive-lifecycle or external-channel delivery claim.
- Release Pi **0.1.0-poc.14** and DeepSeek Harness **0.1.0-rc.17**, both pinning core **0.16.6** with synchronized Skills. Core remains on `latest`; connectors remain prereleases on `next`, with unchanged Host version ranges.

## 0.16.5 / Pi 0.1.0-poc.13 / DeepSeek Harness 0.1.0-rc.16 — 2026-10-28

- Distinguish Claude List scans that were explicitly skipped (`screen_not_scanned`) from captures that failed or returned no screen (`screen_unavailable`). Do not misdiagnose either case as an unrecognized Composer; provide the applicable rescan or capture recovery guidance.
- Preserve existing Composer, draft, stash, foreground-work and exact input-authority checks. Missing screen evidence still disables Send; a successful fresh scan can restore the existing action offer.
- Retain action contract **35**, compact List **v4**, Store writer protocol **11**, Watch schema **3**, and existing Codex and managed-Send behavior.
- Release Pi **0.1.0-poc.13** and DeepSeek Harness **0.1.0-rc.16**, both pinning core **0.16.5** with synchronized Skills. Core remains on `latest`; connectors remain prereleases on `next`, with unchanged Host version ranges.

## 0.16.4 / Pi 0.1.0-poc.12 / DeepSeek Harness 0.1.0-rc.15 — 2026-10-28

- Adapt the reviewed macOS Codex CLI/app-server **0.165.0** pair for native status, models, permissions and question controls. Keep direct-backend operations contract-probed and distinguish the verified frontend version from the backend version; mixed older frontends do not inherit new terminal-write authority.
- Recognize the exact native `GPT-6.1 Terra` display label and model ID across model pickers, effort headers and idle footers, without guessing unknown labels or fixed option indices. Accept the observed native single-column transcript bullet behind the exact styled Full Access confirmation.
- Detect Codex's persistent folder-trust dialog as blocked and require a manual decision in the original CLI. With an exact frontend association, List and Send retain this boundary even when the shared backend is idle; pre-input revalidation prevents a newly appearing dialog from receiving task input. This fixes an existing recognition gap, not a new claim that 0.165 introduced trust dialogs.
- Preserve exact native task identity, bounded public progress, default 720-minute monitoring, managed-terminal inactivity limits and callback/response deduplication. Record isolated native-task checks and their limits in the [0.165.0 compatibility review](docs/codex-0.165.0-compatibility.md); no new Desktop or external-channel delivery claim is made.
- Release Pi **0.1.0-poc.12** and DeepSeek Harness **0.1.0-rc.15**, both pinning core **0.16.4** and the synchronized Skill. Core remains on `latest`; connectors remain prereleases on `next`, with unchanged Host version ranges.

## 0.16.3 / Pi 0.1.0-poc.11 / DeepSeek Harness 0.1.0-rc.14 — 2026-10-28

- Identify the exact running Codex native executable behind a verified npm Node launcher. Check process generation, forwarded arguments and mapped file identity before using its reported version; never substitute an unrelated executable from PATH. Fresh observations can recover existing versionless activity Watches without changing their saved anchors.
- Recover DSH callbacks across supported Web Host restarts within the same canonical Profile/Store scope. Persist controller ownership and prepared/accepted receipts; resolve and verify the original persisted Session, use the current trusted helper/socket/token, and acknowledge only after Session flush. Keep command identity separate from recovered callback aliases.
- Add an internal opt-in callback recovery catalogue with exact authorized route identities. Skip unowned routes before claiming delivery; explicitly adopt pre-fix Watch IDs and verified historical Profiles rather than scanning temporary files or inferring authorization from a session ID.
- Preserve process/input fences, Store authority, exact task attribution, original envelopes, deadlines and deduplication. Do not reset permanent or uncertain delivery outcomes. Older Hosts without the required Session restore/flush APIs retain live-session-only behavior; OpenClaw's default transport is unchanged.
- Keep action contract **35**, compact List **v4**, Watch schema **3**, Store writer protocol **11** and public tool parameters. Recovery does not turn stable idle into exact task success or solve reconciliation latency. The upstream live restart evidence covers Codex terminal activity; other producers have automated regression coverage, not new live-channel validation.
- Release Pi **0.1.0-poc.11** and DeepSeek Harness **0.1.0-rc.14**, both pinning core **0.16.3** with synchronized Skills. Core remains on `latest`; both connectors remain prereleases on `next`, with unchanged Host version ranges.

## 0.16.2 / Pi 0.1.0-poc.10 / DeepSeek Harness 0.1.0-rc.13 — 2026-10-27

- Allow degraded terminal-activity Watch creation without optional native process UUID or birth metadata. Reuse Claude's independently observed physical OS birth when available, retain every captured process fence, and report incomplete evidence instead of claiming exact task completion. Do not mix OS birth with Claude's UTC process-start value or substitute UUID namespaces.
- Recover missing process workspace metadata from the selected terminal's absolute directory. Relative paths remain invalid, and a new Watch is still refused when neither source supplies an absolute workspace; no placeholder directory or new nullable persisted record is introduced.
- Distinguish matching identity, proven mismatch and temporarily unavailable evidence during fallback observation. Missing or throwing reads keep pending observation retryable; independently proven terminal, PID, endpoint, process-incarnation or directory changes still terminate it. Unknown evidence does not authorize interaction input.
- Preserve exact durable-completion precedence, task/request attribution, Store and callback ownership, deadlines and notification deduplication. Best-effort terminal activity remains notification-only. This release does not change recovery of already-existing exact Watches after a Host restart or notification outbox recovery.
- Retain action contract **35**, compact List **v4**, Watch schema **3**, Store writer protocol **11** and public tool parameter shapes.
- Release Pi **0.1.0-poc.10** and DeepSeek Harness **0.1.0-rc.13** with exact core **0.16.2** dependencies and synchronized Skills. Core uses `latest`; connectors remain prereleases on `next`, with unchanged Host compatibility requirements.

## 0.16.1 / Pi 0.1.0-poc.9 / DeepSeek Harness 0.1.0-rc.12 — 2026-10-27

- Explain what each List entry can do, why input or monitoring is unavailable, and the applicable next step. Derive bounded usage guidance from current action offers, capabilities, activity and blockers; preserve it in compact and shortened rows without changing the overall Host response budget.
- Recheck unresolved Claude native identities once per List scan with a fresh reader snapshot. Explain verified foreground-window evidence separately from background workers and independently offered physical terminal input. Matching project directories or registry entries do not establish native task ownership or authorize input.
- Preserve an executable `terminal_user_explicit` Send on an explicitly selected terminal even when native identity is unresolved. Keep private authority, process identity and Store fences internal; native acceptance and completion remain unproven on this route. Ordinary managed failures never silently downgrade, and uncertain input is not replayed.
- Refuse Claude physical Send before input when a visible draft, occupied native stash, active foreground turn or unrecognized footer makes the Composer unsafe. Recognize the Claude 2.1.295 footer and inline `new task? /clear … · › stashed` notification. A shell count or empty prompt alone does not prove foreground completion.
- Remove the destructive sentinel/stash/erase preparation. After a fresh empty-Composer check, use at most one non-destructive `Ctrl+S` restore probe; stop without task text or Enter if content appears or the probe is uncertain, leaving the restored draft for manual handling. Do not clean up after task text or Enter. This is not an atomic keyboard lock or a guarantee against simultaneous human input or an unprocessed restore key; see the Claude compatibility notes.
- Advance the action contract to **35**; retain compact List projection **v4**, Store writer protocol **11**, public request parameters and ordinary managed Send behavior. Update recovery guidance and synchronized Skills.
- Release Pi **0.1.0-poc.9** and DeepSeek Harness **0.1.0-rc.12** with exact core **0.16.1** dependencies. Core remains on `latest`; both connectors remain on `next`, with unchanged Host compatibility requirements.

## 0.16.0 / Pi 0.1.0-poc.8 / DeepSeek Harness 0.1.0-rc.11 — 2026-10-26

- Separate native-thread Store authority recovery (`transfer_store_authority`) from managed Session binding reconciliation (`reconcile_binding`), and expose the applicable recovery action consistently on native and terminal rows. Keep the runtime ledger globally shared so different Hosts cannot independently claim the same native thread; record absolute Store identity, Host identity, owner PID, process start identity and instance nonce.
- Transfer authority through a durable journal (`prepared → source_retired → target_created → committed`), retiring the source before creating the target. Validate Store owner identity against the registry and live process generation; retain active-owner rejection, crash recovery, concurrent-claim exclusion and stale-writer fencing. Recovery itself sends no terminal input. Offer automatic recovery only with positive evidence for an eligible abandoned ephemeral Store; legacy or ambiguous ownership requires explicit recovery. Set `send_after_transfer` only when `automaticEligible` is true, and never infer `maintenance_acknowledgement`.
- Preserve each invocation's configured agent home and terminal discovery options during recovery identity checks, including concurrent Host calls; do not silently fall back to the default home.
- Upgrade Store writer protocol from 10 to **11**, keeping Store format **1**. Upgrade the public action contract from 32 to **33** and compact List projection to **v4** so recovery actions retain their displayed private authority. Update operator guidance and all generated Skills with the two conflict types and their recovery paths.
- Remove the generic 90-second `runCliAsync` relay deadline from `send`, `delegate` and `respond`. It could kill a dispatcher after text injection but before Enter dispatch, leaving `terminal_message_acceptance_uncertain` and a draft in the composer. Submission phase deadlines, explicitly supplied relay deadlines and Host cancellation still apply. Claude's `permissionMode=default` (`manual mode`) governs tool approvals and does not block task input; two consecutive live manual-mode Sends now reached Enter dispatch and acceptance, with completion and callback delivery verified.
- Coordinate core **0.16.0**, Pi **0.1.0-poc.8** and DeepSeek Harness **0.1.0-rc.11** with exact core dependencies, aligned lockfiles, runtime versions and synchronized Skills. Core remains on `latest`; both prerelease connectors remain on `next`, with unchanged Host compatibility requirements. Full/release validation remains the publishing machine's immediate pre-publication gate.

## 0.15.0 / Pi 0.1.0-poc.7 / DeepSeek Harness 0.1.0-rc.10 — 2026-10-23

- Prefer an exact controllable terminal for new Claude Code Sends, automatically creating a managed Turn with completion monitoring and supported approval actions. Use the native inbox when no controllable counterpart exists; keep Codex backend-first and preserve existing task routes, receipts and pending interactions. Busy terminals, conflicting ownership and Store failures never authorize a second send through another connection.
- Expose Claude's eligible cancellation, inspection, thread lifecycle, model and managed interaction controls through unified List and Status. Preserve the original Turn for approvals and answers, exact process and prompt checks, and single-use response authority. Claude permission-mode switching remains unavailable.
- Recognize successful Stop hook summaries without discarding independently proven task completion. Keep hook errors, prevented continuation, background work and ambiguous task chains unproven; native Watches notify about exact-task waiting changes without gaining approval authority.
- Support the standard `claude` executable and configured wrappers such as `tclaude` through the same adapter. Document explicit native sender permission classes, agent-side command-line verification and `from-mode` envelopes; this metadata neither changes receiver permissions nor resends held messages. Claude Code `2.1.295` and `2.1.296` are live-tested observations, not minimum-version requirements.
- Let complete, unlisted Claude versions attempt compatible transcript, status, model and questionnaire contracts instead of rejecting them solely for lacking a regression profile. Preserve actual-version identity, runtime schema/UI checks, fresh prompt/catalog authority and verified postconditions; missing versions and unknown or incompatible structures remain unavailable.
- Preserve explicit physical-terminal Claude Sends, including draft replacement and human handoff, while ordinary new Sends prefer managed delivery. Keep exact terminal-token revalidation and original-route deduplication.
- Publish Pi `0.1.0-poc.7` and DeepSeek Harness `0.1.0-rc.10` with exact core `0.15.0` dependencies and synchronized Skills. Both remain on `next`; Host compatibility requirements are unchanged.

## 0.14.17 / Pi 0.1.0-poc.6 / DeepSeek Harness 0.1.0-rc.9 — 2026-10-23

- Adapt Codex CLI 0.164.0 terminal controls to the observed `default` effort label and single-row contextual composer footer without treating an unset effort as a known model setting. Add reviewed status, permission and question profiles while retaining exact identity, input ownership and uncertainty guards.
- Keep 0.164.0 terminal asynchronous-question selection limited to proven plain-text titles. Unproven Markdown candidates remain ambiguous instead of being excluded from identity matching; native structured answers remain available independently.
- Verify the 0.164.0 CLI/backend pair in isolated sessions. Keep exact-turn selection independent of new native read receipts, and preserve bounded public progress, monitoring deadlines and notification deduplication. See the [operation-specific review](docs/codex-0.164.0-compatibility.md) for live evidence and retained limits.
- Release Pi `0.1.0-poc.6` and DeepSeek Harness `0.1.0-rc.9` with exact core `0.14.17` dependencies and synchronized Skills. Both connectors remain on `next`; existing Host compatibility boundaries are unchanged.

## 0.14.16 / Pi 0.1.0-poc.5 / DeepSeek Harness 0.1.0-rc.8 — 2026-10-23

- Fold unnamed Codex CLI threads with no materialized task history from default List when one established same-project thread is available and identity/attention guards permit it. Keep exact IDs and first-task actions in diagnostics, and restore ordinary display when a task starts. This is a display preference, not proof that an empty thread is abandoned or authorization to redirect a message.
- Keep sole empty threads, named threads, exact terminal attachments, multiple established sessions and identity conflicts visible. Report folded candidate counts and a diagnostic query; distinguish backend reachability from unverified frontend presence.
- Publish Pi and DeepSeek Harness connectors alongside core, with both dependencies pinned to `0.14.16`. Keep the connectors on npm `next` and the existing Host compatibility boundaries; no tclaude preview changes are included.
- Require coordinated core/Pi/DSH release preparation and registry verification for future core releases. Updating core alone does not upgrade an already-installed connector; install or update the connector's `@next` release to receive its new bundled core dependency.

## Pi connector 0.1.0-poc.4 / DeepSeek Harness connector 0.1.0-rc.7 — 2026-10-21

- Pin both independent connectors to published AKK core `0.14.15`, replacing Pi `0.14.7` and DSH `0.14.8`; align lockfiles, runtime versions and the canonical Skill/27-tool handshake. Publish on `next` without moving either `latest` tag.
- Expose conversation-only List and the separate bounded Watches query; inherit the core's protected 48-hour completed-observation cleanup and Store writer protocol 10. Do not migrate callback routes or existing observation deadlines.
- Retain the established Pi and DSH Host compatibility policies, DSH-specific Store, approval boundaries and callback deduplication. Validate the actual pinned core, native Host tool/schema wiring and isolated List/Watches forwarding; no new live-model or external-chat delivery claim.

## 0.14.15 - 2026-10-21

- Determine local Herdr capabilities per operation instead of rejecting unfamiliar versions. Retain `0.8.0` / protocol `19` and `0.9.5` / protocol `22` as tested baselines, with socket, terminal and process identity checks before input.
- Probe read capabilities without terminal input; require a matching CLI schema declaration or verified baseline behavior for writes. Keep untested servers without input evidence read-only, reject incompatible declarations without fallback, and preserve uncertainty after dispatch. Doctor reports installation readiness separately from unprobed live capabilities.

## 0.14.14 - 2026-10-18

- Attempt all implemented Codex Desktop operations after an app update instead of blocking writes on an exact version allowlist. Preserve tested-build metadata separately from current action availability.
- Apply the same policy to conversation creation through the installed bundled backend; retain bundle provenance, real initialization, exact owner/task/request/revision checks and explicit protocol errors.
- Keep uncertain outcomes unreplayed, expired interactions rejected and existing Watch/callback identities intact. This does not add unsupported cold-loading/resume operations or claim future protocols are verified.

## 0.14.13 - 2026-10-18

- Separate conversation discovery from monitoring: List retains currently discoverable CLI/Desktop entries and current action authority, while `watches` provides bounded recent monitoring and unresolved records.
- Default Watch queries to 24 hours with pagination. Keep active and unresolved observations visible outside the window; list retained managed Turns separately for recovery.
- Add bounded 48-hour cleanup for healthy completed Watch bodies, preserving minimal durable deduplication tombstones, pending delivery/interactions, existing deadlines and native history.
- Advance the Store writer fence to protocol 10 so older writers cannot recreate pruned requests. This changes the writer manifest, not existing tasks or deadlines; rollback requires a coherent backup or a compatible writer.

## 0.14.12 - 2026-10-18

- Prefer the verified backend as the default CLI entry for a unique same-agent/project discovery pair. Keep its exact conversation ID, title, status and actions so controllers can use one entry without choosing a transport. Terminal candidates remain available in diagnostics.
- Preserve proven alias controls, direct-only/terminal-only discovery, multiple native sessions and known identity conflicts. Keep terminal attention and management/recovery records visible; never copy unverified terminal authority into a backend or redirect an existing terminal selector by cwd.
- Retain bounded List pagination, backend-first routing, busy/blocked/uncertain protections, existing Watch deadlines and callback receipts. This release does not change coding-agent compatibility profiles or publish independent Pi/DSH connectors.

## 0.14.11 - 2026-10-18

- Keep independently verified Codex CLI backends selectable in default List when a same-project terminal has no proven exact alias. Preserve CLI/Desktop presentation, exact identity rules and bounded pagination; connection counts do not imply independent tasks.
- Use List's authoritative Send projection for unified terminal routing, preserving its explicit user authority and final process, endpoint, approval and input checks. Do not force input into history views or redirect by cwd.
- Separate proven pre-executor preparation rejection from uncertain execution in route journals. Keep the original route/message identity, retain concurrent or legacy uncertainty, and never replay old notifications or automatically retry across transports.
- Validate with isolated Host/List/router/Store regressions and the formal release gate. No existing user thread is used for test sending; this release does not install itself locally or publish Pi/DSH connectors.

## 0.14.10 - 2026-10-18

- Fix explicit Watch creation when backend-first routing selects an exact terminal: preserve the terminal argument required by the Watch adapter. This covers Host `conversation_id` / `terminal_id` inputs and CLI `watch-terminal --terminal`, including Codex and Claude terminal fallback.
- Keep available native backends preferred and preserve terminal/process identity checks, controller ownership, exact task anchors, callback routing and duplicate-observation handling. Existing Watch records and deadlines are unchanged.
- Include the Desktop build 20398 compatibility and bounded, paginated Host List improvements introduced in 0.14.9. No independent Pi/DSH connector release is required.

## 0.14.9 - 2026-10-18

- Support macOS Codex Desktop `26.1007.71326` / build `20398` through its original IPC owner: creation, Send, bounded public Status progress, exact Watch, command/file approvals, blocking/asynchronous answers, model/permission settings and exact interruption. Retain the separately reviewed `13536` and `20156` capability profiles; unknown builds remain read-only.
- Require a coherent Desktop application/build/bundled-backend tuple for creation. Preserve owner, task, request, freshness and one-dispatch checks; reconcile uncertain acceptance without resending.
- Stop reporting a missing sidebar in an additional CLI-only Codex home as a broken Desktop layout. Actual missing, invalid or unreadable Desktop layouts remain explicit, and saved sidebar membership does not imply a live owner.
- Bound controller-facing List output before JSON serialization. Compact projection v3/action contract 31 puts conversations first, retains active or unresolved attention, and summarizes healthy ended history. Add `listView`, `listCursor` and `listLimit` for complete history/all access; preserve raw CLI diagnostics. Every page retains exact IDs, continuation and attention counts under a whole-response budget. See [List output and history](docs/list-output.md).
- Leave existing Watch deadlines, callback records, idempotent Send and recovery semantics unchanged. This release does not publish or upgrade the independent Pi/DSH connectors.

### Validation boundaries

- Dedicated Desktop real-task checks covered creation, public progress, command/file allow and reject, Unicode asynchronous answers, a two-question Plan request, settings readback, exact cancellation and a subsequent successful task. Nine original native tasks produced fifteen unique local attention/completion acknowledgements, each accepted once. No existing business conversation was used, and no external chat delivery is claimed.
- List validation used thousands of synthetic ended/attention records and actual local discovery through the installed OpenClaw Codex harness at its minimum 16,000 weighted-character budget. Current/history/all pages remained valid JSON without lost or duplicate IDs. This bounds returned context, not native discovery cost; callers must follow the returned pagination arguments.

## DeepSeek Harness connector 0.1.0-rc.6 — 2026-10-17

- Support DeepSeek Harness `0.2.1-rc.2`, with its actual Cordis `4.0.5` and SDK dependencies. Preserve the previously reviewed Host versions and reject unknown or mixed runtime package sets.
- Pin AKK core `0.14.8`, keeping the installed runtime, canonical Skill and capability handshake aligned, including Desktop question answers.
- Isolate the default DSH Store from other Hosts so a foreign worker cannot claim its native callbacks. Preserve explicit Store paths and existing records without migration or replay.
- Verify current and previous SDK fast tests, native tool execution and callback consumption/deduplication. Publish only the independent DSH connector on npm `next`; core, Pi and npm `latest` are unchanged. See the [compatibility record](docs/pi-dsh-compatibility.md#dsh-021-rc2-compatibility--2026-10-17).

## 0.14.8 - 2026-10-14

- Enable blocking and asynchronous question answers on macOS Codex Desktop `26.1007.30912` / build `20156`, independently of model/permission settings and cancellation. Use the advertised Respond action from fresh conversation or exact Watch Status.
- Preserve exact task/request identity, one-dispatch response records and native answer confirmation. Real Desktop validation covered an asynchronous choice, free text, and a two-question Plan request; original tasks consumed the answers and completed. Local attention/completion callbacks were verified, not external chat delivery.

## Connector releases - 2026-10-14

- Publish Pi connector `0.1.0-poc.3` and DeepSeek Harness connector `0.1.0-rc.5` independently under npm `next`; neither changes the core `0.14.7` version or promotes a connector to stable `latest`.
- Pin both connectors to published AKK `0.14.7`, aligning the installed HostAdapter, lockfiles, 26 registered tools and canonical Skill handshake. The connectors now expose that core's direct CLI/Desktop capabilities under the existing per-target limits.
- Support Pi `1.2.0`, retaining the reviewed `0.84.4` runtime. Use the actual Host version in the callback profile, adapt the tool execution context, and support exact conversation/Watch approval confirmations with explicit allow/reject labels.
- Adapt DSH `0.2.0-rc.2` and separately reviewed `0.2.1-alpha.2` package contracts: coherent Host/Cordis peers, AKK-specific message source typing, and current schema/Skill validation. DSH `latest` remains a release candidate, not a stable release.
- Preserve exact live controller ownership, callback deduplication and conservative recovery: an accepted callback is not a model-consumption or external-chat-delivery guarantee; old routes do not migrate automatically to a restarted Host.

See [connector compatibility and validation](docs/pi-dsh-compatibility.md) for the version matrix and evidence boundaries.

## 0.14.7 - 2026-10-14

- Enable explicit command and file approvals on macOS Codex Desktop `26.1007.30912` / build `20156`: allow once or reject from the controller, through the original Desktop conversation.
- Advertise approvals independently from broader native controls across List, Status, Watch and interaction notifications. Question answers, model/permission changes and cancellation remain unavailable on this build; the reviewed build `13536` retains its existing controls.
- Preserve exact owner, task and pending-request checks, one-dispatch response records and effect verification. An IPC acknowledgement alone does not confirm approval; consumed or uncertain responses are not blindly replayed.

### Validation boundaries

- A dedicated Desktop conversation verified real semantic Send/Status/Approve for command allow/reject and file allow/reject, including successful execution or file changes after approval and absent side effects after rejection. Local attention/completion callbacks were accepted once each; no external chat-delivery claim is made.
- This release adds no persistent authorization rules or full-access mode changes.

## 0.14.6 - 2026-10-13

- Present CLI and Desktop conversations together, with Codex/Claude Code as the agent type. Keep transport details in diagnostics instead of showing backend and terminal connections as separate user-facing categories.
- Group one-to-one same-agent/project discovery candidates into the original terminal display row without copying native identity, status or permissions. Preserve separate rows for known conflicts and multiple candidates, and retain direct-only CLI discovery. Expand all unassociated connections with `terminalDebug` / `list --terminal-debug`.
- Preserve exact special-control targets, managed recovery records and independent Watch receipts in the compact list. Display grouping never changes backend-first routing, task ownership, uncertain-send handling or callback deduplication.

## 0.14.5 - 2026-10-13

- Add a separate Desktop Create tool for a new conversation in an exact existing project or outside projects, with an optional first task. Create zero-turn metadata, hand the same UUID to Desktop, then use its verified owner for real task submission and automatic monitoring.
- Persist creation identity and stage receipts. Continue only the same operation after incomplete handoff or uncertain delivery; preserve the original first-task identity and callback route without creating a replacement or replaying uncertain task text.
- Add a capability-specific macOS Desktop `26.1007.30912` / build `20156` creation/Send profile. Native approval, question-answer, model/permission and cancellation controls remain unavailable on this build; the previously reviewed build `13536` retains its existing controls.

### Validation boundaries

- On macOS Desktop build `20156`, the real semantic tool and built CLI verified project/projectless creation, zero-turn blank ownership, first-task submission through Desktop IPC, exact completion, and one accepted callback to an isolated local receiver. No external chat-delivery claim is made. Desktop applied Read Only/on-request after handoff; creation does not imply write access.

## 0.14.4 - 2026-10-12

- Send the first task directly to an exactly identified, already loaded, idle Codex CLI thread whose history is still empty. Use the original thread and owner; no manual seed task, replacement process, or terminal input is required.
- Defer native subscription only for the verified empty-history case, then bind observation and interactions to the accepted task as its history becomes available. Keep acknowledged submissions separate from verified acceptance, and never replay uncertain task text.
- Keep List Send/Watch capabilities consistent across exact backend and terminal aliases. Persist preflight failures under the same message-identity lock as Send so concurrent failures cannot overwrite an accepted task or trigger a fallback resend.
- Report proven pre-submission failures as not sent, without starting a monitor or callback. Preserve existing deadlines, idempotent Send, callback deduplication and the public Status progress budget.

### Validation boundaries

- Verified two isolated macOS Codex CLI 0.162.1 + shared app-server 0.162.1 empty-thread tasks: a simple first reply and a first task requiring a harmless command approval. Both used the original CLI thread, verified execution/results and produced one local completion acknowledgement; repeated Send and observer reconnection did not duplicate execution or completion.
- Delayed history, lost acknowledgements and concurrent preflight failures are covered by regression tests. These checks do not claim a new live WeChat delivery test. Desktop live verification remains intentionally skipped; native new/clear/cold-resume support is unchanged.

## 0.14.3 - 2026-10-11

- Add direct control of existing Claude Code CLI sessions on macOS without tmux, Herdr, Claude plugins, hooks, special launch flags or a replacement agent. Discover exact live sessions, send idle tasks, read bounded public progress/results and observe exact completion or exit. Requires Python 3 on the controller side; verified with Claude Code 2.1.296.
- Prefer the Claude native route for supported basic operations. Preserve eligible exact terminal routes for existing special operations; unsupported approvals, questions, model/permission changes, cancellation and lifecycle controls remain unavailable without an appropriate terminal route. Busy or uncertain submissions never silently fall back or resend.
- Retry a callback only when structured transport evidence proves it was not submitted. Recognize the reviewed OpenClaw opening-handshake failure, retain request-phase evidence and original notification identity, and preserve the existing bounded backend retry budget. Unknown or conflicting error schemas cannot authorize replay.
- Make one bounded read-only exact-run check after eligible uncertain callback submissions. Only positive acceptance evidence settles the notification; missing records, query timeouts and malformed acknowledgements do not authorize another send. Historical uncertain notifications are not automatically replayed.
- Preserve callback deduplication across observer restart, concurrent recovery and late definitive receipts. Explain exhausted retry budgets and keep task completion, controller acceptance and downstream channel delivery separate in Status, List and recovery text.

### Validation boundaries

- Claude direct discovery, sending, progress, exact completion and terminal fallback were exercised in isolated local acceptance checks. Native special-control APIs remain outside this first direct adapter; see the [Claude direct guide](docs/claude-cli-direct.md).
- Callback recovery is verified with isolated transport responses and temporary durable stores. No historical callback was replayed, and this release does not claim a new live WeChat delivery test or a guarantee against arbitrarily long Gateway outages.
- Existing Codex CLI/Desktop compatibility boundaries, the 800-code-point Status budget, 720-minute monitoring deadline and terminal-managed 60-minute inactivity window are unchanged. Desktop live verification remains intentionally skipped.

## 0.14.2 - 2026-10-10

- Adapt Codex CLI 0.162.1 native status to the changed usage-page URL without relaxing exact thread, process, version, composer or freshness checks. A rejected status card no longer hides the underlying diagnostic behind a plain-text semantic tool error: native inspection execution failures return structured JSON with an explicit non-retryable outcome.
- Add exact 0.162.1 terminal model, permission, blocking-question and asynchronous-question profiles, including the macOS Control/Shift key glyphs. Keep paginated interaction writes bound to the reviewed 0.162.1 frontend/backend pair; unreviewed pairs do not acquire write authority.
- Recognize 0.162.1's centered Full Access confirmation overlay using exact warning, choice, style and geometry checks; preserve background transcript/composer separation and stop on uncertain input or layout.
- Preserve exact task ownership across compatible native protocol additions, including turn lineage and partial answers. Partial answers cannot become completion evidence or final callback text.
- Report a loaded idle CLI thread with no persisted history without confusing unavailable native subscription with absent thread identity. Keep its Send/permission actions unavailable and pending-interaction count unknown until those paths can be verified.
- Retain the 800-code-point public Status progress budget, shared 720-minute monitoring hard deadline, managed-terminal 60-minute inactivity window, existing deadlines and callback deduplication.

### Validation boundaries

- Verify macOS CLI 0.162.1 + shared app-server 0.162.1 through dedicated live tasks: exact discovery/routing, public progress, automatic/explicit Watch, callbacks, approvals, blocking/async answers, permissions and Recovery. Native terminal model discovery and all four permission modes also pass; model mutation and terminal answer-key injection are not newly exercised live. See the [operation matrix](docs/codex-0.162.1-compatibility.md) for exact route boundaries.
- Pass 2,836 fast tests and the full 3,351-test release gate, including isolated OpenClaw 2026.9.1 compatibility and ClawHub runtime validation/dry-run. Version admission alone is not a compatibility result or a minimum-version promise.
- Desktop live verification is explicitly skipped for this release; its regression coverage and exact supported app/build requirement remain unchanged. Paginated native new/resume remains unsupported.

## 0.14.1 - 2026-10-10

- Add bounded, redacted public progress to Codex CLI backend and Desktop conversation/task Status: the latest commentary and up to two action summaries share an 800-code-point, grapheme-safe budget. Keep exact Watch turn attribution, native timestamps and read failures explicit; List and terminal screen output are unchanged.
- Share a 720-minute default monitoring hard deadline across backend and terminal Send/Watch entry points and service fallbacks. Backend Renew uses the hard-timeout configuration; terminal managed Renew retains its independent inactivity window. Existing deadlines, replay identities and accepted callback records are unchanged.

### Validation boundaries

- Verified public progress during an active task, 720-minute Send monitoring, a single local completion acknowledgement, and idempotent Send on macOS with Codex CLI and shared app-server both at 0.162.1. This does not establish a new numeric minimum or claim all native operations were repeated.
- Desktop behavior is covered by regression tests; Desktop live verification was explicitly skipped for this release. The existing exact supported app/build requirement remains unchanged.

## 0.14.0 - 2026-10-10

### Added

- Control loaded Codex CLI conversations through their shared app-server without tmux, Herdr, or terminal input. Add native discovery, exact task send/Watch, durable completion and interaction callbacks, command/file approvals, blocking and async answers, and per-thread permission settings.
- Discover Codex Desktop conversations alongside terminal sessions, with search, project filtering, pagination, and separate catalog and live-owner evidence. Keep unloaded and creator-unknown conversations discoverable without treating metadata as permission to send.
- Send tasks to an exact existing Desktop conversation through its original owner, record a durable send intent, and bind monitoring to the accepted native task. Repeated message IDs and uncertain submissions never automatically resend task text.
- Add Desktop Status and exact task Watch, with durable completion and manual-attention notifications. Monitoring retains its original native task when a later task starts; stopping a Watch leaves the Desktop task running.
- Add exact-task Recover, observation Renew, managed Close, and manual Retry Callback for direct Codex CLI and Desktop. Separate stopping observation from closing Send management, retain unresolved submission ownership until explicitly closed, and preserve callback identity and uncertain-outcome boundaries without terminal fallback.
- Add Desktop command/file approval decisions and blocking questionnaire responses through the original conversation owner, with exact native request and result evidence.
- Add typed responses for Desktop asynchronous questions in the exact active task, with durable response deduplication, native answer confirmation, and expiry of undelivered obsolete reminders.
- Add per-conversation Desktop Read Only/Default/Full Access settings, explicit model/effort and Plan/default controls, and exact-task cancellation. Verify effective settings instead of treating acknowledgements as success; report the unavailable model catalog explicitly.

### Changed

- Present unified `conversations[]` for Send, Status, and Watch, preferring a verified Codex backend and preserving eligible terminal fallback. Coalesce only exact native identity matches, keep task/interaction routes fixed, and never replay an uncertain mutation through another transport. Preserve raw CLI provider arrays for diagnostics and existing clients.
- Apply backend-first capability selection across Codex conversation commands, including permission reads/updates and native interaction actions. Allow targeted Status and other eligible operations to resolve an idle terminal through the existing exact native status inspection; preserve no-input List, bound task/interaction identities, and terminal-only lifecycle semantics.
- Default Desktop List to persisted expanded sidebar membership, with explicit `desktop_view: "history"` / `--desktop-view history` for the broader historical catalog. Keep unconnected rows visible and report unsupported layouts without falling back to history; live counts describe the current page only.

### Fixed

- Recover missed Codex Desktop asynchronous-question notifications by reading questions from native messages as well as pending requests.
- Preserve exact legacy terminal identifiers and explicit managed-only operations through conversation routing. Keep routing reservations independent of managed Store writer locks so eligible physical Send retains its existing compatibility and lock ordering.

### Compatibility

- Review direct CLI operations on macOS with Codex CLI `0.160.0` and shared app-server `0.162.0`. The local CLI and daemon installation observed at `0.162.1` on 2026-10-10 is not a new end-to-end verification or a numeric minimum; runtime identity and protocol checks determine direct-control availability.
- Require the reviewed macOS Codex Desktop `26.1002.52244` build `13536` for native writes through its private IPC. This exact build is not a minimum-version promise. Loading inactive conversations and launching replacement CLI sessions remain unsupported.
- Preserve the existing tmux and Herdr adapters and their terminal-specific interaction controls.
- Keep Pi and DeepSeek Harness connector releases independent. Their current manifests still pin AKK `0.13.3`; releasing the core package does not upgrade those connector runtimes.

## 0.13.18 - 2026-10-04

- Adapt Codex 0.160.0 async-question Option-key hints while preserving exact versioned input checks and older keymaps.
- Recognize the new native `Workspace (granular)` current permission state so an idle session can select a verified standard preset without treating granular permissions as an existing standard preset.
- Review Codex 0.159.3 and 0.160.0 native status, question, model, and permission profiles; preserve paginated task identity, exact callback, and answer confirmation boundaries.
- Add audited 0.159.3/0.160.0 shared-backend compatibility alongside matching-version pairs, with regression coverage for replay, backend drift, and unreviewed write rejection.

## 0.13.17 - 2026-10-02

- Separate Watch observation and response adapters, Monitor recovery and persistence, and native model-control preparation into focused modules while preserving identity, locking, and single-input boundaries.
- Separate legacy Codex rollout acceptance, completion, human-started task observation, and question attribution; retain existing public entry points and diagnostic outcomes.
- Isolate native screen parsers and SQLite/read-only rollout inventory adapters, and organize tool descriptions separately from execution without changing the public contracts.
- Split large regression fixtures and validation scripts by responsibility while retaining their assertions, test selection mappings, and lifecycle cleanup.
- Lower architecture budgets to four production files over 2,000 lines and 330 default complexity warnings, with tighter Watch and Monitor file limits.

## 0.13.16 - 2026-10-02

- Add Codex permission discovery and explicit session permission changes through the native `/permissions` menu, including automatic Full Access confirmation without an additional user prompt and fresh status/menu verification before sending a task.
- Keep permission menus separate from ordinary Send and generic approvals, and stop automatic retries when terminal input or its result is uncertain.

## 0.13.15 - 2026-10-02

- Attempt Codex exact callback observation through validated runtime UI and paginated read contracts on newer versions; preserve exact task identity across compatible backend upgrades.
- Automatically attach a notification-only terminal-activity Watch when exact Codex or Claude Send preparation is unavailable and physical identity remains safe.
- Preserve strict native answer permissions and refuse uncertain probe input; include sanitized backend-version and operation diagnostics in read errors.
- Use store writer protocol 9 with backward-readable anchors, leaving existing private Watch records intact.

## 0.13.14 - 2026-10-01

### Changed

- Support Codex CLI 0.159.2 and the reviewed 0.159.0 foreground/0.159.2 shared-backend pair. Bind the physical and backend versions separately for paginated Send, Watch, native questions, and answer receipts; reject unreviewed pairs and backend drift.
- Add exact Claude Code 2.1.285 lifecycle, native status, question, and model-control profiles while retaining earlier version checks.

### Fixed

- Recover clipped Codex `/status` cards through bounded native history navigation, requiring a complete card, unique captured overlap, and restoration before using its thread identity. Correct locale-free tmux viewport parsing, Herdr visible-screen reads, and native style checks.
- Continue read-only confirmation of a single Codex async answer for up to 15 seconds after dispatch, including a timed-out RPC, without repeating the answer.
- Recognize Claude's named-session Composer and Bash ask-rule prompt, and read transcript attachments written before their parent records without changing conversation order or weakening identity checks.

## 0.13.13 - 2026-09-30

### Changed

- Extend the paginated task adapter to Codex 0.159.0 for physical Send, exact task Watch, native questions and answer receipts, and completion callbacks.
- Preserve existing string-cursor pagination while accepting 0.159.0 as an independently checked client/backend version.
- Keep the existing 0.158.0 support and the documented 0.157.x limitations. Store writer protocol remains 8 and Terminal Watch schema remains 3.

### Fixed

- Parse Codex 0.159.0 borderless native status output and wrapped fields while retaining exact fresh-card, session, and Composer checks. Separate native activity (including Thinking, Waiting, Compacting, and dynamic headers) and queued-question regions from the status card so active Watch binding and question-answer identity checks can complete. Display text remains outside task identity evidence.

## 0.13.12 - 2026-09-29

### Fixed

- Track Codex 0.158.0 ordinary terminal Send and active-task Watch through exact foreground thread binding and native paginated history, including completion after terminal exit and callback retries.
- Preserve native Plan-mode result text in completion callbacks and verify the real styled Composer before answering async questions.
- Recognize current async question identities and submit answers only to the expected active native turn, confirming the exact durable reply. Handle blocking native question requests and private multi-question drafts through the server's single-response protocol.
- Route paginated Send away from the legacy future-rollout monitor before task input. Keep callback receipts explicit about exact versus activity-only observation.
- Use native bracketed paste for Codex 0.158.0 tmux physical Send so a long single-line request cannot leave its Enter inside the native character-paste burst.
- Adapt 0.158.0 fullscreen status, Composer, command menus, async navigation, and model/effort selection. Bump store writer protocol to 8 so older writers cannot overwrite new task and questionnaire state.

## 0.13.11 - 2026-09-29

### Fixed

- Read Codex 0.157.0/0.157.1's complete fullscreen idle footer as diagnostic activity, while preserving working priority and rejecting clipped or changed surfaces.
- Preserve visible commands and status fields between independently terminated terminal hyperlinks instead of consuming everything between the first and last link.
- Carry the freshly observed Codex version into native-status readiness checks so fullscreen classification uses the same client version as discovery.
- Read Codex's `history_mode` and retain paginated sessions as metadata only. Obsolete JSONL paths cannot supply fork context or native lifecycle candidates; older legacy databases remain supported.

### Compatibility

- Report the known Codex 0.157.0/0.157.1 paginated-history, shared-server, and fullscreen command-menu boundaries explicitly. Refuse managed completion-bridge Send, native thread transitions, and automated native status dispatch before terminal input; keep visible status-card parsing, explicit terminal Send, and best-effort terminal-activity Watch available.
- Keep 0.157.1 questionnaire, typed model-control, and exact native-action profiles unverified. `--no-daemon` does not restore legacy task history.

## 0.13.10 - 2026-09-26

### Changed

- Declare the ClawHub plugin category as `developer-tools` and add `herdr` to its searchable topics.

### Fixed

- Present non-blocking Codex `request_user_input_async` questions to the user and wait for an explicit answer instead of treating `requires_response=false` as permission for OpenClaw to decide.
- Keep monitoring the exact running Codex task for completion when an asynchronous answer has an uncertain outcome, while preserving the one-shot terminal-input fence.
- Allow a bounded read-only recapture after opening the asynchronous question editor so delayed redraws do not require another key press.

## 0.13.9 - 2026-09-25

### Fixed

- Read Claude Code `2.1.282`'s native `/status` panel when it includes the `Auto mode server` row or a bounded `System diagnostics` section. Diagnostic prose is excluded from returned status fields and excerpts.

### Security

- Keep Codex `0.157.0` and Claude Code `2.1.282` on unverified runtime profiles without granting version-bound model-control or questionnaire actions. Claude native status still requires exact session, workspace, and fresh-screen evidence and rejects unprofiled fields or diagnostics.

## 0.13.8 - 2026-09-21

### Added

- Add typed Codex `0.154.0` and `0.155.1` support for running `request_user_input_async` questions across managed Monitor and exact Terminal Watch, while the coding task remains working.
- Project single-select and bounded free-text steps through the existing semantic interaction contract, with explicit `steer_current_turn` and `queue_next_turn` delivery modes and no public raw-key or menu-index surface.

### Fixed

- Recognize the exact styled GPT-6 Astra animated empty Composer during managed Send, including the candidate-acceptance path that previously dropped the running Codex version and unnecessarily downgraded delivery to an unmanaged Watch.
- Keep Host-profile callback notifications pending for their matching runtime instead of allowing an unrelated background worker to claim and permanently fail them.
- Treat only the independently parsed countdown repaint digest as non-semantic when reopening the same collapsed asynchronous question; question, task, terminal, pending-count, and key-binding drift still reject before input.

### Security

- Bind every asynchronous answer to the exact terminal incarnation, native task, current question, semantic option, callback owner, and versioned TUI profile. Unknown or clipped surfaces, competing responders, state drift, and uncertain input remain fail-closed and are never retried automatically.

## 0.13.7 - 2026-09-20

### Added

- Add exact Codex CLI `0.155.1` lifecycle, native `/status`, transition-settlement, blocking questionnaire, and typed model-control profiles based on the installed client and official tagged source.
- Recognize the native user-verification surface as an input-owning, non-approvable prompt that requires direct user handling.

### Fixed

- Recognize Codex `0.155.1`'s exact styled `/model` completion surface without relying on the viewport-wide background paint used by `0.154.0`, so typed model discovery can open, parse, and safely dismiss the native picker.
- Resolve the native model catalog from the exact running profiled Codex executable, while retaining complete `0.154.0` compatibility and rejecting adjacent unverified versions.

### Security

- Bind the new footerless model-control surface to the exact `0.155.1` profile and exact terminal styles. Plain transcript lookalikes, missing or displaced styles, unknown rows, active approvals or questionnaires, and terminal/process drift remain zero-input failures; any post-input uncertainty remains non-retryable.

## 0.13.6 - 2026-09-20

### Changed

- Extend the advertised `terminal_user_explicit` `replace_current_composer_and_submit` policy to Claude Code. After the live input-safety checks pass, Claude Code uses a sentinel-backed native `C-s` stash-clear transaction that is independent of the cursor position and does not interrupt an active turn, proves the main Composer empty, then injects the new request, waits through the paste window, and dispatches Enter exactly once. An existing draft, parsed working activity, or ordinary Composer visibility, stability, or exactness does not veto the human's explicit Send.
- Advance the structured List action contract to v29 with the agent-neutral `terminal_user_explicit_composer_policy`; retain `codex_terminal_user_explicit_composer_policy` as a v28 compatibility alias.

### Security

- Preserve zero-input, fail-closed boundaries for blocked approvals, input-owning questionnaires, editors or menus, read-only viewers, and terminal/process drift. Once Claude Code clear or request input may have occurred, an uncertain outcome is never retried automatically.
- Return structured `submission_uncertain` and `do_not_retry` evidence through Host tools after any possible replacement input, and retain the durable message intent so the same request cannot be replayed blindly.

## 0.13.5 - 2026-09-17

### Fixed

- Recognize Codex 0.154.0 GPT-6 Astra's animated Braille sparkle empty-Composer frame as diagnostic idle when the exact placeholder and a complete supported footer remain visible.
- Reuse the same observed coding-agent version for terminal status parsing and List capability projection, preventing versionless screen-classification drift.

### Security

- Keep animated idle classification separate from exact empty-Composer authority. Unsupported versions, unknown glyphs, clipped or changed footers, real drafts, working, approval, questionnaire, and model-picker surfaces remain fail-closed; native lifecycle, new-thread, and model-control actions still require independent exact-Composer proof.

## 0.13.4 - 2026-09-15

### Changed

- Make typed model control use one shared source of truth for native profile support, terminal subject normalization, input-owning surface classification, action availability, private authority, and transaction phase. List and execution now make the same fail-closed decision for ordinary, residual-continuation, and repair flows.
- Run managed Monitor and Terminal Watch questionnaire responses through the same reservation, live-revalidation, dispatch, settlement, and `response_uncertain` transaction semantics while preserving their distinct ownership and task-completion models.
- Keep OpenClaw, Pi, and DeepSeek Harness integrations aligned through one Host-neutral 22-tool semantic catalog, one canonical bundled Skill, a versioned capability handshake, and shared connector package verification.
- Restructure terminal discovery into immutable facts, centralized action policy, and compact public projection. Split terminal Send, approval, retry, native inspection, model control, Watch storage, callback routing, and Herdr transport into focused modules behind compatibility facades.
- Add typed model-control UI goldens, an in-process List-to-catalog-to-set-model contract, architecture-health ratchets, focused contract suites, and separate current-architecture and historical design records.

### Security

- Preserve exact pane, process-birth, cwd, agent, version, mutation-lock, and durable pre-input reservation checks across the new module boundaries. Private authority remains isolated, historical Store formats remain readable, and any possible input with an unproven postcondition remains non-retryable.

## 0.13.3 - 2026-09-14

### Added

- Add typed, catalog-bound model control for supported idle Codex and Claude Code panes. Callers can inspect native model/reasoning choices, select only an advertised semantic tuple, and receive separate effective-current-session and future-session-default postconditions without exposing raw slash commands, keys, menu indexes, or private authority.
- Add a narrowly scoped Codex model-control repair action for an exactly recognized stale `/model` completion surface, bare Composer command, or native picker. The cleanup action never selects a model or submits work and must prove the main Composer empty before returning success.

### Changed

- Replace the structured List response's repeated action contract and verbose diagnostics with a compact terminal-first projection shared by OpenClaw, Pi, and DeepSeek Harness. It retains live resource identities, current state, action names, and dynamic semantic inputs; static action meanings and safety rules live in the bundled `agent-knock-knock` skill.
- Bundle that same canonical skill with the OpenClaw plugin and export one Host-neutral List projection contract so native controller connectors do not maintain separate field-pruning logic.

### Fixed

- Let exact, idle Codex `0.154.0` zero-rollout panes discover and change native model settings without first fabricating a Session identity, while preserving exact pane/process/cwd, empty-Composer, interaction, active-Turn, and postcondition checks.
- Recognize the standard and narrow Codex `Select Model and Effort` picker, including the nested `More reasoning…` flow, as a model-control surface instead of generic busy activity. List no longer advertises ordinary idle mutations while that picker owns input.
- Normalize terminal/process incarnation authority across List and typed model-control execution, preserve a safe continuation action for exact residual `/model` state, and keep uncertain input outcomes non-retryable.

### Security

- Revalidate the exact terminal, process birth, screen generation, native catalog, Composer/input-owning surface, and current action offer under one mutation lock. Approval, questionnaire, editor, viewer, active Turn, unknown content, and identity drift remain zero-input failures; any post-input uncertainty remains `do_not_retry`.

## 0.13.2 - 2026-09-12

### Added

- Add exact Codex CLI `0.154.0` lifecycle, native `/status`, transition-settlement, and legacy blocking `request_user_input` questionnaire profiles, backed by isolated tmux probes and the official tagged source and snapshots.

### Changed

- Keep human-priority Send available while Codex is working, showing ordinary queued messages, or presenting a collapsed asynchronous question summary. Refuse input before mutation when the asynchronous question editor is expanded, clipped, or otherwise owns terminal input.
- Recognize the Codex `0.154.0` active-writer resume viewer, including narrow layouts and remapped or disabled transcript shortcuts, so AKK never injects input into its read-only surface.
- Preserve legacy questionnaire settlement and bounded session excerpts around the new `retained_context` rollout record. Non-blocking `request_user_input_async` response automation remains explicitly unsupported until it has a separate lifecycle contract.

### Security

- Revalidate asynchronous-question input ownership both before and after the Send reservation. Expanded or ambiguous editors, approval surfaces, read-only viewers, and terminal identity drift remain zero-input failures; ordinary drafts and collapsed questions retain the explicit human Send guarantee.

## 0.13.1 - 2026-09-10

### Fixed

- Reconcile owner-released historical Turns without attempting obsolete native-identity recovery, while preserving active, stalled, malformed, ambiguous, and tampered records for explicit handling.
- Read and safely upgrade exact v1/early-v2 Terminal Watch callback presentations, and recognize an accepted historical completion receipt only when a newer terminal dispatch has strictly superseded its top-level ledger entry. The repaired Store now reconciles 222 Turns and scans 80 Watches with zero errors.
- Add exact lifecycle, native-status, and AskUserQuestion profiles for Claude Code `2.1.266` and `2.1.267`, including the optional `Organization policy` Status row introduced in `2.1.261`. The field is also accepted by the `2.1.263` profile and its value is always redacted.
- Keep Codex `0.153.4` as the latest exact regression-tested stable profile after reviewing the installed client and official release behavior; the newer `0.154.0` builds remain prereleases and are not promoted.

### Security

- Bind Claude questionnaire identities and prompt fingerprints to the exact client version, reject malformed or inherited version-registry keys, and send no terminal input when a saved interaction crosses a client-version change.
- Preserve Store repair idempotency and historical data: compatibility recovery requires exact receipts, process and path evidence, and never deletes valid active Sessions, Turns, or Watches.

## 0.13.0 - 2026-09-10

### Added

- Promote terminal-scoped Codex sends from a frozen open-rollout candidate set after exactly one rollout durably accepts the request, including the first task after `/clear` when the foreground rollout does not exist before Enter.
- Add explicit `identify_foreground` and atomic `identify_and_send` operations for safely resolving an ambiguous foreground Codex rollout without weakening ordinary human-priority Send.
- Notify the owning controller when an unmanaged fallback Watch observes a native questionnaire that requires manual TUI input, without granting that Watch response or key-dispatch authority.
- Let newly created exact Terminal Watches notify and answer supported native Codex and Claude Code questionnaires through the same owner-bound `respond_interaction` contract used by managed Turns. Activity/best-effort Watches and migrated legacy records remain notification-only.

### Changed

- Make human-explicit Send results distinguish physical terminal dispatch, native agent acceptance, managed ownership, and observation mode. Legacy delivery fields remain available as compatibility aliases during the 0.13 transition.
- Continue candidate acceptance across the frozen pre-send roots and the current root inventory, so a rollout whose original FD closes can still be proven by its unchanged path, device, inode, and byte boundary.

### Fixed

- Retry a short-lived duplicate Codex file descriptor for the same exact rollout only inside bounded post-send identity and acceptance polling, so native-thread creation can settle without stalling the managed Turn; conflicting identities remain immediately uncertain and no descriptor is selected while the overlap persists.
- Give human-explicit Send a bounded one-second Store/state lock grace while keeping terminal acquisition non-blocking, so brief monitor-supervision writer leases do not unnecessarily downgrade an otherwise manageable questionnaire to a notification-only Watch.
- Preserve the exact pre-send Codex rollout candidates as Turn-scoped monitor companions after one rollout accepts the request, so a still-open predecessor does not suppress questionnaire discovery or response authority after managed promotion.
- Transfer one unchanged detached Session claim to the provisional managed Session when its exact source-less Codex candidate accepts the new Send, so a closed prior Turn cannot stall the next questionnaire on the same native thread.
- Preserve managed Codex continuation after a released Turn leaves an obsolete completion callback pending or failed: an exact human-selected Send may fence only that unaccepted callback retry debt, then continue through the existing managed authority path with interaction response enabled.
- Pass the private managed binding token from OpenClaw's freshly reconciled terminal action into the CLI, and report managed-authority conflicts separately from genuinely stale physical terminal authority.
- Settle fallback Watches on their exact Codex `turn_aborted` record or invalidate them when a later native turn overtakes the accepted task, so an old Watch cannot repeatedly attribute new questionnaires to an abandoned Send.
- Attribute questionnaire notifications during multi-rollout ambiguity only when the accepted rollout contains the unique pending `request_user_input` whose step, prompt, and options match the live TUI; paired outputs, changed rollouts, duplicate signatures, and unreadable evidence remain silent.

### Security

- Keep physical target, process incarnation, composer/interaction, and duplicate-dispatch checks fail-closed while preventing rollout, Session, Store, or callback uncertainty from vetoing an explicitly selected human Send. Replaced, deleted, ambiguous, multiply accepting, or unreadable rollout evidence remains uncertain and is never replayed automatically.
- Bind detached-claim transfer to the frozen v3 acceptance anchor and CAS-fenced Session state. Claim drift, blocking work, ambiguous owners, or changed terminal/workspace authority remains post-dispatch uncertainty with no automatic resend.
- Limit callback-debt supersession to the exact released binding generation with a validated terminal, native thread, rollout, submission receipt, and final lifecycle message. Active interactions, approvals, transitions, in-flight callbacks, accepted transports, stale managed tokens, and cross-Turn evidence remain fail-closed; an explicitly overridden uncertain callback is retained as audit evidence and is never retried.
- Revalidate controller ownership, terminal/process/native-task identity, prompt surface, and responder priority immediately before Watch input. Managed Turns take precedence, while stale, reserved, uncertain, consumed, manual-only, or ambiguous interactions remain fail-closed without replay.

## 0.12.37 - 2026-09-08

### Fixed

- Derive a guarded Codex custom-text choice when `0.153.4` renders only its client-generated `None of the above` row. The derived action uses native Other's Accept-to-Notes path, while the native Other semantic choice keeps its distinct direct-submit behavior.
- Join Codex option-description continuations only when a narrow pane wraps them at the exact native description column without crossing a physical blank frame boundary, so final `enter to submit all` questions remain actionable without accepting ambiguous layouts.
- Treat an elapsed interaction projection timestamp as a mandatory live-recapture boundary instead of terminal-questionnaire death. OpenClaw and CLI responses proceed only when the same Turn, owner, terminal identity, prompt fingerprint, semantic projection, and action plan are proven again under lock.

### Security

- Keep the public expiry validator fail-closed by default and allow stale-shape validation only in internal dispatch paths that always perform exact live terminal recapture before reservation or input. Changed or missing prompts continue to send zero input.

## 0.12.36 - 2026-09-08

### Fixed

- Treat a guarded Codex `0.153.4` `Type something.` alias beside the exact native Other row as a two-step custom-answer flow: bounded cursor movement selects native Other and opens Notes without submitting the alias literally, then a fresh `free_text` interaction sends the user's text. Native Other itself remains directly selectable without Notes.

### Security

- Accept Codex custom text only from the exact empty `Add notes` editor and known footer, keeping changed Other rows, existing human drafts, unknown layouts, and uncertain multi-key delivery fail-closed.

## 0.12.35 - 2026-09-08

### Fixed

- Run OpenClaw plugin CLI relays asynchronously so `list --reconcile`, Send, Status, questionnaire responses, and callback-side approval work cannot freeze the Gateway event loop while a monitor reconnects.
- Propagate OpenClaw invocation cancellation through asynchronous relay work, and give Gateway callback, chat, session, and wait calls an explicit 25-second CLI deadline inside AKK's 30-second delivery watchdog.

### Changed

- Keep routine releases focused on the build-pinned OpenClaw version. The slower minimum-host and Plugin API boundary matrix remains available through `npm run compat:openclaw` for periodic compatibility review and compatibility-floor changes.

## 0.12.34 - 2026-09-08

### Fixed

- Recognize Codex `0.153.4` questionnaire footer tips when the terminal wraps them across exact tip boundaries, and accept the verified `enter to submit all` footer on the final option or free-text question, so multi-step questionnaires remain actionable instead of falling back to `manual_required`.

### Security

- Keep questionnaire footer matching fail-closed: only exact known tips in their expected order are accepted, while the raw physical footer layout remains part of the prompt fingerprint so a resize or redraw between Status and dispatch invalidates stale response authority.

## 0.12.33 - 2026-09-07

### Added

- Notify the owning OpenClaw conversation whenever a managed Claude Code or Codex Turn reaches a supported native questionnaire step, then resume monitoring so sequential questions and final confirmation each receive their own durable callback.

### Fixed

- Expose portable OpenClaw response schemas for single-select, bounded free-text, and confirmation answers while retaining strict semantic validation against the current terminal question.
- Treat a durable interaction reservation as the expiry acceptance boundary, preventing a questionnaire recapture that crosses a ten-minute lease bucket from being falsely reported as changed and stalling the Turn. Proven zero-input failures now release only their exact reservation and require a fresh Status; genuinely uncertain terminal input remains fail-closed.

### Security

- Keep interaction callbacks notification-only: the owning controller must obtain a fresh Status-bound private offer before responding, and multi-select, stale, secret-bearing, changed, or uncertain prompts remain non-actionable.

## 0.12.32 - 2026-09-07

### Fixed

- Adopt OpenClaw 2026.9.2's portable `assets/icon.png` plugin branding convention and remove the unsupported top-level manifest icon URL, keeping the AKK icon packaged locally while restoring a warning-free ClawHub validation result.

## 0.12.31 - 2026-09-07

### Added

- Promote Codex `0.153.4` and Claude Code `2.1.263` to exact regression-tested lifecycle and native-status profiles, alongside their interactive-questionnaire profiles, after isolated real-TUI validation.

### Fixed

- Recognize the current terminal-scoped Send projection in the isolated lifecycle smoke while keeping its dispatch on the strict managed-only path and all terminal authority out of published evidence.
- Preserve exact committed Codex lifecycle companion fences through submission acceptance and monitor recovery, so a first Send after `/new` is not falsely stalled when Codex keeps the predecessor rollout open; unknown roots remain fail-closed.

## 0.12.30 - 2026-09-07

### Added

- Add an owner-bound `agent_knock_knock_respond_interaction` contract for exact native Claude Code and Codex questionnaires, including opaque single-select choices, stepwise multi-question flows, bounded free-text replies, and final confirmation or cancellation.
- Add semantic `approve_once` and `reject` approval decisions when the current exact terminal prompt advertises a proven native rejection action.

### Security

- Bind every interactive response to the managed Turn, controller session, terminal and process incarnation, exact versioned screen fingerprint, expiry, and durable one-shot reservation. Unknown layouts, secret-bearing questions, stale offers, and uncertain post-input outcomes remain fail-closed without automatic retry.

## 0.12.29 - 2026-09-07

### Fixed

- Let an exact-empty managed Claude tmux send recognize the stable `[Pasted text #N +M lines]` composer produced by its single successful multiline paste. AKK now revalidates the same terminal incarnation, line count, closed frame/footer profile, and placeholder before dispatching exactly one Enter, instead of stalling while the collapsed draft is safe to submit.

## 0.12.28 - 2026-09-04

### Security

- Update the verified OpenClaw build dependency to `2026.9.1` and ClawHub release tooling to `0.23.3`, then refresh the root and DeepSeek connector dependency locks to remove the reported vulnerable transitive versions without raising AKK's supported OpenClaw host floor.

### Fixed

- Let the OpenClaw compatibility and release matrix detect capability-consent support and accept the plugin's declared capabilities on hosts that require explicit consent.
- Create the matrix's isolated callback session before asserting durable next-turn injection, matching the stricter persisted-session contract in current OpenClaw without weakening the minimum-host check.
- Omit absent optional state and log paths from callback injection metadata so the payload remains valid JSON under current OpenClaw's strict plugin-hook validation.

## 0.12.27 - 2026-09-04

### Added

- Add exact Codex `0.153.0` and Claude Code `2.1.259` lifecycle and native-status profiles after isolated real-TUI validation of status inspection, prompt submission, durable session identity, new-thread, and exact-resume behavior.

### Fixed

- Exclude Codex `0.153.0` management and non-interactive subcommands from terminal discovery while preserving interactive prompts, option values, resume, and fork invocations.
- Recognize Claude Code `2.1.259` value-taking CLI options and its Bash permission footer without the removed Ctrl+E hint; safely correlate the canonical auto-mode tip when it wraps at 80 columns without ever joining wrapped command text.
- Give the exact Codex `0.153.0` profile the bounded MCP restart settlement used by verified current lifecycle transitions.

## 0.12.26 - 2026-09-01

### Added

- Add structured Herdr session, pane-process, process-association, and exact-terminal discovery diagnostics so a missing terminal row can be localized without logging terminal contents or coding-agent commands.

### Fixed

- Preserve authoritative PID and ancestry rows when `ps` elapsed metadata is temporarily unavailable, and select the interactive Codex root through the complete process tree so nested helper processes cannot replace the terminal's stable PID.
- Keep exact Terminal Watch observation bound to its requested PID even when a nested Codex process appears first, preventing a live Herdr pane from being misreported as `terminal_process_unavailable`.
- Resolve the read-only physical Codex identity from a complete unique same-PID, same-incarnation open-root inventory when a stale managed Session preference rejects the current thread. Managed binding conflicts remain independently visible, while ambiguous roots and every mutation path continue to fail closed.

## 0.12.25 - 2026-08-31

### Fixed

- Let the npm OpenClaw installer detect capability-consent support and pass `--accept-capabilities` through both fresh linked installs and trusted replacement installs. Older OpenClaw versions keep the existing argument shape, while installation receipts now report whether capability consent was accepted.

## 0.12.24 - 2026-08-31

### Added

- Add an exact Codex `0.151.0` native lifecycle and `/status` inspection profile after validating its Composer, rollout identity, slash-popup, status-card, clear, exact-resume, and terminal Send surfaces in an isolated real TUI.

### Fixed

- Let Codex `0.151.0` and forward-compatible lifecycle verification wait safely for a resumed thread's bounded MCP startup to restore the exact empty Composer before sending the single post-resume `/status` probe. A proven `not_started` Composer observation is retried without terminal input only for those profiles; historical profiles and other failures retain their existing fail-closed behavior.
- Preserve a bounded stable-recapture opportunity when the first exact native `/status` Composer capture itself exceeds the wall-clock settle deadline on a busy tmux server; mismatched or disappearing candidates still fail closed without Enter.

## 0.12.23 - 2026-08-30

### Fixed

- Give user-explicit unmanaged fallback Watches their own `chat.send` callback profile instead of reusing the managed Send Gateway method. Recover the exact historical pre-I/O profile-mismatch receipts with their original idempotency keys, preserve ambiguous or delivered evidence, and expose callback delivery failures in Watch status.

## 0.12.22 - 2026-08-30

### Added

- Add an exact Claude Code `2.1.251` lifecycle, transcript, Bash approval, and `/status` inspection profile after real TUI validation.

### Fixed

- Treat Claude Code `2.1.251` `agents` rows reported as `waiting` without a wait reason as input-ready, while preserving non-empty permission/background wait reasons as blocked or active states.
- Recognize the strict three- or four-choice Claude Bash approval variants that offer auto mode, approve only a highlighted one-time `Yes`, and exclude the auto-mode tip from exact transcript command correlation.
- Exclude the new Claude Code management subcommands from interactive terminal discovery and accept the newly profiled Status fields without exposing the peer address.

## 0.12.21 - 2026-08-30

### Added

- Add an exact Codex `0.150.1` native lifecycle and `/status` inspection profile after verifying its Composer, rollout, slash-popup, status-card, clear, and exact-resume surfaces.

## 0.12.20 - 2026-08-28

### Added

- Add a durable `terminal_activity` / `best_effort` Watch fallback for an exact user-selected terminal when no unique provider task anchor is available. It arms on observed work or approval and reports stable idle only after two consecutive supervision sweeps.

### Fixed

- Keep an explicit read-only Watch available across managed ownership, missing action advertisement, lifecycle-binding gaps, agent/artifact version drift, an existing Watch, and malformed unrelated Watch records; these conditions now warn, reuse, or degrade instead of vetoing the user.
- Recognize the Codex 0.149.1 `item_completed` `UserMessage` record as exact human-root evidence, including exact text and turn-identity validation.

### Changed

- Allow independent controller callback authorities to observe the same terminal while keeping same-target, same-controller Watch creation idempotent. Existing active Watches no longer hide the Watch action on terminal rows.
- Expose immutable Watch warnings plus `watch_mode` and `confidence` in status and callbacks so exact task completion remains distinct from best-effort terminal activity becoming idle.

### Security

- Keep manual Watch observation-only: it acquires no terminal mutation authority, sends no input, changes no managed ownership, and never auto-approves. Creation still fails when the exact terminal is absent or unobservable, neither an exact anchor nor screen-status path exists, or durable Watch state cannot be written.

## 0.12.19 - 2026-08-27

### Added

- Attach a durable Terminal Watch after a successful `terminal_user_explicit` unmanaged physical Send, restoring completion, failure, invalidation, and timeout callbacks without fabricating a managed Turn.

### Changed

- Advance the model-facing action contract to 23, Terminal Watch schema to v2, and Store writer protocol to 6 with compatible migration and normalization of existing records.

### Security

- Keep the user's explicit Send authoritative: Watch attachment and observation are best-effort, warning-only follow-up work and can never block, revoke, or automatically replay accepted terminal input.
- Bind fallback callbacks to the exact Codex rollout or Claude transcript task accepted after the Send, including same-request races and completion before the first Watch sweep. Automatic fallback Watches do not emit approval callbacks; approval input remains manual.

## 0.12.18 - 2026-08-27

### Fixed

- Make an explicit Codex Send independent of Composer visibility, stability, and exactness. Physical fallback now replaces the current Composer with one `C-u`, injects the new request, waits through the paste window, and dispatches Enter exactly once without a post-text Composer veto. Claude Code remains exact-empty-only.

### Changed

- Treat Codex and Claude Code version profiles as regression-test evidence rather than runtime allowlists. A complete but unverified `x.y.z` version keeps every otherwise eligible Watch, native status, new-thread, candidate-list, and exact-resume action available through a generic compatibility profile, with explicit warnings in List, action, doctor, and command results.
- Advance the model-facing action contract to 22 so Hosts preserve compatibility warnings and advertise Codex `replace_current_composer_and_submit` while continuing to pass only semantic action arguments.

### Security

- Preserve exact terminal/process, native-thread, workspace, artifact, approval, composer, candidate, and postcondition checks for unverified versions. Real UI or schema drift fails at runtime, and any result after possibly sending input remains uncertain and must not be retried automatically.
- Preserve the exact live terminal/process and scanned, non-blocked approval boundary for Codex user-explicit Send. Once its sole mutation sequence begins, an uncertain result must not be retried automatically.

## 0.12.17 - 2026-08-26

### Fixed

- Keep an explicit user Send available for a verified mutable Codex prompt even when its composer already contains a stable draft. An empty composer receives the new request, an identical draft receives exactly one Enter without duplicate text injection, and a different draft is cleared once, replaced by the new request, and then submitted once.
- Use one shared prepared timestamp for a deferred foreground transfer, its Turn submission receipt, and its dispatch ledger, preventing real-clock drift from producing a half-submit authority mismatch between otherwise identical evidence.

### Changed

- Advance the model-facing action contract to 20 and add the first Codex nonempty-Composer user-explicit policy, later superseded by the v22 replace-current-Composer behavior. Claude Code user-explicit Send, native inspection, and native lifecycle input remain restricted to a verified empty Composer.

### Security

- Revalidate the exact Codex terminal/process identity, non-approval state, stable composer digest, and user request immediately around clear, text, and Enter boundaries. Live working activity remains diagnostic rather than a veto for this user-explicit path. A failure after the sole draft-clear key is uncertain and must not be retried automatically; draft text and opaque composer authority remain outside model-facing actions and durable receipts.

## 0.12.16 - 2026-08-26

### Added

- Add a Host-owned foreground MCP/stdio Bridge that exposes the existing 16 semantic AKK tools without introducing a second state or tool model.
- Add strict Host Profile v1 configuration with trusted environment session binding, a shell-free `command_json_v1` callback driver, compatibility/doctor commands, a published JSON Schema, and a starter user Profile.
- Add the public `./host-adapter` facade used by native controller integrations, with exact per-controller command/tool authority and one shared Host-owned lifecycle.
- Add a first-party DeepSeek Harness Web connector package that derives the controller route from the exact invoking Agent, registers `/akk` plus all 16 semantic tools, and returns callbacks through idle `followup` or running `inject` without a user-visible bind step.

### Changed

- Reuse the shared Host lifecycle and existing durable callback route, outbox, retry, and settlement core for configuration-only Hosts while preserving the native OpenClaw adapter unchanged.
- Persist complete route-bound Terminal Watch callback authority and keep callbacks pinned to the initiating Host/Agent incarnation instead of redirecting them after replacement or restart.

### Security

- Keep Profile selection, controller identity, executable, arguments, credentials, and acknowledgement rules outside model-facing tool inputs; exact route fingerprints and delivery/message acknowledgements fail closed on drift.
- Keep DeepSeek session routing outside slash/tool arguments, authenticate its private callback socket, and reject disposed or replaced Agent objects rather than trusting a reused session-id string.

## 0.12.15 - 2026-08-25

### Added

- Add the `terminal_user_explicit` physical Send authority domain, global message intent, and immutable omitted-target binding so an explicit user Send remains actionable independently of AKK management state.

### Fixed

- Prevent stale, stalled, deferred, corrupt, or missing Store, Session, Turn, transfer, activity, and dispatch-ledger state from vetoing an explicit user Send. When a zero-wait managed attempt proves that no input was submitted, fall back once to exact physical delivery and leave subsequent observation to Terminal Watch.
- Detach an exact same-incarnation bound Session left behind by failed managed preparation after physical fallback when no live blocking Turn remains, so a later Terminal Watch can attach normally.
- Retire an exact same-incarnation ordinary dispatch ledger whose owner Turn is gone after physical fallback, so a refreshed List can advertise Watch again; unresolved native lifecycle ledgers remain preserved.
- Reject ordinary native slash-command text before selector discovery, avoiding terminal or host-process scans for an invalid Send or Respond.
- Make OpenClaw doctor skill verification compatible with multi-agent installations that require an explicit `main` owner.
- Scope durable omitted-target delegate bindings to the active runtime directory, preventing in-process hosts with scoped `AKK_RUNTIME_DIR` values from sharing message-ID state.
- Bind explicit physical Send authority to the exact operating-system process incarnation and reject stale supplied authority before managed preparation or terminal input.

### Changed

- Advance the action contract to 19 and expose Send readiness from physical terminal evidence while retaining the existing Store format and writer protocol.

### Security

- Continue to require exact live terminal and process identity, approval eligibility, an empty composer, and unambiguous input evidence before physical Send. Possible prior input, true concurrency, or same-message ambiguity remains fail-closed and never triggers duplicate delivery.
- Keep fallback delivery free of synthetic Turns or callbacks, and treat post-delivery bookkeeping or cleanup failures as warnings without automatically replaying user input.
- Preserve a Session still named by an unresolved native lifecycle ledger instead of fabricating a transition outcome; the physical Send remains delivered and cleanup reports the retained recovery boundary.

## 0.12.14 - 2026-08-24

### Added

- Add an exact Codex `0.149.1` native lifecycle and `/status` inspection profile, retaining fail-closed handling for adjacent and future unverified versions.
- Add a versioned, host-neutral callback route and transport boundary with durable routing and idempotency authority while retaining OpenClaw as the concrete host adapter.

### Fixed

- Distinguish the exact Codex root user row from same-turn synthetic user-role context, preserving Terminal Watch until a later native task actually supersedes it.
- Safely recover eligible uncertain Send submissions through exact one-shot retry and reconciliation without replaying accepted input or replacing the original request.
- Make explicit Close honor the user's management-release decision first, with best-effort linked cleanup, warning-only cleanup conflicts, no terminal or coding-agent interruption, and immediate eligibility for a fresh Watch.

### Security

- Freeze callback routing and idempotency authority durably, fail closed on route drift or ambiguous recovery, and keep model-facing callback and retry contracts free of opaque authority material.
- Require exact adjacent native-event evidence and a privacy-safe content hash when identifying Codex root user rows; missing, duplicate, orphaned, or mismatched evidence fails closed.

## 0.12.13 - 2026-08-22

### Added

- Add durable Terminal Watch for exact human-started Codex and Claude Code tasks, with restart-safe OpenClaw callbacks for approval, completion, failure, timeout, invalidation, and cancellation.
- Add `agent_knock_knock_watch` / `agent_knock_knock_unwatch`, `/akk watch` / `/akk unwatch`, and watch-aware list/status output without creating an AKK Session or Turn or sending terminal input.

### Fixed

- Derive Watch and Send authority from exact terminal IDs inside the trusted plugin/CLI boundary, so OpenClaw models never need to copy opaque tokens or fingerprints.
- Keep Watch activity authoritative when Codex's transient screen markers look idle, support large historical rollouts with incremental checkpoints, and isolate corrupt historical Watch records without starving healthy watches or callbacks.
- Restore follow-current Send across tmux route renumbering, stale legacy dispatch ledgers, long-lived Sessions with released earlier binding epochs, and interrupted v1-to-v2 ledger migration without replaying terminal input.

### Changed

- Advance the action contract to 18 and expand the OpenClaw plugin contract to 16 tools. Model-facing actions now carry semantic IDs only; opaque freshness and confirmation authority remains private to the plugin and CLI. Store writer protocol remains 5; Terminal Watch uses its own schema-v1 aggregate.

### Security

- Pin each Watch to exact terminal, process, native-task, runtime-version, rollout/transcript file, and privacy-safe request-hash evidence; drift fails closed and approval observations never authorize automatic input.
- Revalidate private Send, lifecycle, handoff, reconciliation, and approval authority under canonical terminal and Store locks; stale, split, replayed, cross-session, or callback-mismatched evidence sends zero terminal input.

## 0.12.12 - 2026-08-21

### Added

- Add exact native lifecycle and status compatibility for Codex `0.148.0` and Claude Code `2.1.237`, while retaining the previously verified profiles.
- Report exact native-profile support in CLI and OpenClaw doctor output without blocking ordinary terminal work for an otherwise available but unprofiled coding-agent executable.

### Changed

- Decompose the orchestration runtime into typed, ownership-checked domain facades and services while preserving action contract 16, Store writer protocol 5, public CLI/OpenClaw contracts, lock ordering, and durable-write ordering.
- Strengthen architecture enforcement with bounded production functions, canonical status authorities, targeted affected-test selection, and reproducible refactor evidence.
- Clarify the TUI-first handoff model and make fast tests the normal development/local-install gate while reserving the full release suite for actual npm and ClawHub publication.

### Security

- Keep adjacent unknown Codex and Claude Code versions fail-closed for native inspection and lifecycle operations, and enforce one-way Claude transcript resume compatibility across verified profiles.
- Preserve exact terminal identity, binding, approval, acceptance, callback, retry, and uncertainty fences across the internal architecture refactor.

## 0.12.11 - 2026-08-14

### Fixed

- Allow managed close to retire a Turn when its exact bound Codex or Claude Code process is conclusively absent, without falling into the managed/raw close deadlock.
- Stop terminal-monitor relaunch loops for verified-dead accepted Turns, while preserving completion-first settlement when the exact rollout or transcript already contains a durable result.
- Recover verified-dead stall and close transitions idempotently across event/state/ledger crash windows without replaying terminal input.

### Security

- Require a complete process inventory, exact Session and Turn binding generation, canonical terminal endpoint, process incarnation, dispatch ledger, and append-only native-acceptance receipts before dead-process cleanup; malformed, partial, conflicting, or unavailable evidence remains fail-closed.
- Distinguish durable completion as present, absent, or unverifiable for both Codex rollouts and Claude transcripts. Unverifiable evidence may stop orphan-monitor churn but cannot resolve the dispatch, renew the Turn, or trigger terminal input.

### Changed

- Keep action contract 16 and Store writer protocol 5 unchanged; no new public action or Store authority is introduced.

## 0.12.10 - 2026-08-13

### Fixed

- Scope Codex and Claude Code approval fingerprints to one adapter-isolated, exact unredacted prompt region, so unrelated terminal output can continue scrolling across review, authorization, and dispatch reservation without invalidating the same visible request.
- Normalize managed approval locking to terminal, Store writer, then Turn state order, eliminating the writer/state inversion that could amplify approval delays under concurrent monitor activity.
- Support the complete Codex 0.147 command, edit, permission, and MCP approval menus, including multi-choice decline/cancel rows and the permission deny shortcut.

### Changed

- Publish action contract 16. Whole-screen digests and excerpts are diagnostic only; v15 approval fingerprints and terminal-scoped approval tokens require a fresh `list` or `status` after upgrade.
- Store writer protocol remains 5.

### Security

- Revalidate the exact prompt-region digest with terminal, process, action, request, policy, and working-directory authority before approval input; missing, incomplete, duplicated, reordered, spoofed, or changed prompt evidence sends zero keys.
- Keep raw prompt text local to the adapter and out of status, Store records, tokens, logs, and failure diagnostics; only its SHA-256 digest participates in authorization.

## 0.12.8 - 2026-08-13

### Fixed

- Route every eligible quiescent rollout-backed Codex pane through terminal-follow-current candidate attribution, including single-root and multi-root inventories with resolved or unavailable foreground identity, then bind only the unique post-submit acceptor.
- Keep the Codex `/clear` resume hint advisory, so a valid fresh candidate action remains usable after the hint scrolls out of view while exact terminal, process, Store, inventory, and composer authority remains unchanged.
- Restore idempotent retry after a conclusively zero-input candidate-send abort without reusing the abandoned provisional Session or allowing binding drift.

### Changed

- Publish action contract 15. Rollout-backed Codex rows advertise `terminal_follow_current` instead of `session_exact`, and cached direct `session_id` sends reject before task input.
- Store writer protocol remains 5.

### Security

- Require a complete nonempty open-root inventory, exclusive candidate ownership, exact process and terminal incarnation, frozen source history and dispatch ledger, an idle empty composer, and no blocking Turn before candidate input; stale, incomplete, claimed, or ambiguous state remains fail-closed.

## 0.12.7 - 2026-08-12

### Fixed

- Follow a supported manual Codex `/clear` through a fresh terminal-scoped candidate send, binding only the rollout with one unique post-anchor acceptance without an internal `/status` probe.
- Restore future-send liveness after explicitly closing an uncertain predecessor when its resolved close ledger, append-only uncertain receipt, frozen Turn history, absent old rollout, and unclaimed current inventory remain exact.
- Recognize the supported Codex resume hint when its UUID wraps across lines in a narrow pane, while keeping the hint as routing evidence rather than native-identity authority.
- Ignore closed detached Codex companions when one exact current rollout is open, and release completed Claude Turns for a fresh message ID while retaining immutable acceptance receipts.

### Changed

- Publish action contract 14. Store writer protocol remains 5.

### Security

- Revalidate candidate inventory, terminal and process identity, abandonment proof, and source/target lineage before input, commit, and crash recovery; ambiguous, drifted, or uncertain native acceptance remains non-retryable.

## 0.12.6 - 2026-08-12

### Added

- Add manual-only terminal-scoped Codex approval for one exact visible prompt when a human-entered task has no AKK dispatch owner or usable foreground UUID, while requiring a fresh list token, status fingerprint, and explicit confirmation.

### Fixed

- Let an advertised ordinary Codex task proceed once in a narrow pane when AKK has a complete but foreground-unbound rollout inventory, then bind only the rollout that uniquely accepts the exact request without an internal `/status` probe.
- Reconcile callbackless terminal completion locally, release the exact dispatch ledger, and restart pending candidate monitors after a crash without creating a Gateway outbox or replaying terminal input.

### Changed

- Publish action contract 12 and Store writer protocol 5. Protocol 4 Stores upgrade through an atomic manifest-only writer fence.

### Security

- Freeze released predecessor Turn history throughout deferred candidate binding, preserve separate same-UUID and different-UUID Session lineages, and keep zero, multiple, drifted, or uncertain request acceptance non-retryable.
- Revalidate manual approval and cancellation against the canonical terminal endpoint, process incarnation, dispatch snapshot, Session revision, and prompt immediately before terminal keys, while keeping auto-approval and provisional managed controls unavailable.
- Serialize deferred recovery as terminal-to-writer-to-state and treat Store or state-lock contention as monitor backoff rather than native-acceptance uncertainty.

## 0.12.5 - 2026-08-12

### Fixed

- Let an advertised terminal-scoped ordinary Codex first task proceed in a narrow pane without an internal `/status` probe when the existing status-card-only context has a verified zero rollout, then bind the new AKK Session to the exact rollout that accepts the request.
- Preserve strict UUID proof for explicit Session sends, responses, approvals, cancellations, lifecycle operations, and native inspection while keeping uncertain terminal input non-retryable.

### Security

- Isolate deferred foreground sends in a zero-UUID provisional Session and require exact process, terminal, request-acceptance, ownership, and binding-generation evidence before promoting it to the native thread.
- Add Store protocol 4 writer fencing plus crash-safe deferred-transfer receipts and recovery across pre-input aborts, post-input uncertainty, same-thread handoff, acceptance backfill, and downgrade attempts without replaying terminal input.

## 0.12.4 - 2026-08-11

### Fixed

- Submit every internal Codex `/status` through one exact-version closed path with bracketed-paste settling, current-composer proof, one Enter, and same-depth freshness, so narrow or stale Herdr screens cannot masquerade as a complete current Session.
- Stop uncertain terminal dispatches from collateral-stalling already completed Claude Turns, and strictly repair legacy false stalls only when completion, callback, dispatch-fence, and closed-owner evidence agree.
- Preserve exact Claude composer text across Herdr visual soft wraps while ignoring historical prompts outside the current bottom composer frame.

### Security

- Fence Codex status probes with exact tmux or kernel PTY viewport evidence, terminal route, process birth, TTY device identity, native identity, and final composer revalidation before the single Enter.
- Apply terminal-incarnation blockers consistently across list, send, lifecycle, and native inspection, while keeping human-handoff source Turns behind snapshot-bound close decisions and retaining typed Store-only close for genuinely unavailable terminals.

## 0.12.3 - 2026-08-11

### Fixed

- Recover a same-process Codex terminal after the previously bound rollout has conclusively ended by detaching the old Session and creating a separate virgin Session for the next exact terminal-scoped send.
- Parse only Claude Code's current bottom composer frame, so a historical `/clear` prompt does not block Herdr handoff and exact soft-wrapped drafts can still receive one verified Enter.

### Security

- Keep generic unverifiable native identity and explicit Session-scoped sends fail-closed, while requiring the exact endpoint, PID, process birth, cwd, owner, source binding, idle state, and styled-empty composer before adopting a verified zero-rollout Codex context.
- Preserve character-exact draft checks, repeated pre-text and pre-Enter identity revalidation, single-Enter dispatch, isolated Session history, and no blind retry after text may have reached the terminal.

## 0.12.2 - 2026-08-11

### Added

- Let terminal-scoped sends absorb an exact, verified native-thread switch made by a human through Codex or Claude Code, including `/clear`, new-thread, and Resume flows across tmux and Herdr.
- Restore a uniquely matching historical Session with its own binding generation, or create a separate Session for a previously unseen native thread, without merging conversation history.

### Changed

- Keep explicit Session-scoped sends pinned to their original native context, while active Turns expose a snapshot-bound handoff decision that requires explicit confirmation before the current human context is adopted.

### Security

- Revalidate the native UUID, process birth, terminal endpoint, cwd, exclusive ownership, idle state, and exact composer immediately around terminal input, while preserving single-Enter and no-blind-retry guarantees.
- Persist human-observed handoffs through fenced lifecycle transitions and ledgers with crash recovery, stale-decision rejection, and strict isolation for prior Turns, monitors, callbacks, approvals, and dispatch receipts.

## 0.12.1 - 2026-08-11

### Fixed

- Allow a genuinely virgin Codex TUI to accept its first AKK send by pinning the exact process incarnation before input, then atomically refining the Session and Turn to the newly materialized native UUID, rollout, and request evidence after the single Enter.
- Recover both post-Enter virgin-binding crash windows without replaying terminal text or Enter, while preserving the existing ownership, binding-generation, process, pane, cwd, rollout, and request-hash fences.
- Preserve tmux `pane_current_path` when extended eight-field pane output is collapsed to whitespace or underscores, rejecting ambiguous or truncated records instead of appending the server socket and pane ID to the workspace.
- Preserve Codex composer ANSI styling through Herdr's visible screen buffer so an empty dim placeholder is not mistaken for authored draft text, while leaving ordinary monitor and status reads on Herdr's agent-aware detection buffer.

## 0.12.0 - 2026-08-10

### Added

- Add exact local Herdr `0.8.0` / protocol 19 support as a second terminal provider alongside tmux, including discovery, screen capture, bracketed-paste-aware text delivery, key dispatch, lifecycle state, Resume snapshots, native inspection, monitoring, and OpenClaw actions.
- Add a routed terminal-provider registry, Herdr-aware doctor diagnostics, packaged setup documentation, and provider-neutral terminal identities throughout the Store and public terminal list.

### Changed

- Split the CLI entrypoint from its injectable command core, move the slowest lifecycle and rollout semantics into deterministic in-process fixtures while retaining their real-process contract tests, and add a fail-closed affected-test runner for faster local iteration.
- Isolate terminal-provider discovery and diagnostics failures so an unavailable Herdr session contributes no candidates without hiding healthy tmux terminals.

### Security

- Bind Herdr control to the local Unix-socket incarnation, stable `terminal_id`, refreshable pane route, shell and agent process ancestry, cwd, native coding-agent identity, and the existing Session/Turn binding fences before every side effect.
- Preserve the durable `prepared → text_injected → enter_dispatched → agent_accepted` boundary, keep lost acknowledgements uncertain without blind retries, fail closed when multiple providers could own one process, and isolate a failed provider discovery without hiding healthy transports.

## 0.11.7 - 2026-08-10

### Changed

- Establish a provider-neutral terminal-control boundary that separates stable endpoint/resource identity, mutable delivery routes, and process-incarnation evidence while preserving the existing tmux CLI, OpenClaw tools, and agent lifecycle behavior.
- Route terminal discovery, capture, text injection, and key delivery through an injectable provider registry with fresh resource resolution and explicit transport capabilities.
- Derive binding tokens, terminal locks, dispatch ledgers, receipts, approval fingerprints, and Resume snapshots from one canonical endpoint identity, while monotonically refining existing v0.11.x records and atomically promoting legacy ledgers without duplicate owners.

### Security

- Fail closed when provider identity, process anchors, or required capabilities cannot be revalidated, and preserve the distinction between input proven not sent and a potentially submitted uncertain outcome without blind retries.
- Use stable tmux server/socket and pane identities for namespace isolation and route-renaming safety while retaining exact legacy binding-token and approval-fingerprint compatibility boundaries.

## 0.11.6 - 2026-08-10

### Added

- Add exact lifecycle and native `/status` behavior profiles for Codex 0.147.0 and Claude Code 2.1.226 while preserving Codex 0.146.0/0.146.1 and Claude Code 2.1.218 support.
- Let Claude Code 2.1.226 discover and exactly resume same-workspace 2.1.218 history through source-version-bound v2 candidate tokens and the existing full UUID, ownership, binding, and identity fences.

### Fixed

- Match Codex 0.147.0's exact ordered two-row `/status` completion surface and Claude Code 2.1.226's `Session kind: interactive` Status panel.
- Keep Claude native inspection closed and reliable across narrow panes by accepting only exact profiled rows or their explicit Unicode-ellipsis prefixes, with a version-owned bounded settle deadline before the single Enter dispatch.

## 0.11.5 - 2026-08-09

### Added

- Extend the closed `native_inspect(status)` action to exact Claude Code 2.1.218 with an adapter-owned `/status` plan, a separately measured 80 ms composer-stability boundary, bounded and redacted Status-panel parsing, and safe return to the original idle composer.

### Security

- Fence Claude inspection with a fresh snapshot token, the shared terminal lock, exact pane, PID, process birth, cwd, binding, unique `claude agents --json --all` Session identity, and exclusive active ownership before and across terminal input.
- Keep ordinary `send` and `respond` slash-command rejection intact, issue at most one Enter and one Escape without blind retries, create no AKK lifecycle state, and leave `/usage`, `/cost`, `/stats`, and `/usage-credits` unavailable.

## 0.11.4 - 2026-08-09

### Added

- Add an adapter-owned, version-scoped native status inspection for Codex 0.146.0 and 0.146.1, exposed through a closed `native_inspect(status)` action that returns a bounded and redacted fresh `/status` result without creating a Session, Turn, receipt, monitor, callback, or Store state.

### Security

- Keep ordinary `send` and `respond` slash-command rejection intact while serializing native inspection with terminal mutations, revalidating the exact terminal, process, binding, version, idle composer, and ownership state, and dispatching at most one Enter only after the versioned 121 ms materialization boundary.
- Fail closed after identity drift, ambiguous or stale status evidence, and uncertain submission outcomes without blind retries or a second Enter.

## 0.11.3 - 2026-08-08

### Fixed

- Make virgin Codex raw-terminal attachment atomic by persisting its managed Session only after read-only pre-input checks pass, then CAS-detaching the provisional binding after every conclusively pre-input failure so a failed first send cannot strand a bound orphan.
- Add exact snapshot-fenced `reconcile-binding` recovery for eligible provisional and same-process external-thread conflicts while keeping ambiguous identity, PID, Turn, transition, and dispatch cases fail-closed and suppressing control actions that are already known to fail.
- Distinguish definite tmux no-input failures from uncertain submission outcomes so safe retries remain available without risking duplicate terminal injection.

## 0.11.2 - 2026-08-08

### Fixed

- Filter Codex resume candidates by workspace, source, archive state, and provider before applying the SQLite result limit, so older same-workspace threads are not dropped by unrelated global history.
- Keep the current adapter version separate from each candidate's source agent version, allowing historical Codex threads to remain resumable when their rollout metadata agrees while preserving the complete snapshot, ownership, binding, and identity safety fences.

## 0.11.1 - 2026-08-07

### Fixed

- Harden Codex resumable-thread discovery across transient SQLite WAL/SHM creation, replacement, and checkpoint windows with one read transaction, identity-checked bounded `SQLITE_CANTOPEN` recovery, and a query-only sidecar-materialization fallback that does not use `immutable=1`.
- Forward configured `codexHome` to Codex lifecycle discovery, new, and resume paths in OpenClaw tools and `/akk` commands.

## 0.11.0 - 2026-08-07

### Added

- Add snapshot-bound native Resume navigation with deterministic numbers, collision-safe display-only short IDs, opaque five-minute handles, and a `previous` / `刚才那个` shortcut derived from the current Session's latest committed lifecycle transition.

### Security

- Resolve every Resume shortcut back to the complete UUID and exact evidence tuple, then fail closed if the terminal action generation, process, workspace, binding, ordered candidate snapshot, ownership, or TTL changed before native input.

## 0.10.4 - 2026-08-07

### Fixed

- Recognize exact Codex multiline drafts across TUI-painted visual wraps before dispatching Enter once, while preserving authored newlines, indentation, repeated spaces, stable-capture checks, and fail-closed content drift detection.

## 0.10.3 - 2026-08-07

### Added

- Supervise active terminal bridge monitors from the OpenClaw plugin every five seconds and automatically recreate an unexpectedly exited owner without requiring `list` or `status`.
- Retain redacted durable-completion detector limitation and recovery diagnostics in each Turn's event history.

### Fixed

- Treat Store writer-lock timeouts as transient monitor deferrals with bounded backoff while preserving the hard fence for a genuinely superseded Session binding generation.
- Complete accepted Codex turns from their exact bound rollout and native turn UUID beyond the legacy recent-turn window, while preserving the existing exactly-once completion claim across recovery.

## 0.10.2 - 2026-08-07

### Fixed

- Require exact post-anchor Codex rollout or owner-private Claude transcript evidence before reporting a terminal submission as delivered; tmux transport success alone now remains pending or uncertain and is never automatically retried.
- Track durable `prepared → text_injected → enter_dispatched → agent_accepted` proof, preserve that exact proof level across replay and recovery, and fence stable OpenClaw retries to their original Store, Session, Turn, message, binding, and terminal incarnation.
- Settle an exact multiline Codex composer before dispatching Enter once, promptly report an unchanged exact draft as not accepted, and extend the opt-in lifecycle smoke payload to verify multilingual multiline native acceptance.
- Keep append-only submission receipts bound to the pane incarnation that received their input while allowing a replacement tmux pane to establish a new dispatch generation.

## 0.10.1 - 2026-08-06

### Added

- Add an opt-in native lifecycle live-smoke diagnostic that records redacted, commit-bound Codex and Claude Code `new → send → resume` evidence.
- Add an exact Codex 0.146.1 native lifecycle behavior profile while preserving 0.146.0 support.

### Fixed

- Let the lifecycle diagnostic attest a persisted unmanaged Codex 0.146.1 thread whose identity is first proved by New's locked, fresh `/status` probe, then fail before `/clear` unless that exact origin remains a uniquely owned, revalidated resume candidate; ordinary list and New behavior remain unchanged outside the opt-in diagnostic.
- Keep the semantic Turn phase independent from callback transport delivery, so a failed or pending `done` notification leaves the Turn idle and a failed or pending `question` or `blocked` notification remains actionable through respond or cancel.
- Treat accepted OpenClaw injection and wake acknowledgements as durable delivery while keeping `agent.wait` timeout, error, or malformed output as observation-only evidence that cannot replay an accepted callback.
- Serialize callback claims with exact in-flight diagnostics, preserve immutable outbox delivery across close and Session binding-generation changes, and migrate valid legacy callback-owned statuses without letting malformed records poison Store-wide listing.

### Changed

- Keep the native lifecycle smoke optional during rapid iteration: npm and ClawHub publishing no longer require an annotated-tag attestation, while the manual runner and evidence verifier remain available for diagnostics.

## 0.10.0 - 2026-08-06

### Added

- Add capability-scoped native-thread lifecycle controls for starting or clearing context, listing verified same-workspace resume candidates, and resuming one exact Codex or Claude Code native thread in the existing tmux pane.
- Add the optional OpenClaw tools `agent_knock_knock_new_thread`, `agent_knock_knock_list_resumable_threads`, and `agent_knock_knock_resume_thread`, plus `/akk new-thread`, `/akk clear-thread`, `/akk threads`, and `/akk resume-thread` human-facing commands.
- Publish the v5 list/action contract with exact terminal lifecycle targets, complete native-thread identities, fresh compare-and-swap binding tokens, per-candidate evidence fingerprints, and capability-gated availability.

### Changed

- Keep ordinary sends scoped to the current native context: each accepted send creates a new Turn, while a successful native lifecycle transition creates or activates an AKK Session and creates no Turn.
- Treat a sole historical Session whose recorded coding-agent PID has conclusively exited as resumable on the next lifecycle listing; the resume mutation compare-and-swap detaches that stale binding before terminal input, without background polling.
- Let human-facing lifecycle slash commands fetch a fresh binding token internally immediately before mutation; plugin tools retain the explicit token so OpenClaw follows an auditable list-then-mutate flow.
- Record terminal binding generations and native-thread transition lineage so sends after new/clear or resume target only the newly verified context.
- Upgrade the Store writer protocol to v3. The first mutation of a v1 or v2 predecessor durably materializes authoritative Session records before publishing the new manifest, quarantines ambiguous bindings, and leaves existing Turn state and event logs unchanged.

### Security

- Serialize native-thread transitions against sends, approvals, monitors, callbacks, and recovery; require an exact idle terminal with no unresolved Turn and fail closed on unsupported, ambiguous, stale, active-elsewhere, or unverifiable native identity evidence.
- Fence old monitors, receipts, approvals, callbacks, and recovery mutations to their original terminal incarnation, native thread, AKK Session, Turn, and binding generation.
- Reject every first-line native slash command at the ordinary send/respond boundary before creating Session, Turn, ledger, or terminal side effects, including lifecycle-changing `/clear`, `/new`, `/resume`, Codex `/fork`/side threads, and Claude `/branch`.

## 0.9.0 - 2026-08-05

### Added

- Add a durable AKK `session_id` for the continuing native coding-agent context and a unique `turn_id` for every accepted terminal dispatch.
- Add an explicit `respond(turn_id, answer)` path for questions and blocked requests that must continue the same in-flight turn.

### Changed

- Make ordinary sends to an existing AKK Session target its `session_id` and create a new Turn, while managed status, approval, cancellation, retry, renewal, and close operations target an exact `turn_id`.
- Keep first attach and raw-terminal control compatibility narrow and list-driven: an unmanaged row may prefill its own `selector` for initial send or `conversation_id` for an advertised raw status, approval, cancellation, or orphan-close action; callers must never construct, guess, or reuse either value.
- Publish the v4 list/action contract with terminal → session → turn history, and include both identities in messages, callbacks, delivery ledgers, and recovery output.
- Treat existing `conversation_id` values as legacy Store aliases; new records keep `conversation_id` equal to `turn_id`, while legacy records receive in-memory identity fallbacks.
- Upgrade the Store writer protocol to v2 and atomically migrate exact v1 manifests on the first mutation while preserving legacy Turn records.

### Security

- Fail closed when native Codex or Claude Code session evidence is unavailable or changes, when persisted identity fields conflict, or when callback identity sources disagree.
- Fence terminal receipts and late callbacks to the exact Store, Session, Turn, message, and native process incarnation so stale work cannot cross execution boundaries.

## 0.8.1 - 2026-08-03

### Fixed

- Keep automatic and manual callback retries config-routed when no durable Gateway token exists, instead of restoring a tokenless explicit URL that OpenClaw rejects.
- Preserve persisted, explicitly authenticated Gateway URL and token pairs across retries without copying credentials into callback delivery state.

## 0.8.0 - 2026-08-01

### Changed

- Make `AKK list` terminal-first: every discovered tmux pane is a single primary `terminals[]` resource with its authoritative current turn or latest retained turn nested below it.
- Replace ambiguous managed-turn `send` hints with `follow_up`, keep historical turns explicitly addressable, and limit default selectors to physical terminal candidates.
- Determine current terminal ownership from the dispatch ledger and suppress side effects when ownership is unresolved, while keeping the pane visible.

### Removed

- Remove the public `delegated[]`, `terminal_controlled[]`, `tasks[]`, legacy `commands`, and `source: "akk_delegate"` list compatibility model.

## 0.7.0 - 2026-08-01

### Changed

- Move managed task state to the permanent `~/.agent-knock-knock/store` root, with a compatibility manifest and conversation data under `conversations/`.
- Let OpenClaw-triggered `list` reconcile all managed tasks and `status` reconcile only its selected task. Standalone shell `list` and `status` stay read-only by default, expose reconciliation only through explicit `--reconcile`, and never change state while resolving a selector.
- Leave the former `~/.agent-knock-knock/conversations` store untouched and ignored. This release does not migrate old managed task records; existing tmux panes remain discoverable for new work.

### Security

- Refuse incompatible Store writers before changing managed state or performing terminal and Gateway side effects.
- Always use the plugin package's bundled relay and remove the configurable external `binPath` override.

## 0.6.2 - 2026-07-31

### Changed

- Publish `AKK list` action contract v2 with machine-readable field semantics that distinguish managed task lifecycle, terminal process liveness, parsed screen activity, deprecated compatibility flags, and the authoritative `available_actions` snapshot.

### Fixed

- Recognize both current `»` and legacy `›` Codex composer markers across idle detection, approval parsing, stale-prompt rejection, completion boundaries, and terminal artifact cleanup while preserving fail-closed working and approval precedence.

## 0.6.1 - 2026-07-30

### Added

- Return per-session `available_actions` and a versioned action contract from `AKK list`, including exact tool names, authoritative target arguments, fresh-status approval prerequisites, and recovery message IDs when currently available.

### Fixed

- Exclude unsupported and retired ACPX executor records from session discovery so historical Cursor or pre-tmux state cannot break valid Codex and Claude Code routing, while active legacy ownership still fences its pane against double dispatch.
- Keep idle cleanup logging safe when it closes an unsupported legacy executor record.

## 0.6.0 - 2026-07-30

### Changed

- Discover and control verified Codex and Claude Code tmux panes across workspaces without project-specific plugin configuration.
- Keep bare delegation fail-closed when multiple idle panes exist, while allowing exact selectors to route safely across projects.
- Revalidate the coding-agent PID, tmux pane identity, and matching process/pane working directory before terminal operations.
- Simplify ClawHub and npm installation, diagnostics, and first-run guidance by removing the top-level workspace setup step.

### Security

- Keep automatic approval disabled by default and scoped only by each trusted rule's exact commands, agents, and one or more `autoApprove.rules[].workspaces` roots.

### Removed

- Remove the top-level plugin `workspace` setting and the corresponding `install-openclaw` and `doctor` workspace options.

## 0.5.2 - 2026-07-30

### Fixed

- Keep macOS tmux workspace revalidation reliable when `lsof` returns usable cwd rows with a partial-failure status.
- Limit cwd lookups to the expected coding-agent PID while retaining ancestry checks and failing closed when target cwd evidence is absent.

## 0.5.1 - 2026-07-29

### Changed

- Put one complete ClawHub-first path from installation through workspace setup, Gateway restart, tmux startup, diagnostics, and the first task at the top of the README.
- Separate direct `/akk` usage from optional natural-language tool access and keep the npm installer as an alternative path.

### Fixed

- Fail closed with actionable setup guidance when the plugin workspace is missing or non-absolute instead of falling back to the Gateway working directory.
- Keep `/akk doctor` available to diagnose invalid workspace configuration.

## 0.5.0 - 2026-07-29

### Changed

- Make already-running, verified-idle Codex and Claude Code tmux panes the only delegation targets.
- Resolve bare `/akk <task>` only when exactly one eligible idle pane exists in the configured workspace, and use `/akk <selector>: <message>` for an explicit target.
- Enforce the configured workspace as a hard boundary even for explicit terminal IDs and recovery operations.
- Keep the main command surface focused on task routing, listing, status, and cancellation; keep diagnostics, approvals, and recovery operations in their relevant workflows.

### Removed

- Remove configuration-based default-agent routing and the `--default-agent` installer option.
- Remove obsolete session inspection and attachment surfaces from the user-facing workflow.

## 0.4.0 - 2026-07-29

### Changed

- Focus Agent Knock Knock on one transparent execution path: shared tmux terminals for Codex and Claude Code.
- Reuse exactly one idle agent pane in the configured workspace and fail closed when no unique safe target exists.
- Prevent a new terminal generation from replacing an active task, persist exact dispatch receipts across stores, and fence uncertain submissions until their owner is explicitly closed.
- Simplify installation, diagnostics, plugin tools, the bundled skill, and documentation around the tmux handoff workflow.

### Removed

- Remove the alternative managed execution stack, blanket background approval, non-tmux agent integration, model/proxy overrides, and callback bootstrap contract.
- Remove obsolete quickstarts, smoke tests, simulations, modules, and maintenance assets for unsupported execution paths.

## Earlier releases

The pre-0.4 history remains available in [GitHub Releases](https://github.com/scotthuang/agent-knock-knock/releases).
