tasks_add
Creates a dependency-aware task in the ready queue, with optional gates for external blockers. Use it to add work that stays blocked until prerequisites finish or gates clear.
Instructions
Add a task to the dependency-aware ready queue. depends_on lists task ids that must finish first (done or dropped unblocks); each must exist and must not create a cycle. The task is 'ready' once it has no open/in_progress blocker and no open gate. A task that waits on a person or an event outside Seamless carries a gate: gate_who and gate_what on the step itself, or a task of kind gate that the waiting steps depend on, so one gate holds many steps and clearing it frees them all.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>"
},
"name": "tasks_add"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | optional details / acceptance criteria (aliases: content, text) | |
| kind | No | step (the default: work an agent claims and finishes) or gate (a person's action, or an event outside Seamless, that the tasks depending on it wait for: never ready and never claimed; gate_who and gate_what describe it, and clearing it closes it and unblocks its dependents) | |
| plan | No | optional plan slug (plan:<slug> convention) that composes this task as a step of a plan. Plan steps are excluded from the default ready-queue and surfaced under the plan filter. | |
| title | Yes | short task title | |
| project | No | project slug; defaults to the bound/ambient session's project. An unknown slug CREATES that project -- naming a new one is normal and never an error. Pass project=global ONLY for knowledge that belongs in EVERY project's briefing; it is not a neutral default. With no session and no explicit project the call is rejected as ambiguous. A session bound to a confidential or sealed project can write ONLY into that project. | |
| session | No | the session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless | |
| gate_who | No | who must act before this task can go ahead: owner, founder:<name>, sitting:<name>, hardware, sealed:<project>, or free text (one line). With gate_what it gives the task a gate: a step whose gate is open is not ready, and tasks_ready lists it under gated | |
| gate_what | No | what must happen, one line (with gate_who) | |
| depends_on | No | task ids this task is blocked by (a comma-separated string is also accepted) | |
| gate_decision | No | optional: the open question the person answers, one line | |
| gate_ready_when | No | optional: when the task is ready, one line |