How blader/taskmaster works
Taskmaster enforces explicit completion for coding-agent sessions. A session completes when the agent emits the session-specific done token; otherwise Taskmaster blocks stopping and requests more work. Codex enforcement continues the existing session through its wrapper and PTY bridge, while Claude enforcement uses a Stop hook. Both paths use the shared compliance prompt. The README documents these connections; source excerpts were unavailable, so the graph omits implementation details not established there.
Main entry points: inject-continue-codex.sh Event monitor · check-completion.sh Stop hook · run-taskmaster-codex.sh Codex wrapper · run-codex-expect-bridge.exp Expect PTY bridge
Components 10
Codex enforcement
- Codex wrapper
run-taskmaster-codex.sh - Event monitor
hooks/inject-continue-codex.sh - Expect PTY bridge
hooks/run-codex-expect-bridge.exp
Claude enforcement
- Stop hook
hooks/check-completion.sh - Completion check
check-completion.sh
Shared policy
- Compliance prompt
taskmaster-compliance-prompt.sh
Other components
- User
- Codex CLI
- Codex session logs
- Claude Code
Connections 13
- User → Codex CLI: requests work
- Codex CLI → Codex wrapper: runs through
- Codex wrapper → Codex CLI: launches with logs
- Codex CLI → Codex session logs: writes events
- Event monitor → Codex session logs: watches events
- Event monitor → Expect PTY bridge: requests continuation
- Expect PTY bridge → Codex CLI: injects prompt
- Event monitor → Compliance prompt: uses prompt
- User → Claude Code: requests work
- Claude Code → Stop hook: invokes on stop
- Stop hook → Completion check: runs check
- Completion check → Compliance prompt: uses prompt
- Stop hook → Claude Code: blocks with feedback