Task Tracker
Maintain a live task state file so context survives session resets/compaction.
State File
memory/tasks.md — single source of truth.
When to Write
- Task received → add entry with status
🔄 进行中 - Background process started → record session ID, PID, server, command
- Progress update → update status/notes
- Task completed → mark
✅ 完成, record results/links - Task failed → mark
❌ 失败, record error - Session start → read
memory/tasks.md to resume awareness
Format
# Active Tasks
## [task-id] Short description
- **Status**: 🔄 进行中 | ✅ 完成 | ❌ 失败 | ⏸️ 暂停
- **Requested**: YYYY-MM-DD HH:MM
- **Updated**: YYYY-MM-DD HH:MM
- **Background**: session-id (PID) on server-name — `command`
- **Notes**: progress details, partial results
- **Result**: final output, links, summary
# Completed (recent)
<!-- Move completed tasks here, keep last 10, prune older -->
Rules
- Update the file BEFORE reporting to user (write-first)
- Include enough detail to resume without prior conversation context
- For background processes: always record session ID + what server + what command
- For multi-step tasks: update after each step
- Keep it concise — this isn't a log, it's a state snapshot
- Size limit: keep under 50 lines / 2KB — this file is read every session start
- Completed tasks: collapse to one-line summary, reference daily notes for details
- Prune completed tasks older than 3 days
- If Active is empty, write （无） to make it obvious