CodexDashBoard

Was war die Idee?

CodexDashBoard Lightweight native dashboard for Codex on Linux.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 27 TODO/FIXME-Hinweise, 2 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

Score-Reasons

• git repo
• 27 TODO/FIXME/WIP hints
• README present
• agentized
• plans/backlogs found

TODO/FIXME-Auszug

• /home/smlflg/Projekte/CodexDashBoard/README.md:11 — - quick actions for resume, open folder, refresh, and safe process stop
• /home/smlflg/Projekte/CodexDashBoard/.hermes_async/jobs/audit-2026-05-03-codexdashboard-crash-risk/result.json:59 — "next_action": "Review diff. If acceptable, run a controlled headless/GUI smoke in a guarded environment before enabling or starting the user service."
• /home/smlflg/Projekte/CodexDashBoard/artifacts/codex-audit/top-tasks.json:21 — "why": "Headless tests cover startup/import safety but not most GUI behavior: buttons, dialogs, row contents, tray menu, refresh status updates, or xdg-open/resume command construc
• /home/smlflg/Projekte/CodexDashBoard/artifacts/codex-audit/top-tasks.json:23 — "unit-test command construction for resume/open-folder without launching processes",
• /home/smlflg/Projekte/CodexDashBoard/artifacts/codex-audit/repo-audit.md:14 — - src/codex_dashboard/app.py: GTK UI, tray integration, refresh orchestration, process stop/resume/open-folder actions.
• /home/smlflg/Projekte/CodexDashBoard/artifacts/codex-audit/repo-audit.md:35 — 6. GUI behavior is mostly untested because tests avoid importing GTK. That is useful for headless CI but leaves click wiring, row rendering, dialogs, tray behavior, search debounce