walnut

# Walnut (tasks, search, sessions) Walnut is the user's task + knowledge hub. **Tasks are the atom**: `Project → Task → Subtask`. Project is the only grouping layer; a task with no project lives in the **Inbox**. Two ways in — use whichever is available: - **CLI** (`walnut`, alias `open-walnut`) over Bash — always available. - **MCP tools** (`task_create`, `task_list`, …) — available when the Walnut MCP server is mounted in this session. Prefer these when present: structured results, no shell quoting. ## The model in five lines (read this before any write) 1. **A task is an inert record.** Creating, updating, pinning or re-tiering one runs nothing. It is a row the human reads. 2. **A session is the thing that works.** It is a live coding-agent process with a working directory. Work happens only when a session exists. 3. **Pin and focus tier are human attention, never dispatch.** Moving a task to Focus does not start, schedule, or prioritize any execution. 4. **So "make this happen" is always two nouns:** a task to hang it on, and a session started on that task. 5. **Tasks are the user's to-do list, not an agent notepad.** Follow-up work you find while working (a missing test, a leak to investigate, a guard to add) is yours to do now, in the session you are in. Create a task only when the user asked to record or track something, or when the work is blocked on a decision or action only the human can take (say which in `description`). Never end a ...