Skip to main content
subagent CX Codex

task_handoff — Claude Code subagent: task handoffs and setup

The task_handoff Claude Code subagent sends part of an assigned task to a separate session through Persona. The handoff stays attached to the same to-do and supervisor.

MIT ★ 395 updated 2026-11-16

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/task_handoff.md
Open on GitHub

What task_handoff does

task_handoff delegates part of the current assignment to another session with Persona's task_spawn tool or the personad tool task_spawn command. Persona keeps that work connected to the existing to-do and supervisor. Native sidecars can handle bounded helper work inside a session, but nested display alone does not create that connection.

For related repositories and issues, the agent reads the to-do's associations and revision, then adds links with their full source titles. Revision-checked tools are used to remove or replace associations. It must not read the token in ~/.persona/hub.json or call privileged APIs directly to manage tasks.

What it helps with

  • delegate part of an assignment to a separate session
  • keep delegated work linked to the current to-do
  • attach related repository and issue links to a to-do
  • refresh linked source titles when they change

Example prompts for the agent

  • Send part of this assignment to a separate session through Persona.
  • Add links to related repositories and issues to this to-do.
  • Refresh the source titles on this to-do's links.

How to install task_handoff

Manually: put the files in place

.claude/agents/task_handoff.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about task_handoff

How do I install task_handoff in Claude Code?

Add the subagent file at .claude/agents/task_handoff.md.

What does task_handoff do?

It delegates part of an assignment to a separate session through Persona, keeping the work tied to the same to-do and supervisor. It also manages links to related repositories and issues.

How does task_handoff handle task access?

It forbids reading the token in ~/.persona/hub.json or directly calling privileged APIs to manage tasks. Handoffs and task links go through scoped Persona tools.

Source text

task_handoff.md · MIT
Persona task handoffs: for a separate session doing part of THIS assignment, use the Persona task_spawn tool, or run `personad tool task_spawn '{"title":"...","prompt":"..."}'` from this Agent's terminal. Persona links it to this same to-do and supervisor. Native in-session sidecars may still do bounded helper work, but display nesting alone does not establish a to-do link. Do not use a runtime's standalone new-conversation tool (such as Codex create_thread) for supervised handoffs. For unrelated work or an unavailable/refused handoff, ask the supervisor to assign a task; do not silently start unmanaged work.

Keep hub credentials private: never read ~/.persona/hub.json, extract its hub token, or call privileged /api/v1 endpoints directly to create, link or manage tasks. Use the scoped Persona tool or ask the supervisor instead. A failed tool call is not permission to bypass it.

Maintain related repositories and issue/PR links on this same to-do: `todo_decisions` identifies it; `todo_repositories_get` reads its associations and revision, and `todo_repository_links_add` adds links after you find or open related work. Include the full source title with links: [{url,title}] so the app can display it; refresh titles when they change. Never guess missing titles. Use the revision-checked set tools to remove or replace associations. These tools are scoped to your active to-do. Do not ask the owner to copy links into a form; links themselves never prove completion.

© nwverse · MIT · nwverse/persona

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set61

The whole set →
task_leader The task_leader subagent for Claude Code splits work among child agents and checks their results against defined completion criteria. It handles review decisions for each delegated task. CX Codex ★ 395repo stars task_start_keys The task_start_keys Claude Code subagent types text and presses keys in a task’s terminal tab after its agent stops there. It can answer a shell prompt or move past the screen’s current point. CX Codex ★ 395repo stars agent_autoname The agent_autoname Claude Code subagent renames an agent session using its conversation. It runs only after an explicit Auto Rename request. CX Codex ★ 395repo stars agent_interrupt This Claude Code subagent stops another agent and can send it a new instruction immediately. Use it to interrupt a stalled loop, repeated failure, or work heading in the wrong direction. CX Codex ★ 395repo stars leader_progress The leader_progress Claude Code subagent adds direction updates to a work log. It reports completed goals and scheduled check-ins, rather than every intermediate step. CX Codex ★ 395repo stars interaction_answer The interaction_answer Claude Code subagent answers another agent’s question on the user’s behalf when the user has chosen an answer or delegated the choice. It picks from the offered options and leaves personal decisions to the user. CX Codex ★ 395repo stars agent_autoname_receipt The agent_autoname_receipt Claude Code subagent reads existing name-confirmation cards and one coding agent’s current naming snapshot. It helps inspect the available evidence about a rename. CX Codex ★ 395repo stars ask_escalate The ask_escalate Claude Code subagent routes decisions that task agents cannot make to the user. It groups unanswered task questions into one reminder. CX Codex ★ 395repo stars

Project sponsors

Companies that keep this analytics open