Handoff to Claude Code
SkillProductivityContinue a task in Claude Code through a portable Director handoff packet. Use when work started in Codex CLI or Grok Build should move to Claude, or when a fresh Claude session needs the current decisions and verification evidence.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Handoff to Claude Code skill
What this skill tells your AI
The instructions your AI receives, as published by claude-world/director-mode-lite in skills/handoff-claude/SKILL.md and read by ahel’s review.
Use the shared session-relay workflow. Claude starts a new native session and
reads the same vendor-neutral packet used by Codex and Grok.
ROOT="${CLAUDE_PROJECT_DIR:-${GROK_WORKSPACE_ROOT:-}}"
[[ -n "$ROOT" ]] || ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
RELAY="$ROOT/.director-mode/bin/director-relay"
[[ -x "$RELAY" ]] || RELAY="$HOME/.claude/bin/director-relay"
"$RELAY" create \
--from <codex|grok> --to claude \
--goal "..." --summary "..." --next "..."
"$RELAY" continue --to claude
The second command only prints the interactive command. Add --run when the
user explicitly wants to launch it, or --headless for a one-shot claude -p
continuation.
Claude Code's own --continue and --resume remain the right tools for
resuming a Claude-native history. Use a Director packet when the source is
another CLI, when a concise checkpoint is preferable, or when the workflow may
later move again.
Profiles created with CLAUDE_CONFIG_DIR can still isolate authorized Claude
accounts, but profile credentials, permissions, plugins, MCP configuration, and
session histories are not copied into the packet.
Signals
- GitHub stars
- 81
- Forks
- 11
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
handoff-claude- Source
- github.com/claude-world/director-mode-lite