// Install, verify, and debug JoelClaw Codex session capture hooks and compare Codex/Claude/Pi capture health.
| name | session-capture |
| description | Install, verify, and debug JoelClaw Codex session capture hooks and compare Codex/Claude/Pi capture health. |
Use when capture health matters. Do not claim sessions are in JoelClaw unless the state/log files and search path prove it.
~/.codex/hooks.jsonjoelclaw-session-capture/scripts/capture-codex-session.js~/.joelclaw/codex-session-state.json~/.joelclaw/codex-capture.log~/.codex/sessions/**/*.jsonlDoctor:
node joelclaw-session-capture/scripts/doctor-codex-session-capture.js
~/.claude/settings.json~/.bun/bin/joelclaw-capture-session~/.joelclaw/claude-session-state.json~/.joelclaw/claude-capture.log~/.claude/projects/**/*.jsonlCurrent risk: the historical Claude hook writes generic session-state.json / capture.log and uses runtime claude-code, so it can look like Pi capture unless the capture script is namespaced.
~/.joelclaw/session-state.json~/.joelclaw/capture.log~/.pi/agent/sessions/**/*.jsonljoelclaw session search first for indexed/cross-machine pointers.Search Joel's Pi, Claude, and Codex session history using the pi-tools session-reader flow. Use when the user asks to search past sessions, recover context, find prior decisions, inspect transcript history, continue old work, find support patterns from previous runs, or verify whether sessions are being captured by JoelClaw.
Resolve project-local issue tracker routing and publish Linear issues safely. Use before creating Linear issues, PRDs, phase breakdown issues, or when deciding whether Linear/GitHub/local docs is the configured tracker. Enforces capability ≠ routing: Linear requires project-local policy, team association, auth, and verified readback.
Create distinctive, crafted TUI components for pi using @mariozechner/pi-tui and @mariozechner/pi-coding-agent. Use when building interactive terminal UIs — custom components, overlays, dialogs, dashboards, widgets, data visualizations, animated elements, game-like interfaces, or any visual TUI work inside pi extensions or custom tools. Triggers on: 'build a TUI component', 'make a dashboard', 'create an overlay', 'interactive widget', 'terminal UI', 'custom component', 'pi-tui', or any request to create visual, interactive terminal interfaces. Also use when beautifying or redesigning existing TUI components.