CodexMonitor
AGENTS.md4.3k starsChanged 8 months agoMITView on GitHub
All docs must be canonical, with no past commentary, only live state. This file is the agent contract for how to work in this repo. Detailed navigation/runbooks live in: CodexMonitor is a Tauri app that orchestrates Codex agents across local workspaces. For backend behavior changes, follow this order: If you add a backend command, update all relevant layers and tests. Use project aliases for frontend imports: For broader path maps, use docs/codebase-map.md. For Queue vs Steer follow-up behavior, start here:
- Installs packages
Trending
Quiet since June.thin dataabout the whole repository
Who's talking about Dimillian/CodexMonitor
- @dimillian.app“For those who are not terminally ill, I've created a macOS Codex Application that can manage any number of …”Bluesky · Jan 15, 2026 · 22 likes
- @dimillian.app“You use this app github.com/Dimillian/Co...”Bluesky · Jan 24, 2026 · 3 likes
- @github-trending-js.bsky.social“📦 Dimillian / CodexMonitor ⭐ 3,016 (+76) 🗒 TypeScript An app to monitor the (Codex) situation”Bluesky · Mar 12, 2026 · 2 likes
- A Hacker News story“Codex Monitor”Hacker News · Mar 10, 2026 · 2 points
- @librecanada.bsky.social“GitHub - Project Page - "Dimillian/CodexMonitor: An app to monitor the (Codex) situation"... …”Bluesky · Jan 21, 2026 · 2 likes
The biggest 5 of 13 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 13
Talked about on GitHub, Bluesky and Hacker News (13 times).
On GitHub · 7
- Jun 21, 2026Add platform: CodexMonitor — jrdevelopr/ai-builders-toolkit0 reactions
- Jun 8, 2026PRD: Change Request Review — harrryyd/h-code0 reactions · 1 comment
- May 30, 2026[Request]: CodexMonitor — ScoopInstaller/Extras0 reactions
- Mar 18, 2026feat: add CodexMonitor tracker adapter — Dimillian/symphony0 reactions
- Jan 31, 2026[Bug]: Error: 401 Missing authentication token — getsentry/MobileBuildMCP0 reactions · 3 comments
2 more on GitHub
- Jan 27, 2026CodexMonitor:专为开发者设计的本地 Codex AI 智能体编排与协作中心 — jaywcjlove/quick-rss0 reactions · 1 comment
- Jan 12, 2026feat: Add sidebar workspace collapse — nedimf/CodexMonitor0 reactions
On Bluesky · 4
- Jan 15, 2026For those who are not terminally ill, I've created a macOS Codex Application that can manage any number of agents across multiple projects… — @dimillian.app22 likes and reposts · 1 reply
- Jan 24, 2026You use this app github.com/Dimillian/Co... — @dimillian.app3 likes and reposts · 1 reply
- Mar 12, 2026📦 Dimillian / CodexMonitor ⭐ 3,016 (+76) 🗒 TypeScript An app to monitor the (Codex) situation — @github-trending-js.bsky.social2 likes and reposts
- Jan 21, 2026GitHub - Project Page - "Dimillian/CodexMonitor: An app to monitor the (Codex) situation"... github.com/Dimillian/Co...… — @librecanada.bsky.social2 likes and reposts
On Hacker News · 2
- Mar 10, 2026Codex Monitor2 points
- Jan 15, 2026Codex Monitor: An app to minitor your (Codex) situation1 point
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
23 rules. About 0 are common, 15 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
All docs must be canonical, with no past commentary, only live state.
- Very specific: line 25
Put shared/domain backend logic in src-tauri/src/shared/* first.
- Distinctive: line 26
Keep app and daemon as thin adapters around shared cores.
- Distinctive: line 27
Do not duplicate logic between app and daemon.
- Distinctive: line 28
Keep JSON-RPC method names and payload shapes stable unless intentionally changing contracts.
- Distinctive: line 29
Keep frontend IPC contracts in sync with backend command surfaces.
- Distinctive: line 40
If you add a backend command, update all relevant layers and tests.
- Very specific: line 44
Keep src/App.tsx as composition/wiring root.
- Distinctive: line 49
Keep presentational UI in feature components.
- Very specific: line 50
Keep Tauri calls in src/services/tauri.ts only.
- Very specific: line 51
Keep event subscription fanout in src/services/events.ts.
- Distinctive: line 55
Use project aliases for frontend imports:
- Very specific: line 82
Never resurrect hidden threads during reconciliation (hiddenThreadIdsByWorkspace still wins).
- Distinctive: line 97
When changing backend behavior that can run remotely:
- Very specific: line 107
Use existing design-system primitives and tokens for shared shell chrome.
- Very specific: line 108
Do not reintroduce duplicated modal/toast/panel/popover shell styling in feature CSS.
- Very specific: line 114
Prefer safe git operations (status, diff, log).
- Distinctive: line 115
Do not reset/revert unrelated user changes.
- Distinctive: line 116
If unrelated changes appear, continue focusing on owned files unless they block correctness.
- Distinctive: line 117
If conflicts impact correctness, call them out and choose the safest path.
- Distinctive: line 122
Run validations based on touched areas:
- Distinctive: line 127
Use targeted tests for touched modules before full-suite runs when iterating.
- Distinctive: line 156
Use extra care in high-churn/high-complexity files:
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CodexMonitor Agent Guide
All docs must be canonical, with no past commentary, only live state.
Scope
This file is the agent contract for how to work in this repo. Detailed navigation/runbooks live in:
docs/codebase-map.md(task-oriented file map: "if you need X, edit Y")docs/multi-agent-sync-runbook.md(upstream../Codexsync checklist for multi-agent/config behavior)README.md(setup, build, release, and broader project docs)
Project Snapshot
CodexMonitor is a Tauri app that orchestrates Codex agents across local workspaces.
- Frontend: React + Vite (
src/) - Backend app: Tauri Rust process (
src-tauri/src/lib.rs) - Backend daemon: JSON-RPC process (
src-tauri/src/bin/codex_monitor_daemon.rs) - Shared backend source of truth:
src-tauri/src/shared/*
Non-Negotiable Architecture Rules
- Put shared/domain backend logic in
src-tauri/src/shared/*first. - Keep app and daemon as thin adapters around shared cores.
- Do not duplicate logic between app and daemon.
- Keep JSON-RPC method names and payload shapes stable unless intentionally changing contracts.
- Keep frontend IPC contracts in sync with backend command surfaces.
Backend Routing Rules
For backend behavior changes, follow this order:
- Shared core (
src-tauri/src/shared/*) when behavior is cross-runtime. - App adapter and Tauri command surface (
src-tauri/src/lib.rs+ adapter module). - Frontend IPC wrapper (
src/services/tauri.ts). - Daemon RPC surface (
src-tauri/src/bin/codex_monitor_daemon/rpc.rs+rpc/*).
If you add a backend command, update all relevant layers and tests.
Frontend Routing Rules
- Keep
src/App.tsxas composition/wiring root. - Move stateful orchestration into:
src/features/app/hooks/*src/features/app/bootstrap/*src/features/app/orchestration/*
- Keep presentational UI in feature components.
- Keep Tauri calls in
src/services/tauri.tsonly. - Keep event subscription fanout in
src/services/events.ts.
Import Aliases
Use project aliases for frontend imports:
@/*->src/*@app/*->src/features/app/*@settings/*->src/features/settings/*@threads/*->src/features/threads/*@services/*->src/services/*@utils/*->src/utils/*
Key File Anchors
- Frontend composition root:
src/App.tsx - Frontend IPC wrapper:
src/services/tauri.ts - Frontend event hub:
src/services/events.ts - App command registry:
src-tauri/src/lib.rs - Daemon entrypoint:
src-tauri/src/bin/codex_monitor_daemon.rs - Daemon RPC router:
src-tauri/src/bin/codex_monitor_daemon/rpc.rs - Shared workspaces core:
src-tauri/src/shared/workspaces_core.rs+src-tauri/src/shared/workspaces_core/* - Shared git UI core:
src-tauri/src/shared/git_ui_core.rs+src-tauri/src/shared/git_ui_core/* - Threads reducer entrypoint:
src/features/threads/hooks/useThreadsReducer.ts - Threads reducer slices:
src/features/threads/hooks/threadReducer/*
For broader path maps, use docs/codebase-map.md.
Thread Hierarchy Invariants
setThreadsreconciliation must preserve incoming order while retaining required local anchors (active/processing/ancestor summaries) when payloads are partial.- Never resurrect hidden threads during reconciliation (
hiddenThreadIdsByWorkspacestill wins). useThreadRowsrenders children under parents only when parent summaries are present in the visible list; missing parent summaries will promote children to roots.
Follow-up Behavior Map
For Queue vs Steer follow-up behavior, start here:
- Settings model + defaults:
src/types.ts,src/features/settings/hooks/useAppSettings.ts - Settings persistence/migration:
src-tauri/src/types.rs,src-tauri/src/storage.rs - Composer runtime behavior:
src/features/composer/components/Composer.tsx - Send intent routing:
src/features/threads/hooks/useQueuedSend.ts,src/features/threads/hooks/useThreadMessaging.ts - App/layout wiring:
src/features/app/hooks/useComposerController.ts,src/features/layout/hooks/layoutNodes/buildPrimaryNodes.tsx,src/App.tsx
App/Daemon Parity Checklist
When changing backend behavior that can run remotely:
- Shared core logic updated (or explicitly app-only/daemon-only).
- App surface updated (
src-tauri/src/lib.rs+ adapter). - Frontend IPC updated (
src/services/tauri.ts) when needed. - Daemon RPC updated (
rpc.rs+rpc/*) when needed. - Contract/test coverage updated.
Design System Rule (High-Level)
Use existing design-system primitives and tokens for shared shell chrome. Do not reintroduce duplicated modal/toast/panel/popover shell styling in feature CSS.
(See existing DS files and lint guardrails for implementation details.)
Safety and Git Behavior
- Prefer safe git operations (
status,diff,log). - Do not reset/revert unrelated user changes.
- If unrelated changes appear, continue focusing on owned files unless they block correctness.
- If conflicts impact correctness, call them out and choose the safest path.
- Fix root cause, not band-aids.
Validation Matrix
Run validations based on touched areas:
- Always:
npm run typecheck - Frontend behavior/state/hooks/components:
npm run test - Rust backend changes:
cd src-tauri && cargo check - Use targeted tests for touched modules before full-suite runs when iterating.
Quick Runbook
Core local commands (keep these inline for daily use):
npm install
npm run doctor:strict
npm run tauri:dev
npm run test
npm run typecheck
cd src-tauri && cargo checkRelease build:
npm run tauri:buildFocused test runs:
npm run test -- <path-to-test-file>Hotspots
Use extra care in high-churn/high-complexity files:
src/App.tsxsrc/features/settings/components/SettingsView.tsxsrc/features/threads/hooks/useThreadsReducer.tssrc-tauri/src/shared/git_ui_core.rssrc-tauri/src/shared/workspaces_core.rssrc-tauri/src/bin/codex_monitor_daemon/rpc.rs
Canonical References
- Task-oriented code map:
docs/codebase-map.md - Multi-agent upstream sync runbook:
docs/multi-agent-sync-runbook.md - Setup/build/release/test commands:
README.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

