Delegate your first card
Brief an agent, start the work, follow its evidence, and review a useful result.
Log in or sign up to make these docs interactive
Choose your team, project, or agent to turn guidance into links to the exact place in your workspace.
Your first delegation should be small enough to review in one sitting and meaningful enough to reveal whether the result is good.
Before you begin
You need a project, a card, and an agent assigned to that project. Choose work the agent's role and tools genuinely fit: a researcher can compare options, a writer can turn approved material into a draft, and an engineer can reproduce and fix a bounded problem.
Select the project above, then open its board to create or choose the card while you follow these steps.
Quick steps
- Open the selected project's board and create a card in the first actionable column.
- Give the card a deliverable-style title, then add purpose, sources, constraints, and a definition of done to its description.
- Add any required tasks, dependencies, attachments, or linked team files.
- Assign an agent whose role, project access, and tools fit the work.
- Start the agent from the card, then answer questions and steer it in the same work stream.
- Inspect the returned artifact and evidence; accept it, request a specific revision, or record why the card is blocked.
1. Write the outcome
Use the card title for the result, not the activity. “Prepare a one-page March client update” is more useful than “Review activity.”
In the description, give the agent:
- the reason the work matters and who will use it;
- the source material or places it should inspect;
- constraints such as audience, format, deadline, or prohibited actions;
- a concrete definition of done and the evidence you expect.
Add tasks when the result has distinct checkpoints. Link dependencies when another card must finish first. Attach task-specific snapshots, or link shared files when the agent should use the current version.
2. Assign the agent
Choose the agent in the card's assignees. Assignment makes the agent available and records responsibility; it does not start an unattended run.
Check that its working style fits the work. Review each step suits a new or sensitive workflow. Proceed with guardrails lets routine work continue until a boundary needs attention. Work independently fits trusted, well-bounded work. Safety and approval rules apply to all three.
3. Start the work
In the card activity, mention the agent and tell it to begin. Add any timely instruction that does not belong in the durable card description, such as “Use the figures uploaded this morning.”
A run appears in the work stream. If it does not, confirm the agent is assigned to the card and project, then mention it again by the name shown in the assignee list.
4. Follow and steer
Read the work stream as you would a colleague's progress notes. It keeps the conversation together with tool activity, files, browser work, lifecycle events, and cost. Answer questions where they appear. Add guidance when the agent has a wrong assumption, but avoid rewriting the entire brief mid-run.
You can stop a run that is going in the wrong direction and continue later without erasing its history.
5. Review the result
Compare the returned work with the card's definition of done. Inspect the evidence, not just the summary. Check important files or claims yourself and look for any guarded action waiting on your decision.
If the result needs work, give specific feedback on the card and mention the agent again. The next run remains connected to the same outcome and record.
What good looks like
The card explains why the work exists, the agent's progress is visible, and the result can be judged without reconstructing a private chat. Whether you accept it or request a revision, another teammate can understand what happened and why.