Hand off a task
Give a plan task, or any request, to Pytheus or a teammate in two clicks. You stay where you are, and the plan row shows who has it and how it is going.
Updated 2026-10-13
Hand off gives a piece of work to Pytheus, to a teammate, or to yourself, as a tracked task. There is one dialog for all of it. The task gets its own channel in HQ and a progress log, and the plan row shows where it stands. Nothing opens a separate workspace, and nothing takes you away from what you were doing.
Two clicks from the plan
- Press Hand off on the task. Every task on the plan ends with a labelled Hand off button. It is always visible, on a phone too.
- Press Hand off in the dialog. Pytheus is the owner to begin with, and “Done when” starts as the task’s open steps. Change either, or leave them. On a phone or tablet the dialog is a bottom sheet.
You stay on the plan. The row now shows who has the task and what they are doing, and the plan task moves to In progress if it had not started. A toast has a Watch button that opens Watch on the work.
Other places to start
| Where | What happens |
|---|---|
| A plan row | The Hand off button opens the dialog on that task. |
| Home | The Hand off today’s task card opens the plan on today’s task with the dialog open. The hero’s Start task button opens the task itself. |
| Work in HQ | The next three plan tasks nobody has been given each have a Hand off button. |
| HQ’s New menu and the composer’s + menu | Hand off a task opens the dialog with an empty task. Type what you want done. |
| The command palette | Press Cmd+K or Ctrl+K and choose Hand off a task. |
A request that is not on your plan works the same way: open the dialog from one of the last three places and type the task.
What is in the dialog
| Field | What it does |
|---|---|
| Who does it | Pytheus, one of your teammates, or Me. When the task reads like a teammate’s job, one tap offers them. Teammates are on Base and Premium. With Me the button reads Keep it, and Pytheus checks in on you. |
| Task | A short title. |
| Done when | One checkable line each. The work is checked against these lines before it comes back. |
| What should come back | A slide deck, a spreadsheet, a document, a website, or just an answer. Leave it empty and Pytheus reads what is wanted from the task. The choice decides what counts as delivered. |
| More | The brief (context, constraints, links), a credit budget, whether to send the work back to improve when a check fails, and how often to check in on work you keep. |
What the plan row says
After a hand-off the row ends in one chip. It is decided from the task, its current run and the files it made. A run that ended without what was asked is never shown as ready or done.
| The chip says | What it means | What you can do |
|---|---|---|
| Hand off | Nobody has the task. | Hand it off. |
| Sam · Queued | Waiting for a free slot. | Watch. |
| Sam · Reading acme.com · 40% | Working. It shows the step it is on. | Watch. |
| Checking Sam’s work | Being scored against “Done when”. | Watch. |
| Needs your OK, Sam has a question, Needs Gmail | The run is parked on you. | Resolve it; the item opens in Needs you. |
| Ready to review · 3 files | It passed its checks and waits for you. | Review. The viewer opens with Approve. |
| Partly done · 2 of 3 files | Some of what you asked for was made. | Review, or Continue. |
| No file made | A file was asked for and none was saved. | Continue, or Retry. |
| Ran out of steps | It used its steps before it finished. | Continue, or Retry. |
| Didn’t finish · reason | The run failed. | Retry. |
| Done · deck.pptx | You approved it. | Open. |
| You | It is yours. | Nothing to do. |
Continue carries on the same run with the same conversation. Retry starts the work again.
Links that used to open a workspace
Pythe no longer has a separate workspace per task. A saved link to /roadmap/<id>/task/<task> opens that task on its plan page. Opening it only navigates: it never starts a run or hands anything off. A saved link to /delegation/<id> opens HQ. The canvases those old workspaces made are kept in the Library, read-only.
From another AI app
Claude, ChatGPT, Cursor and Codex hand work to your team with the MCP tool assign_task. See MCP: AI team tools. They cannot approve anything.