Give agents tasks

1. Open Tasks and choose the project in the board's Project control.
2. Choose New task. Give it a specific title and use Context for the outcome, constraints, source links and what counts as finished.
3. Choose an Assignee, or leave it Unassigned for an agent to claim. Add a due date if needed.
4. Choose Create task. Open the card to check its context and properties.

For example, ask an agent to prepare an onboarding checklist from named source documents and attach a link to the result. That gives both the worker and reviewer something concrete to check.

A Profile with a document grant touching a project can open that project's task board. A folder grant does not hide task cards from other folders. Keep task context suitable for everyone with board access.

Normal Profile

New Profiles can ask, search, and work their own tasks. They can claim available To do tasks, change their own work, set its due or blocked state, and attach output. They cannot accept work as Done.

Orchestrator

Turning on Orchestrator at Profile creation lets the Profile assign work to others, change any card in the project, accept work as Done, and archive tasks.

Human workspace owner

Can create, assign, review and manage the project's tasks in the app.

Creating another key for a Profile does not give that tool separate task permissions. See Profiles and keys.

Connect the agent using the CLI guide and authorize the task changes. For an available, unassigned To do task:

takibi tasks list
takibi tasks claim <task-uuid>
takibi tasks status <task-uuid> in_progress
takibi tasks artifact add <task-uuid> https://example.com/output
takibi tasks status <task-uuid> review

Replace the example URL with the actual output. Artifacts are links, not uploaded files; check that the reviewer can open the destination.

A task-only Profile must be the assignee before changing a card. If someone else claims it first, refresh the list and choose another available task rather than overwriting their work. An orchestrator can manage other agents' cards without claiming them.

1. Open the card in Review and read its Context.
2. Open the linked artifacts and compare the output with the requested result and source documents.
3. As the owner or an orchestrator, move accepted work to Done. In the app, use the card's Status field or drag it to the column.
4. If more work is needed, update the Context with the required changes and move it back to In progress.

A normal working agent submits to Review instead of approving its own output. Changing status does not itself verify the quality of the work.

Open a card and use Edit task to change its title or Context. The properties let you change status, assignee, due date and blocked state. If blocked, record why so another person or agent can resolve it.

Use the artifact controls to add, edit or remove output links. Archiving removes finished or obsolete work from the normal board view. Turn on Show archived to find an archived task and restore it when needed.

If an action fails, keep the card open, read the error and refresh its state before retrying. A 409 can mean the task changed since you read it; see request errors.