register

Register a Claude Code session with a friendly name in the local registry.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jdidion/claude-plugins --skill register-jdidion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: register
Source: https://github.com/jdidion/claude-plugins/tree/main/plugins/handoff/skills/register
Command: npx skills add https://github.com/jdidion/claude-plugins --skill register-jdidion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables other CLAUDE Code sessions to discover and reach this session for handoffs by registering a friendly name and session identifiers.

Core Features & Use Cases

  • Registers the current Claude Code session with a discoverable name
  • Creates a registry entry and inbox for incoming handoffs
  • Supports auto-registration via a SessionStart hook for seamless collaboration

Quick Start

Register this session for handoff discovery by running the registration command with an optional friendly name.

Frequently Asked Questions about register

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

FAQPage Schema
How do I register a Claude Code session for cross-session collaboration?▼

To register a session for cross-session collaboration, you assign it a friendly name and record it in the local registry at ~/.claude/handoffs/registry.json, which creates an inbox for incoming handoffs and enables discovery by other sessions.

What is a handoff registry and how does it work for CLI workflows?▼

A handoff registry is a local JSON file that records active Claude Code sessions with friendly names and identifiers. It enables routing handoffs and coordinating cross-session collaboration by allowing sessions to discover and reach each other.

Can I auto-register sessions for handoff discovery using a hook?▼

Yes, you can auto-register sessions for handoff discovery by configuring a SessionStart hook. This approach automatically registers the current Claude Code session and creates an inbox for incoming handoffs without manual execution.

Do I need any dependencies to set up session handoffs and routing?▼

No dependencies are required to set up session handoffs and routing. The registration process only uses a local registry file located at ~/.claude/handoffs/registry.json to store session names and manage incoming handoff inboxes.

What's the best way to coordinate multiple CLI sessions for a single project?▼

The best way to coordinate multiple CLI sessions is registering each session with a discoverable friendly name. This creates a local registry entry and inbox, enabling seamless cross-session collaboration and handoff routing between active instances.

Why are my Claude Code sessions unable to discover each other for handoffs?▼

Sessions cannot discover each other for handoffs if they are not registered in the local registry. You must register each session with a friendly name to populate ~/.claude/handoffs/registry.json and create the necessary inbox for routing.