handover

Transfer in-flight work between Claude sessions or alternative runtimes.

1|Updated Mar 5, 2026

Search Tags:#Claude #session management #context switching #work transfer #runtime interoperability

Ready to run

npx skills add https://github.com/souliane/teatree --skill handover-souliane

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/souliane/teatree/tree/main/skills/handover
Command: npx skills add https://github.com/souliane/teatree --skill handover-souliane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables users to handover all current work from one Claude session to another or to a different runtime, ensuring that no work is lost during transitions.

Core Features & Use Cases

Session to Session Hand-off: Transfer in-flight work to another Claude session with a single command.
Claude to Other Runtime: Switch away from Claude without losing the thread, supported by usage telemetry.
Session Recovery: Automatically claim unclaimed hand-offs on session start, recover from network changes, and account switches.

Quick Start

To handover your current session's work to another session, run:

t3 <overlay> handover create --to <id>

Frequently Asked Questions about handover

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

FAQPage Schema

How do I transfer in-flight work between Claude sessions?▼

To transfer in-flight work between Claude sessions, use the handover command to create a transfer record targeting a specific session identifier. This ensures continuity of your current work across different environments without losing the thread.

Can I switch from Claude to another runtime without losing context?▼

Yes, you can switch from Claude to an alternative runtime without losing context by creating a runtime-agnostic handover. This captures your current work state and allows the target runtime to claim the unclaimed hand-off upon startup.

How does session recovery work after a network change or account switch?▼

Session recovery automatically claims unclaimed hand-offs when a new session starts, restoring your previous work state. This mechanism accounts for network changes and account switches to ensure no work is lost during unexpected interruptions.

What do I need to set up before creating a session hand-off?▼

You need the target session identifier to create a session hand-off. The command requires specifying the recipient ID so the transfer can be accurately routed and claimed by the intended Claude session or alternative runtime.

Are there limitations when transferring work to alternative runtimes?▼

Work transfers to alternative runtimes rely on runtime-agnostic handovers and may be constrained by the target environment's ability to claim unclaimed hand-offs. Supported by usage telemetry, the transfer ensures continuity but depends on successful claim upon session start.