Christian Hood
16ba4166f2
Sub-agents must never call td commands directly. Concurrent writes from parallel agents corrupt the SQLite database. Only the orchestrator manages td task lifecycle. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
725 B
725 B
MANDATORY: Use td for Task Management
Run td usage --new-session at conversation start (or after /clear). This tells you what to work on next.
Sessions are automatic (based on terminal/agent context). Optional:
- td session "name" to label the current session
- td session --new to force a new session in the same context
Use td usage -q after first read.
CRITICAL: Sub-agents must NOT call td
Only the orchestrating Claude instance may call td commands. If you are a sub-agent spawned to implement a task, do NOT run td start, td close, td update, or any other td command. Concurrent writes to the SQLite database from parallel agents will corrupt it. The orchestrator manages all task lifecycle calls.