handoff

Persist session state into beads memories for agent handoffs.

12|Updated Apr 28, 2020
One-click install
npx skills add https://github.com/gideonshaked/dotfiles --skill handoff-gideonshaked
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/gideonshaked/dotfiles/tree/main/agents/claude/skills/handoff
Command: npx skills add https://github.com/gideonshaked/dotfiles --skill handoff-gideonshaked

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persisting session context into beads so the next agent can continue without losing the thread.

Core Features & Use Cases

  • Deterministic handoff: captures relevant session state and stores it in durable memories accessible to subsequent agents.
  • Agent interoperability: works with Claude Code, Codex, and any bd-aware tool that can read beads memories.
  • Session wrap-up: produces a concise session_summary and tasks to guide next steps.

Quick Start

Instruct the system to hand off the current session state to the next agent via beads memories.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I persist agent session state for a seamless handoff?

To persist session state, the handoff workflow captures relevant context and stores it in durable beads memories, allowing the next agent to resume automatically without losing the thread.

What is the best way to hand off a coding session between Claude Code and Codex?

The handoff workflow enables agent interoperability by recording session context into beads memories, which can be read by any bd-aware tool including Claude Code and Codex.

How does storing session context in beads memories work?

Storing session context works by validating keys, deduplicating data by meaning, and recording memories, notes, and a session summary to guide the next agent's steps.

Do I need a specific tool to wrap up and hand off my session?

You need a bd-aware tool that can read beads memories. The deterministic handoff workflow is implemented via the handoff-bd script, requiring no additional dependencies.

Can I generate a session summary to guide next steps when wrapping up?

Yes, wrapping up a session produces a concise session_summary and a list of tasks that guide the next steps for the subsequent agent.

Why does my agent lose context when switching sessions?

Agents lose context when session state is not persisted. Using the handoff workflow stores your session state into beads memories, ensuring the next agent resumes automatically.