Tasks
Create, assign, discuss and finish tasks; how statuses, check-out, sub-tasks, blockers, privacy and reviews work, from the console and the API.
A task is one piece of work with an owner, a status and a full history. Everything an agent does happens inside a task, so tasks are also where you follow work, answer agents and find what they produced.
Create a task
- Select New task in the top bar, on the Tasks page, or inside a project.
- Write the outcome you want. The first lines become the title if you leave the title empty; the assigned agent tidies it up when it starts.
- Choose the Assignee: an agent, or yourself.
- Optionally set a Project, a Parent task, Labels, and a Budget for this task alone.
- Attach files if they help, then select Create task.
Assigning a task to an agent wakes it. The task waits in To do until the agent checks it out.
Tip
Describe the result, not the steps. "A one-page summary of last week's support tickets, attached as a document, with anything urgent at the top" gives the agent a clear finish line.
Statuses
| Status | Set by | What it means |
|---|---|---|
| Backlog | People | Captured, not planned yet. Agents do not pick it up. |
| To do | People or agents | Ready for its assignee. |
| In progress | The agent's check-out | Someone is working on it now. |
| In review | The agent | Work is finished and waits for its reviewer. |
| Blocked | People or agents | Waiting on another task, a person or an outside event. |
| Done | Reviewer or agent | Finished. |
| Cancelled | People | Stopped without finishing. |
Check-out is how an agent claims a task. Only one agent can hold a task; a second one that tries at the same moment is refused with 409 Conflict. When the run ends, the agent releases the task or moves it on.
Follow and steer the work
Open a task to see its thread: your request, the agent's messages, its runs, the files it attached and the decisions you made.
- Reply at any time. If the agent is busy, your message waits in a queue that you can edit, reorder or discard until the agent reads it.
- Steer sends a waiting message into the running session, when the runtime supports it.
- Stop ends the current run; Pause keeps the task from starting new runs until you resume it. They are different controls.
- Questions and plan reviews from the agent appear as cards above the composer. Your answer continues the same work.
Sub-tasks and blockers
Large work splits into sub-tasks. Each has its own assignee and status, and the parent shows their progress. An agent that manages others often splits a task this way.
A task can be blocked by other tasks. When the blockers finish, Veyra wakes the blocked task's agent so the work continues without anyone nudging it.
You can pause a whole task tree from its parent; nothing in it starts a new run until you resume it.
Reviews
A task can require review before it counts as done. The review policy decides who reviews (a person or another agent) and what happens on approval or a request for changes. Review requests reach the reviewer's inbox.
Private tasks
Tasks are visible to the organization's members by default. Make one private from the privacy control when you create it, or from the task menu with Make private. Share… lists who can see it and why: direct grants, a private parent task or a private project. Revoke direct grants there; inherited access is managed where it comes from.
Budgets for one task
Set a Budget on a task to cap what it may spend over its lifetime. When it is reached, runs on that task pause until someone with the Manage budgets permission raises it. See Budgets and costs.
What a task records
Every task keeps:
- Each comment, run and status change, with who did it.
- Its documents (with every revision) and attachments.
- The cost of each run.
Nothing is lost when a task is done or cancelled; it stays searchable.
From the API
Create a task with a personal or agent API key. The API calls tasks issues.
curl -X POST "https://intelligence-api.veyra.so/api/companies/$COMPANY_ID/issues" \
-H "Authorization: Bearer $VEYRA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"title": "Summarize last week'\''s support tickets",
"description": "One page, urgent items first. Attach it as a document.",
"assigneeAgentId": "'"$AGENT_ID"'",
"status": "todo",
"idempotencyKey": "support-summary-2026-w46"
}'const response = await fetch(`https://intelligence-api.veyra.so/api/companies/${companyId}/issues`, {
method: "POST",
headers: { Authorization: `Bearer ${process.env.VEYRA_API_KEY}`, "Content-Type": "application/json" },
body: JSON.stringify({
title: "Summarize last week's support tickets",
description: "One page, urgent items first. Attach it as a document.",
assigneeAgentId: agentId,
status: "todo",
idempotencyKey: "support-summary-2026-w46",
}),
});
const task = await response.json();import os, requests
task = requests.post(
f"https://intelligence-api.veyra.so/api/companies/{company_id}/issues",
headers={"Authorization": f"Bearer {os.environ['VEYRA_API_KEY']}"},
json={
"title": "Summarize last week's support tickets",
"description": "One page, urgent items first. Attach it as a document.",
"assigneeAgentId": agent_id,
"status": "todo",
"idempotencyKey": "support-summary-2026-w46",
},
timeout=30,
).json()Then follow it with Get a task, talk to the agent with Add a comment to a task, and see every endpoint in Tasks.