TUNC.AI / Tunc Orb guides

Hand off work between agents with a shared record and log

One agent leaves the task, its results and notes in Tunc Orb; the next agent, in any app, picks it up where it stopped.

Updated

A long task often moves between agents: research in ChatGPT, code in Claude Code, a review in Cursor, a scheduled BOT overnight. Each one starts without the others' context. Put the hand-off in Tunc Orb: one record for the task's current state and one log for its history. Every agent you connect can read both.

The task record

data_write {
  "operation": "create",
  "name": "handoffs/pricing-page",
  "about": "Hand-off: rewrite the pricing page",
  "value": {
    "status": "open",
    "goal": "Show the free plan and the storage add-on on one page",
    "done": ["copy draft in docs/pricing.md"],
    "next": "Review the draft against the checkout code",
    "claimed_by": null
  }
}

Claim it so two agents never take the same task

The next agent claims the task with a JSON Patch whose first operation is a test. If another agent claimed it first, the test fails and nothing changes:

data_write {
  "operation": "patch",
  "name": "handoffs/pricing-page",
  "if_revision": "rev_…",
  "patch": [
    { "op": "test", "path": "/status", "value": "open" },
    { "op": "replace", "path": "/status", "value": "claimed" },
    { "op": "replace", "path": "/claimed_by", "value": "Claude Code on the laptop" }
  ]
}

Notes in a log

Each agent appends what it did to handoffs/pricing-page/log. The writer on every entry shows which connection added it, so the history reads like a shift report.

What Orb does not do

Tunc Orb stores the hand-off; it does not wake an agent up or send it a message. The next agent reads the task when it starts or when you ask it to ("Check Tunc Orb for open hand-offs"). In Tunc Hub, a BOT on a schedule can make that check for you.