OpenParable
Skip to content
← Back to skills

App Server Events Sync

Development
app-server-events-sync

App Server Events Sync is an Agent Skill for development published in the Dimillian/CodexMonitor repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Maintain CodexMonitor and Codex app-server protocol parity. Use when asked to audit supported or missing app-server notifications/requests, trace event routing, diagnose schema drift in app-server payloads, or update docs/app-server-events.md after upstream Codex changes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Dimillian/CodexMonitor/blob/HEAD/.codex/skills/app-server-events-sync/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/app-server-events-sync, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

App-Server Events Sync

Use this skill to keep CodexMonitor app-server integration accurate as ../Codex evolves.

Canonical Source

Start with:

  • docs/app-server-events.md

Treat that file as the canonical runbook and update it when behavior changes.

Workflow

  1. Confirm upstream baseline:
  • Read Codex hash from ../Codex and update the hash in docs/app-server-events.md title.
  1. Compare notification methods:
  • Diff Codex v2 notification method set against CodexMonitor routing in src/utils/appServerEvents.ts and src/features/app/hooks/useAppServerEvents.ts.
  • Update Supported Events and Missing Events sections in docs/app-server-events.md.
  1. Compare request methods:
  • Diff Codex v2 client/server request sets against CodexMonitor outgoing and inbound handling.
  • Update Supported Requests, Missing Client Requests, and Server Requests sections.
  1. Investigate schema drift when lists look unchanged:
  • Inspect v2 payload structs in ../Codex/codex-rs/app-server-protocol/src/protocol/v2.rs.
  • Compare parser and normalization edges in src/utils/appServerEvents.ts, src/features/app/hooks/useAppServerEvents.ts, and src/features/threads/utils/threadNormalize.ts.
  1. Implement support when requested:
  • Add method/type support at parsing edges first.
  • Route in app event hook.
  • Update thread/item reducers and rendering only if needed.
  • Keep app/daemon parity and avoid duplicated logic.
  1. Validate:
  • Run targeted tests for touched files.
  • Run npm run typecheck.
  • Run npm run test for frontend behavior changes.
  • Run cd src-tauri && cargo check for backend changes.

Key Files

  • Routing/types: src/utils/appServerEvents.ts
  • Event router: src/features/app/hooks/useAppServerEvents.ts
  • Handler composition: src/features/threads/hooks/useThreadEventHandlers.ts
  • Item/turn handlers: src/features/threads/hooks/useThreadItemEvents.ts, src/features/threads/hooks/useThreadTurnEvents.ts
  • Normalization: src/features/threads/utils/threadNormalize.ts
  • State: src/features/threads/hooks/useThreadsReducer.ts
  • Outgoing requests: src/services/tauri.ts, src-tauri/src/shared/codex_core.rs
  • Daemon RPC: src-tauri/src/bin/codex_monitor_daemon/rpc.rs and rpc/*

References

  • Quick command set: references/quick-commands.md
  • Canonical runbook: docs/app-server-events.md

Output Expectations

When asked for an audit or update:

  • Report concrete supported and missing method deltas.
  • Cite exact files that need edits.
  • Update docs/app-server-events.md in the same change when behavior changed.
  • Call out deliberate non-support explicitly (for example deprecated methods).