Codex Dashboard for ZECTRIX 0.1.8

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.