You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(tasks): implement task management system with CRUD operations
- Added a new SQL migration to create the `tasks` table with relevant fields and indexes.
- Introduced task management tools for creating, listing, and updating tasks within the system.
- Enhanced the API to support task operations, including endpoints for task creation, retrieval, updating, and deletion.
- Updated documentation to include new task tools and their usage.
- Integrated task management into the agent's workflow, allowing for better task tracking and execution.
Copy file name to clipboardExpand all lines: prompts/en/branch.md.j2
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ Depending on why the channel branched, you might:
22
22
- **Process complex input** — The user said something that requires analysis. Break it down, think through it, return your understanding.
23
23
- **Spawn a worker** — If the user wants something done *now*, spawn a worker for it. Set a status so the channel knows what's happening. Return a summary of what you kicked off.
24
24
- **Save for later** — If the user mentions something they want to do but not right now ("I need to update the tests at some point", "remind me to check the deploy tomorrow"), save it as a **todo** memory instead of spawning a worker. The difference is timing intent: immediate action = worker, future action = todo.
25
+
- **Manage the task board** — For task commands (approve, list, pick up, update progress), use task tools from this branch. Channels do not manage task state directly.
25
26
26
27
## Tools
27
28
@@ -37,6 +38,15 @@ Forget a memory by ID. Use this when the user wants something removed, or when y
37
38
### spawn_worker
38
39
If the user wants something done now and it needs execution tools (shell, file, exec), spawn a worker. Give it a specific task description with enough context to work independently. The worker won't have the conversation history — it only knows what you tell it. If the user is describing something for later rather than requesting immediate action, save a **todo** memory instead.
39
40
41
+
### task_list
42
+
List tasks on the board (optionally by status/priority) before making state changes when you need to verify references.
43
+
44
+
### task_create
45
+
Create structured tasks when the user asks to add planned work to the board.
46
+
47
+
### task_update
48
+
Update task status, priority, subtasks, metadata, or assigned worker. For "pick up #N", move `ready -> in_progress`, spawn a worker, then bind the worker ID to the task.
49
+
40
50
## Rules
41
51
42
52
1. Be concise. The channel is going to read your conclusion and use it in a conversation. Don't write an essay. Return the signal, not the process.
Fork a branch to think independently. The branch gets a clone of your current conversation history and has access to memory_recall, memory_save, and memory_delete tools. It runs independently and returns a conclusion.
1
+
Fork a branch to think independently. The branch gets a clone of your current conversation history and can use memory tools, task tools (task_create/task_list/task_update), and spawn_worker for execution handoff. It runs independently and returns a conclusion.
Create a structured task on the board. Use this when a user asks to add work, capture explicit backlog items, or formalize something actionable. Prefer short titles and concrete subtasks.
List tasks from the board, optionally filtered by status or priority. Use this before task updates when you need to verify a task number or current state.
Update an existing task by task number. You can change status, priority, title, description, subtasks, or metadata. For worker processes, only update the task assigned to that worker.
0 commit comments