v0.5.0

v0.5.0

Date: 2026-05-26

Summary

v0.5.0 productizes codex-wake for supportable Codex and OpenClaw wake
operations. It adds durable OpenClaw plugin install/update helpers, unified
product readiness reporting, explicit state lifecycle docs, a repeatable smoke
harness, and operator support boundaries.

Changes

• Added codex-wake openclaw-plugin install|update|pack for public-tag
  materialization, non-linked OpenClaw plugin install/update, guarded linked
  path pruning, and npm-pack artifact creation.
• Added codex-wake product-readiness --json with normalized readiness checks
  for CLI commands, hooks, skills, repo service, user supervisor, enrolled
  roots, monitor health, Codex app-server dispatch, OpenClaw Gateway RPC,
  OpenClaw plugin readiness, and tmux availability.
• Added codex-wake --version.
• Added codex-wake supervisor run --once --no-dispatch for safe smoke checks.
• Added scripts/product_smoke.py and docs/product-smoke-matrix.md.
• Added docs/runtime-state-lifecycle.md and docs/support-boundary.md.
• Added supervisor root health_status and remediation fields.
• Updated README, daemon-service docs, OpenClaw plugin docs, and the
  codex-wake skill with the productized install/readiness path.
• Bumped the OpenClaw plugin metadata/package version to 0.5.0.

Compatibility

Wake record schema version remains 1. The changes are additive:

• existing wake records remain readable;
• repo-scoped services remain supported;
• user supervisor registry entries remain schema version 1;
• OpenClaw plugin installs should move from linked development paths to the
  public-tag or package-artifact install path;
• no-dispatch smoke paths prove polling/state behavior only, not delivery.

Validation

Productization validation is recorded in:

• docs/dev/verification/0063-2026-05-26-openclaw-plugin-productized-install.md
• docs/dev/verification/0064-2026-05-26-product-readiness-command.md
• docs/dev/verification/0065-2026-05-26-state-lifecycle-retention.md
• docs/dev/verification/0066-2026-05-26-product-smoke-harness.md
• docs/dev/verification/0067-2026-05-26-operator-docs-support-boundary.md
• docs/dev/verification/0068-2026-05-26-live-product-smokes.md

v0.4.15

v0.4.15

Date: 2026-05-26

Summary

v0.4.15 adds monitor-readiness gates and a user-scoped supervisor for
multi-root Codex/OpenClaw wake delivery.

Changes

• Added codex-wake monitor check to report whether an active monitor owns the
  selected wake root.
• Added --require-monitor scheduling gates for CLI-created wakes.
• Added codex-wake supervisor ... commands for explicit wake-root
  enrollment and a user-scoped codex-wake-supervisor.service.
• Added daemon/supervisor monitor health files under user-scoped state.
• Added monitor readiness to doctor --json.
• Hardened the OpenClaw plugin so codex_wake_schedule requires recent
  persistent monitor health by default.
• Exposed OpenClaw plugin monitor defaults in the plugin config schema and
  bumped the plugin package metadata to 0.1.1.
• Updated the codex-wake skill and docs to require monitor readiness before
  unattended wake scheduling.

Compatibility

Wake record schema version remains 1. The changes are additive:

• existing wake records remain readable;
• repo-scoped services remain supported;
• unmonitored manual flows can still use codex-waked --once;
• OpenClaw plugin callers can set requireMonitor=false only for explicit
  manual-daemon workflows.

Validation

Release validation is recorded in:

• docs/dev/verification/0062-2026-05-26-wake-monitor-readiness-user-supervisor.md

v0.4.14

v0.4.14

Date: 2026-05-25

Summary

Releases the OpenClaw Gateway wake transport, the repo-linked OpenClaw
codex-wake plugin, and transport-selection hardening in the agent skill.

Included

• codex-wake openclaw after and openclaw at can create structured
  openclaw_gateway wake records.
• The daemon can dispatch openclaw_gateway records through OpenClaw Gateway
  method agent and preserve Gateway preflight and dispatch evidence.
• OpenClaw wake records reject missing or placeholder session keys so
  no-dispatch smokes cannot masquerade as live OpenClaw readiness.
• The external OpenClaw plugin under plugins/openclaw-codex-wake/ registers
  codex_wake_schedule and /codex-wake for live OpenClaw sessions.
• The plugin writes schema-versioned wake JSON directly without running shell
  commands, and captures trusted agent/session/channel context from OpenClaw.
• The plugin stores Slack/channel/thread metadata as evidence by default and
  writes reply override fields only when explicitly configured.
• The codex-wake skill now requires agents to choose between tmux, Codex
  app-server, and OpenClaw Gateway wake transports before scheduling a wake.
• README, wake schema docs, runbook, and verification notes describe the
  OpenClaw transport and plugin workflow.

Compatibility

• Wake record schema remains version 1.
• openclaw_gateway is an additive target transport.
• Tmux dispatch behavior is unchanged.
• Codex app-server dispatch behavior is unchanged.
• The OpenClaw plugin is released as a repo-linked external plugin in this tag;
  it is not installed by the Python uv tool install path.

Known Limits

• OpenClaw Gateway dispatch requires a real durable OpenClaw session key.
• codex-waked --no-dispatch still proves only trigger evaluation and state
  movement, not OpenClaw, app-server, or tmux delivery.
• Slack-visible OpenClaw proof still requires live channel readback or
  transcript/trajectory evidence after Gateway dispatch.

v0.4.13

v0.4.13

Date: 2026-05-23

Summary

Releases app-server service environment hardening for repo-scoped wake daemons.

Included

• App-server dispatch now resolves the Codex CLI from optional
  target.codex_cmd, CODEX_WAKE_CODEX_CMD, then daemon PATH.
• codex-wake service install can persist CODEX_WAKE_CODEX_CMD into the user
  systemd unit, and --codex-path can set an explicit Codex CLI command.
• codex-wake app after, app at, app status, and
  app candidates --validate support --codex-path.
• codex-wake doctor and doctor --json now report service-side app-server
  Codex readiness.
• Missing app-server command launch failures are recorded as explicit wake
  last_error values instead of looking like app-server protocol failures.
• README, app-server mode docs, wake schema docs, and the codex-wake skill
  now describe the service environment contract.
• P38 validation evidence includes source tests, installed CLI smoke, and an
  installed-service app-server dogfood through a temporary user service.

Compatibility

• Wake record schema remains version 1.
• target.codex_cmd is optional and additive.
• Tmux dispatch behavior is unchanged.
• stdio:// remains the only implemented app-server endpoint for Codex Wake
  dispatch.

Known Limits

• App-server dispatch can resume a thread without showing a visible turn in a
  live tmux pane the operator is watching.
• doctor reports command-resolution readiness, not proof that a specific
  future app-server thread will remain idle.

v0.4.12

v0.4.12

Date: 2026-05-21

Summary

Releases validated app-server candidate discovery.

Included

• Added codex-wake app candidates --validate.
• Added codex-wake app candidates --validate --only-idle.
• Validation checks each candidate with app-server thread/resume and does not start turns.
• JSON candidate rows include validation state and resumed thread status when available.
• Resume failures stay row-local as validation: resume_failed with validation_error.
• README and app-server mode docs now describe validated candidate discovery.
• P34 validation evidence for source tests, source CLI smoke, installed working-tree smoke, and CI.

Compatibility

• Wake record schema remains version 1.
• App-server wake dispatch behavior is unchanged.
• Tmux dispatch behavior is unchanged.
• stdio:// remains the only implemented app-server endpoint for Codex Wake dispatch.

Known Limits

• Validation checks current resumed thread status but does not reserve or lock the thread.
• A thread can become active after validation and before wake registration.

v0.4.11

v0.4.11

Date: 2026-05-21

Summary

Releases local app-server target discovery for rollout-backed Codex threads.

Included

• Added codex-wake app candidates.
• Candidate discovery scans local Codex session rollout metadata under ~/.codex/sessions.
• Discovery reads only each rollout file's first session_meta line and does not emit prompt or transcript bodies.
• Added --json, --cwd, --codex-home, and --limit controls.
• Text output points operators to codex-wake app status --resume <THREAD_ID> before wake registration.
• README and app-server mode docs now describe the candidate discovery flow.
• P33 validation evidence for source tests, source CLI smoke, installed working-tree smoke, and CI.

Compatibility

• Wake record schema remains version 1.
• App-server wake dispatch behavior is unchanged.
• Tmux dispatch behavior is unchanged.
• stdio:// remains the only implemented app-server endpoint for Codex Wake dispatch.

Known Limits

• Candidate discovery identifies local rollout-backed thread ids; it does not prove the thread is currently idle.
• Operators should run codex-wake app status --resume <thread-id> before registering an app-server wake.
• Thread discovery is local to the configured Codex home and session rollout files.

v0.4.10

v0.4.10

Date: 2026-05-21

Summary

Releases resume-backed app-server status checks for persisted Codex threads.

Included

• Added codex-wake app status --resume <thread-id>.
• Kept the default codex-wake app status <thread-id> path on thread/read.
• --resume uses app-server thread/resume and does not start a turn.
• README and app-server mode docs now clarify that app-server wake targets must be resumable rollout-backed threads.
• P32 validation evidence for source tests, source CLI smoke, installed working-tree smoke, and CI.

Compatibility

• Wake record schema remains version 1.
• App-server wake dispatch behavior is unchanged.
• Tmux dispatch behavior is unchanged.
• stdio:// remains the only implemented app-server endpoint for Codex Wake dispatch.

Known Limits

• No live turn completion verification is included in this release.
• Thread discovery remains a future operator surface.

v0.4.9

v0.4.9

Date: 2026-05-21

Summary

Releases app-server thread-status preflight for safer controlled dispatch.

Included

• Added codex-wake app status <thread-id> and --json.
• Added app-server thread/read client support.
• App-server dispatch now records app_server_preflight evidence after thread/resume.
• App-server dispatch calls turn/start only when the resumed thread reports idle.
• Active app-server threads are requeued with backoff instead of receiving a blind new turn.
• README and app-server design docs now describe the status helper and dispatch preflight.
• P30 validation evidence for source tests, source CLI smoke, installed working-tree smoke, and CI.

Compatibility

• Wake record schema remains version 1; new app-server preflight metadata is additive.
• Existing tmux dispatch behavior is unchanged.
• stdio:// remains the only implemented app-server endpoint for Codex Wake dispatch.
• WebSocket dispatch remains deferred behind a concrete operator need and authenticated transport design.

Known Limits

• No live app-server turn/start dogfood is included in this release.
• app status requires a known app-server thread id; thread discovery remains a future operator surface.

v0.4.8

v0.4.8

Date: 2026-05-20

Summary

Releases structured cleanup previews and reports.

Included

• Added codex-wake cleanup --json.
• JSON cleanup output reports mode, retention window, terminal archives, matched archived records, deletion flags, and counts.
• Existing cleanup text output and dry-run defaults are preserved.
• README now documents structured cleanup previews.
• P26 validation evidence for source tests, source CLI smoke, and installed-wheel CLI smoke.

Verified

• Source tests and compileall.
• Local package build from a temporary build venv.
• Installed-wheel smoke for cleanup --archive-terminal --json.
• Clean public tag install and cleanup JSON smoke.
• GitHub Actions CI on the public upstream.

Known Limits

• Cleanup remains an explicit operator action; no automatic cleanup is added.
• cleanup --json does not change status --json; status summaries and cleanup decisions remain separate surfaces.

v0.4.7

v0.4.7

Date: 2026-05-20

Summary

Releases compact wake status summaries.

Included

• Added codex-wake status.
• Added codex-wake status --json.
• Added record-layer status_summary().
• Status summaries include wake root, total count, active total, terminal total, archived total, counts by status, counts by predicate type, counts by target transport, and earliest pending or firing next_attempt_at.
• README now documents the status commands.
• P24 validation evidence for source tests, source CLI smoke, and installed-wheel CLI smoke.

Verified

• Source tests and compileall.
• Local package build from a temporary build venv.
• Installed-wheel smoke for status.
• Installed-wheel smoke for status --json.
• Clean public tag install and status summary smoke.
• GitHub Actions CI on the public upstream.

Known Limits

• status is a compact record summary; use doctor --json for service, hook, and readiness diagnostics.
• The summary is computed from record files on demand and is not a persisted derived index.