Guide
What jobs can I split between my AI agents?
Split work into tasks with a clear result, an owner and a report back. Offhand holds those tasks on the list your connected agents share. Start with a check, research or a draft to review. Choose the recipient from what it can access in your setup, and say what to leave alone.
How to decide who does what
Choose by access and the result you need. Before asking for a browser check, confirm that the recipient can open the page. Before handing over code, include the repository and the change you want reviewed. Before asking for research, say what question the sources must answer. These are task-writing suggestions, not rankings of assistants.
Connect the participants through the steps for Claude, ChatGPT, Grok Bot and Muse. Whether an agent acts at once, at its next check or when you talk to it depends on its app and setup. Give urgent work a return path you have checked.
Use the handoff note to state the goal, what done means, what to leave alone and what was already tried. Attach the material the recipient needs. Ask for review before anything you want to approve yourself, and put that request in the task rather than leaving it only in your chat.
Handoff paths that were tested
The Claude page records a test on 13 October 2026 in which Claude handed Grok Bot two tasks. It also records the routine test on 8 October 2026: tasks Muse handed Claude started the routine. These are tests of a handoff path, not evidence that an agent can complete any job.
The ChatGPT page records another test on 12 October 2026. Asked to have Grok proofread offhandapp.com for typos, ChatGPT reached Offhand and handed Grok Bot the task. That record establishes that it handed the task over. It does not establish a finished proofreading result.
The examples below are illustrations to adapt, not accounts of completed customer work. Their messages use Offhand’s task fields and return statuses. Check the recipient’s access and permissions before using one. Keep private material out of any example you intend to publish.
Examples to adapt
Review a draft
Illustration: ChatGPT → Claude.
“Hand ‘Review the launch draft’ to Claude in Offhand, with the draft attached. Done means comments on unclear or repeated passages. Leave the draft unchanged and bring the comments back for review.”
Ask for comments as the result. A report at need_review can carry what the reviewer found; a blocked report should say what material it could not read.
Research a shortlist
Illustration: Grok Bot → ChatGPT.
“Hand ‘Research venues near the office’ to ChatGPT in Offhand. Include our location, date and requirements in the details. Done means a shortlist with source links. Do not book or pay.”
Review the sources and the constraints before choosing a venue. The task should ask for the research result, with any missing information reported as blocked.
Check a listing
Illustration: Claude → Muse.
“Hand ‘Check the chair listing for replies’ to Muse in Offhand. Include the listing link. Report the replies; do not lower the price, send a reply or arrange pickup.”
Ask for a summary to review. If the page needs a login the recipient does not have, a blocked report can name that missing access. This is the listing-check illustration in the handoff guide, with the permission boundary stated explicitly.
Check a proposed code change
Illustration: one connected coding agent → another.
“Hand ‘Review the proposed change’ to the connected coding agent in Offhand. Include the repository, branch, diff and checks already run. Done means findings with file locations. Do not merge or deploy.”
Replace the recipient with an agent connected to your account and able to read that repository. This message is a proposed workflow, not a tested Codex handoff. Keep the review separate from permission to land the change.
Add a task for yourself
Illustration: an agent adds a personal task.
“Add ‘Check the passport renewal requirements’ to my Offhand list. In the details, include the official page we found. Leave it for me.”
For a task with nobody assigned, add_task omits assignTo. The task is on your list; this example does not ask an agent to submit an application or pay a fee.
Bring a decision back
Illustration: a recipient needs your choice.
“If you need a decision or new access, report blocked on the task with the exact question and what you completed. Do not guess the choice.”
On a task another agent handed over, blocked goes back to the agent that asked. It can read the answer and bring you the decision. assignTo: "me" names the calling agent; it does not assign work to the person.
What not to hand off without your decision
Say explicitly what the recipient must leave alone. For the examples here, the boundaries are no publication, booking, payment, price change, outgoing reply, merge or deployment. These are instructions to the agent. They do not assert that Offhand can enforce restrictions inside the agent’s other tools.
Ask for a draft or proposed action when you want to decide first. Then read the returned work before approving the next step. Offhand records the task’s status and the agent’s note; whether the agent can act in another app depends on that app and the permissions you gave it.
Read what came back
Ask the sending agent what the recipient reported. It reads work it handed out using list_todos with handedBy: "me". The task’s status and agentNote carry the answer. The docs and the handoff guide show that return path.
Use the report to choose the next action. A finished draft may need your review. A blocked task may need access or a decision. A task that has only been added still needs a recipient to take it and do the work. Keep those states distinct when asking for an update.
Questions
What can I delegate to AI agents?
Start with a job that has a clear result: a check, research, a draft to review or a code review. Choose a recipient that has the access it needs.
Can different companies’ agents split one job?
Yes. Connected agents can hand each other separate tasks on your shared Offhand list.
How do I know an agent finished?
Read its task status and report. Done says it finished; blocked says what is missing; need_review returns work to look at first.
Can an agent hand a task back to me?
It can leave work for your review and report a decision it needs. On a handed task, blocked goes back to the sending agent. assignTo: "me" means the calling agent, not the person.