handoff

Preserve Claude session context across fresh instances via CLI handoff.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/cwolfe007/simple-gt --skill handoff-cwolfe007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/cwolfe007/simple-gt/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/cwolfe007/simple-gt --skill handoff-cwolfe007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handoff Claude sessions to preserve work context when you cycle to a fresh instance.

Core Features & Use Cases

  • Collects current session state, inbox/beads/status
  • Sends handoff context to a new Claude session and auto-primes via SessionStart
  • Preserves subject matter, hook, and repository state across restarts

Quick Start

Run gt handoff to hand off your current session to a fresh Claude instance.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve Claude session context when switching to a fresh instance?

To preserve Claude session context when switching instances, use a CLI session-management workflow that collects current state, beads, and git status, then transfers them to a new instance via mail and auto-primes it through hooks. Run gt handoff with explicit -c or -m options to safely execute the context transfer.

What is context-switching for Claude sessions and when do I need it?

Context-switching for Claude sessions is the process of transferring working state and subject matter to a fresh instance to avoid losing progress. You need it when cycling to a new Claude instance during continuous work, ensuring hooks and repository state persist across restarts.

How to hand off a Claude session using the command line?

To hand off a Claude session using the command line, run gt handoff with explicit -c or -m options. This command coordinates state collection from your current session, sends the context to a new Claude session, and auto-primes it via SessionStart hooks for continuous work.

Does handoff require any specific hooks or dependencies to work?

Handoff requires a CLI workflow environment and maintains hook, beads, and git state across sessions. It enforces safe usage by requiring explicit -c or -m options, but lists no external package dependencies, relying on internal hooks and mail for state persistence and session respawn.

Why does my Claude session context disappear when I restart?

Claude session context disappears on restart because the fresh instance lacks your previous working state. Without a state-persistence mechanism to collect and transfer inbox, beads, and repository state, the new session starts blank, breaking continuous work across context-switching boundaries.

What are the limitations of using CLI hooks for Claude state persistence?

Limitations of using CLI hooks for Claude state persistence include the requirement to use explicit -c or -m options for safe usage, dependence on a specific CLI workflow (gt handoff), and the need to properly coordinate SessionStart auto-priming to ensure hooks and git state transfer correctly.