# Codex Project Instructions ## Project intent - Keep this repository a stable, local-first Claude Code monitoring platform. - Maintain correctness across hooks, API, DB, websocket, and UI. ## Priorities - Correctness over cleverness. - Small, scoped, reversible diffs. - Preserve existing behavior unless change is requested. - Update docs whenever workflow or architecture changes — follow `skills/update-project-docs/` automatically at the end of every change-set (README + VN/CN/KO mirrors, ARCHITECTURE, wiki + i18n + cache bump, server/client READMEs, docs/*). - Every applicable source file you create or update (`.js/.ts/.tsx/.cjs/.mjs/.py/.sh/.css`) must start with the authorship header: a truthful file overview plus the exact line `@author Nguyễn Ngọc Trí Vĩ `. See `skills/file-headers/` and `.claude/rules/file-headers.md`; verify with `bash skills/file-headers/scripts/check-headers.sh`. ## Lane stage AgentHub's `codex` (and `antigravity`) lanes carry no pipeline: the dashboard shows no stage for them and never infers or advances one, so there is no `agenthub stage` call to make while you work here as Codex. ## Where to work - `server/` for API/routes/data processing. - `client/` for React UI behavior. - `scripts/` for hook/install/import/cleanup utilities. ## Validation expectations - Backend changes: run `npm run test:server` when possible. - Frontend changes: run `npm run test:client` when possible. - If any check is skipped, report it explicitly. ## Safety expectations - Keep destructive capabilities behind explicit configuration gates. - Never broaden destructive behavior without explicit user request. - Treat hook execution path as fail-safe and non-blocking. ## Useful commands - Setup: `npm run setup` - Dev: `npm run dev` - Build/start: `npm run build` then `npm start`