Skip to content

Releases: BarryBarrywu/codex-zectrix-dashboard

Codex Dashboard for ZECTRIX 0.1.9

Choose a tag to compare

@BarryBarrywu BarryBarrywu released this 24 Aug 11:57

Codex Dashboard for ZECTRIX 0.1.9

Adds the independently sourced reset radar to the 400×300 NOTE4 dashboard. The compact radar distinguishes an active forecast, a recent regular reset announcement, a recent reset-credit announcement, a fresh no-Watch observation, and unavailable evidence without presenting the third-party signal as official account quota.

The Companion requests the public reset-radar status directly at startup and once per hour. Conditional requests, bounded timeouts, a 64 KiB response limit, capability-specific validation, semantic caching, and privacy-safe diagnostics keep this optional source isolated from official quota and task activity.

Task activity now uses a 30-second deadline and official quota a 10-minute deadline. The persistent Companion and its owned app-server session sleep until the nearest source deadline, coalesce overdue observations after wake, avoid heartbeat cache writes, and continue to publish only when visible state changes.

The final 400×300 layout was refined against a physical NOTE4. Official quota now uses a tighter heading-to-number relationship while preserving clear separation between the progress bar, quota guidance, and reset radar. The radar keeps its full-width ten-cell ruler, and the three task rows use a compact, even vertical rhythm with a separately reserved footer.

MVP limitations:

  • the reset radar is a third-party probabilistic signal, not an OpenAI commitment or an account-specific reset time;
  • no exact Desktop unread blue dot synchronization;
  • no 待你 state;
  • no authoritative 检查 state;
  • no plan progress;
  • no task mutation or control;
  • no support for other operating systems;
  • no support for other display models.

Automated fixture, process, and package validation does not constitute installation or physical NOTE4 acceptance. The 0.1.9 layout and changed-frame path were exercised on the development NOTE4, but each installation must still verify its installed companion, source diagnostics, delivery, and physical readability independently.

Codex Dashboard for ZECTRIX 0.1.8

Choose a tag to compare

@BarryBarrywu BarryBarrywu released this 23 Aug 03:42

Codex Dashboard for ZECTRIX 0.1.8

Reuses one persistent Codex app-server session for quota and task observation instead of repeatedly initializing the plugin marketplace. Transport failures now use a bounded 5-second, 30-second, 5-minute, then one-hour reconnect circuit while preserving verified last-known state.

Shutdown and session replacement reap the complete dashboard-owned process tree, including descendants that create independent process groups or sessions. The real-runtime canary now records and verifies owned descendants, staging stability, disk stability, current quota and task activity, and bounded cleanup.

Expired historical running activity no longer makes an otherwise successful observation stale. Slow quota responses receive their own 15-second deadline without weakening the 5-second isolation boundary for other RPCs.

The production-path canary retained one app-server through initialization and ten steady-state minutes with no marketplace staging growth. Two post-install 90-second observations kept the same companion and app-server PIDs, the exact 2 directories / 317,768 KiB / 45 entries retained staging baseline, and current quota and inferred task activity. A physical NOTE4 check then confirmed readable quota data and the completed-turn state on the device.

Normal Codex Desktop operation still writes bounded session logs and state files. This release prevents the dashboard-triggered unbounded marketplace staging growth; it does not claim that macOS System Data remains byte-for-byte static. Multiple ChatCut MCP processes observed after a Desktop restart were owned by Codex Desktop rather than this companion and produced no staging or writable-file growth during the bounded follow-up diagnosis.

MVP limitations:

  • no exact Desktop unread blue dot synchronization;
  • no 待你 state;
  • no authoritative 检查 state;
  • no plan progress;
  • no task mutation or control;
  • no support for other operating systems;
  • no support for other display models.

The validated installation completed a physical NOTE4 check. Each new device installation must still confirm device selection, persisted pageId, first push, subsequent meaningful updates, and physical readability independently.

Codex Dashboard for ZECTRIX 0.1.7

Choose a tag to compare

@BarryBarrywu BarryBarrywu released this 17 Aug 11:51

Codex Dashboard for ZECTRIX 0.1.7

Keeps current Codex quota available when task activity observation is temporarily incompatible, and shows an explicit compatibility notice instead of stale task claims.

Recognized execution-turn lifecycle evidence now survives additive Codex app-server, SQLite, and rollout changes. Unknown or ambiguous evidence remains ignored, diagnostics stay content-safe, and quota publishing continues independently.

MVP limitations:

  • no exact Desktop unread blue dot synchronization;
  • no 待你 state;
  • no authoritative 检查 state;
  • no plan progress;
  • no task mutation or control;
  • no support for other operating systems;
  • no support for other display models.

Automated fixture and package validation does not constitute physical NOTE4 validation. Device selection, persisted pageId, first push, subsequent meaningful updates, and physical readability require a separately authorized real-device check.