paseo-handoff

Name: paseo-handoff
Availability: InStock
Author: getpaseo

Transfers tasks between agents, preserving metadata via Rocket.Chat's API.

12.9k|1.3k|Updated Oct 13, 2025

Search Tags:#workflow #cli #codex #claude #handoff #paseo #agent-transfer

Ready to run

npx skills add https://github.com/getpaseo/paseo --skill paseo-handoff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: paseo-handoff
Source: https://github.com/getpaseo/paseo/tree/main/skills/paseo-handoff
Command: npx skills add https://github.com/getpaseo/paseo --skill paseo-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transfers an active task to a new agent along with full context to ensure continuity when collaborating across Codex or Claude.

Core Features & Use Cases

Generates a self-contained handoff prompt that preserves task description, decisions, and constraints.
Supports provider selection (Codex or Claude) and optional worktree execution for isolated contexts.
Launches the receiving agent via the Paseo CLI and returns an actionable Agent ID with follow-up commands.
Documents current state, what was tried, and decisions to maintain intent and satisfy acceptance criteria.
Includes explicit guidance and constraints to prevent drift or unsafe actions.

Quick Start

Initiate a handoff by running the Paseo CLI with your chosen provider and include the current task context.

Frequently Asked Questions about paseo-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I transfer an active task to another agent without losing context?▼

To transfer an active task, you generate a self-contained handoff prompt that preserves the task description, decisions, and constraints, then use the Paseo CLI to launch the receiving agent with the full context.

What is an agent handoff and when do I need it?▼

An agent handoff transfers an active task to a new agent along with full context to ensure continuity when collaborating across Codex or Claude. It is needed when switching providers mid-task to prevent intent drift.

How do I switch from Codex to Claude during a workflow?▼

To switch from Codex to Claude, you use the Paseo CLI to select the Claude provider. The handoff process documents the current state and decisions, generating a prompt that the new Claude agent can execute reliably.

Can I use an isolated worktree when handing off tasks between agents?▼

Yes, the Paseo CLI supports optional worktree execution for isolated contexts during cross-agent handoffs. This allows you to maintain separate environments for the Codex or Claude agents while transferring the task.

What context does the Paseo CLI pass to the receiving agent?▼

The Paseo CLI passes a self-contained handoff prompt that enumerates the current state, what was tried, decisions, acceptance criteria, and constraints to maintain intent and ensure reliable handoff execution.

How do I track a task after handing it off to a new agent?▼

After handing off a task, the Paseo CLI returns an actionable Agent ID along with follow-up commands. You use this ID to track the receiving agent's progress on the transferred context.