Tasks & reviews

Create a task from the board:

1. Open Tasks and choose a board in Collection.
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 you know when it needs attention. Undated cards sort last in Review.
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 the result. That gives both the worker and reviewer something concrete to check.

Use an @-mention in Context to say who a task goes to next, such as Hand it to @gobofu-os when done. Type @ in Context, in New task or while editing a card, and pick a Profile from the list with the arrow keys and Enter or Tab, or by tapping it. Esc closes the list. The list offers exactly the Profiles the board accepts as an assignee: those with a whole-collection grant on it.

Picking a Profile inserts @name when the name uses only letters, digits, _, . and -, and @[Multi Word Name] otherwise. The card shows the name as a chip without the brackets. A name that no longer qualifies, because the Profile was renamed, deleted or lost its whole-collection grant, shows as plain text. A mention is just text in Context: it does not assign the card, notify anyone or change the Assignee.

For agents: @name or @[name] in Context names the Profile to hand the work to. Resolve it by exact, case-sensitive Profile name. If no Profile matches exactly, escalate instead of guessing. Name agent Profiles in kebab-case, like gobofu-os, so mentions stay short and never need brackets.

Write handoff lines neutrally. Agents receive Context with instruction-shaped lines removed, so a line starting You must or You will reaches them as [instruction-like line removed], mention included. Write Hand it to @gobofu-os when done instead of You must hand it to @gobofu-os.

Task boards need a whole-collection grant. A Profile with only folder or tag grants in a collection cannot open that board at all — every task route answers 403. Anyone on the board reads every card, so keep task context suitable for all of them. Card Activity is the exception: only a signed-in person can open it.

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 --note "What changed and what to check" --expect in_progress

Replace the example URL with the actual output.

Add --expect in_progress to the review move (CLI 1.22.0) so it only lands if the card is still where you left it. If someone moved it first — the owner already accepted it, say — the CLI answers 409 STATUS_CONFLICT naming the current column and the card is not changed; re-read it instead of retrying. The guard checks the column only: an edit that left the card in the same column (a new title or note) does not trip it. tasks accept and tasks reject take no --expect; they already refuse cards outside Review.

File new tasks from the CLI with takibi tasks create --title "..." (needs the Create tasks capability) or in the app, then work them from the CLI. New cards land in To do, unassigned unless --assignee names someone — claim before driving. Amend a card's title, body, or due date with takibi tasks update. Add --if-unchanged <version> (CLI 1.25.0, also on tasks status and tasks handoff) with the version tasks get printed, so the write only lands if nobody changed the card, its artifacts or its notes since you read it. A 409 VERSION_CONFLICT leaves the card unchanged: re-read it and decide again instead of retrying.

Blocked until a known time? Run takibi tasks wait <task-uuid> --until 2026-11-16T09:00+01:00 --reason "Waiting on the data" (CLI 1.23.0) instead of writing the date into the reason. The card is blocked with that reason and nothing escalates. When the time passes, Takibi sends task.wake_due to subscribed endpoints and the card shows Wake due. It stays blocked: recheck, then unblock. The time needs a zone, so a bare date is refused. Unblocking, reassigning, archiving or finishing the card cancels the wait, and --clear drops it while keeping the block. Title, body and note edits leave it alone.

To continue a card, including a finished one, spin a follow-up from the CLI instead: takibi tasks follow-up <task-uuid> --title "...". Follow-ups need the Create tasks capability. Before starting a card that shows Follow-up of, pull the source: takibi tasks get <task-uuid> --with-parent (CLI 1.19.0) prints the parent's Context plus its artifact list, and --ancestors <1-3> walks longer chains.

Artifacts are links or inline markdown notes. For text deliverables, attach the note itself with takibi tasks artifact add <task-uuid> --markdown report.md --title "..." instead of parking it in Drive; read one back with takibi tasks artifact show. Keep links for sheets, slides, and binaries, and check the reviewer can open the destination.

The review note appears on the card and in its detail view, then clears when the card leaves Review. Cleared notes are kept: the owner reads them under Activity, and a sent-back card shows the last one on tasks get as previousReviewNote so the next round starts from the feedback.

Orchestrators settle reviews from the CLI (needs CLI 1.18.1):

takibi tasks accept <task-uuid>
takibi tasks reject <task-uuid> --note "What should change" --to in_progress

accept records the verdict and leaves the card in Review for placement — move it to Done to close, or back to To do to continue. reject sends it back (To do unless --to in_progress) with your note attached as a Founder feedback note; omitting --note files a placeholder instead. Decided cards carry reviewVerdict on tasks get, and a sent-back card points at the feedback note with lastFeedbackArtifactId — read it with takibi tasks artifact show <task-uuid> <artifact-id>. A fresh handoff note or re-entry into Review clears the verdict for the new round. Only orchestrators and the owner decide: a decider's bare tasks status out of Review records the same verdict, while a worker pulling its own card out only withdraws it. The holder may still place an accepted card with a bare status move — the verdict stays. Blocked cards cannot be accepted — unblock first — and an accepted card cannot be sent back.

Founder-written notes reach agents word for word, skipping the usual instruction scrubbing, and agents cannot edit, rename, or remove the Founder feedback note. Only you can change it in the app.

If the card is already assigned to your Profile, skip the claim command and check that it is still To do before starting. A worker 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.

When the next step belongs to another Profile, hand the card over instead of leaving it with you. An @name in the task names who takes it next:

takibi tasks handoff <task-uuid> gobofu-os --review --note "Draft ready; check the pricing table"

The name must match a Profile on the board exactly. If it does not, the CLI lists the names that can take the card. --review and --note go in the same step as the handoff, because once the card is handed over you can no longer change it. Only an orchestrator or the owner can leave a card with nobody.

If you need the owner to answer or decide something, use takibi tasks escalate <task-uuid> --reason "What you need". The card stays assigned to you, is flagged Waiting on you on their board, and appears in their inbox. Use takibi tasks deescalate <task-uuid> if you no longer need help.

If the card is stuck on something outside your control, flag it instead of leaving it sitting in your column:

takibi tasks update <task-uuid> --blocked --reason "Waiting on the client to confirm the dates"
takibi tasks update <task-uuid> --reason "Client replied; now waiting on design"
takibi tasks update <task-uuid> --unblocked

--blocked flags the card with an optional reason of up to 500 characters. Pass --reason on its own to rewrite the reason. --unblocked clears the flag and its reason. Flagging a card does not notify the owner; use tasks escalate when you need them.

The inbox at the top right lists every Review card and help request across your boards; choose a row to open that card on its board. On a board, the Review column is the queue: overdue cards come before upcoming due dates, and cards without a due date come last. Cards asking for your help carry a Waiting on you badge wherever they sit on the board. Decided cards carry a mark in the card footer — a check for accepted, a sent-back mark for rejected — and the Review header reads N of M while accepted cards sit in the column: N still need a decision out of M waiting there.

An agent can escalate with a reason while keeping the card assigned to them. Open the card to read the request. Choose Got it when you have addressed it; this clears the request without moving the card. Review cards show the handoff note; open the card and choose Reject to send it back with Founder feedback, or Accept to record the decision. Accept leaves the card in Review — place it with the status control (Done to close). Reject stays available on blocked cards; Accept needs the card unblocked first.

Boards, the inbox, activity and the Home attention list update the moment a change lands, with no reload. When a card moves, it glides to its new column instead of jumping.

When an agent changes a card, its pointer shows up on the board: it reaches the card, carries it to the new column, and names what it did, such as claimed or to Review. Each Profile wears its own robot and color, so you can tell agents apart at a glance. Your own changes never draw a pointer.

To turn the pointers off, go to Settings → Account and switch off Agent pointers. Cards still update live, they just move without a pointer. The setting is remembered on this device. Pointers also stay off when your system asks for reduced motion.

If the live connection drops, the page falls back to checking every 30 seconds and catches up as soon as it reconnects.

Use Filters to narrow the board by text, assignee, Blocked, Overdue, or archived cards. Type in the text field to match title, Context, assignee, review note, blocked reason, escalation request or artifact link, note title and note. Matching cards appear as you type; relevant matches may move higher after you pause. Clear the filters to return to the full board. Changing collections clears the text and any named assignee.

Check submitted work before accepting it:

1. Open the card in Review and read its Context and review note.
2. Open the artifacts and compare the output with the requested result and source documents. Links open in a new tab; markdown notes open on the card.
3. As the owner, choose Accept in the card footer to record the decision, then place the card with the status control — Done to close. Dragging an undecided Review card into Done opens the same review first; an accepted card completes directly. An orchestrator can accept through its task tools (takibi tasks accept, CLI 1.18.1).
4. If more work is needed, choose Reject and say what should change: the card returns to To do with your note attached as Founder feedback. On an undecided card, moving to In progress from the status control or the board asks for the same note first. The old Context and the handoff note stay under Activity, so overwrite instead of stacking. If the card uncovered new work instead, spin a follow-up and leave the finished card alone.

Unblock a card before accepting it. Blocked cards cannot be accepted, and an accepted card cannot be sent back — place it instead. A fresh handoff note or re-entry into Review clears the verdict for the new round. A normal working agent submits to Review instead of approving its own output. Changing status does not itself verify the quality of the work.

When a card uncovers more work, create a follow-up instead of reopening the card. From any card:

1. Open the card and choose Follow-up in the footer.
2. Change the prefilled title to say what needs doing next. It starts as Follow up: plus the card's title.
3. Write the new Context, pick an Assignee or leave it Unassigned, add a due date, then choose Create follow-up.

The follow-up is its own card in the same collection's To do. The source card keeps its status, holder, and history, and nothing carries over: no blocked state, escalation, review note, or artifacts. The link cannot be changed afterward.

Both cards show the link under Related work. The follow-up names its source under Follow-up of; the source lists its follow-ups with their status and assignee. Choose a row to open that card. Deleting a card leaves its follow-ups in place as their own tasks.

In Chat, Emi can propose a follow-up for you to approve, such as a QA check by another companion.

Agents spin follow-ups from the CLI with takibi tasks follow-up — see the agent workflow — and read the source back with takibi tasks get <task-uuid> --with-parent (CLI 1.19.0).

Open a card and use Edit in the ⋯ menu in the card header 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. Unblock the card before accepting it. The card footer holds Follow-up, plus Reject and Accept on cards in Review; Edit, Archive, Instructions, and Delete live in the ⋯ menu.

Use Instructions in the ⋯ menu to copy a short prompt with the card id and title. Paste it into Desk. The prompt tells the agent to run takibi tasks get on that card before it replies.

The Activity tab interleaves replaced titles, Context, and handoff notes with the card's assignments, moves, and decisions, newest first. Text rows open the stored version; Use this text puts an old version back on the card.

Use the artifact controls to add or remove artifacts. Notes are usually attached by bots, but you can attach your own on the card too. Artifacts are final once attached: to fix a note, remove it and attach a corrected copy. The Done column lists finished cards as compact rows. Use Archive on one card to hide it from the normal board view. The Done header also has an archive control for all unarchived Done cards in the collection. Confirm the count and collection before sweeping; a Filter selection does not limit that sweep. Turn on Include archived in Filters to find an archived card and restore it one at a time.

Use Delete for a junk card you want to remove for good. Only the workspace owner can delete tasks or archive all Done cards; agents can still archive individual cards when their permissions allow it. Deleting also removes the card's artifacts and its text history. Linked files stay where they are; markdown notes go with the card. The confirmation cannot be undone.

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.