← ClaudeAtlas

session-transferlisted

Handle an agent session ID or a request to continue work in another agent. Classify same-platform resume versus cross-platform handoff before attempting any session command.
ShlomiPorush/agent-skills · ★ 2 · AI & Automation · score 68
Install: claude install-skill ShlomiPorush/agent-skills
# Session transfer Use this skill when a user supplies a session ID (often a UUID such as `de31dd36-06a4-4ae8-8fb4-2f32b1a582dd`), asks to move work to another agent, or asks for a second opinion on an existing session. ## First response: classify, do not guess Treat a session ID as an opaque, platform-scoped pointer. Do not spend a turn trying to decode it, searching arbitrary files, or running a resume command before identifying the source platform and surface. ### T3 Code IDs are a separate case When the ID was copied from a T3 Code UI context menu, do not assume it is the Codex rollout ID. T3 may expose its own wrapper, conversation, or UI identifier. The Codex-native ID is the `session_id`/`id` in the first `session_meta` record of the matching Codex JSONL rollout, and normally also appears in the `rollout-...-<id>.jsonl` filename. Do not infer a mapping between the two UUIDs. Use T3's own reopen/share flow for a T3 ID, or obtain the Codex-native ID from the platform's session UI or authorized local session metadata. Do not rely on undocumented T3 LevelDB/cache files as a resolver. A raw occurrence of the T3 UUID there can be UI state, a project index, or cached content and does not establish a relation to a Codex rollout. Never match IDs by timestamp, filename proximity, or text similarity. T3 desktop/server installations may persist an explicit provider cursor in `~/.t3/userdata/state.sqlite`. This resolver is T3-only; never run it for a bare Claude or Codex ID.