Skip to content

Session Source Fork

Start a new managed agent seat from a prior Claude or Codex conversation, without claiming it resumed the original.

Stars
8,553
Licence
Apache-2.0
Files
1 file

What it does

This skill teaches an AI agent how to write OpenRig configuration that starts a new managed agent session by forking an existing native conversation (Claude or Codex). The new session gets its own fresh conversation token, and the original session's token is never attached to it. It also explains what not to do: it must not describe a fork as restoring or resuming the original agent, and it is not the right tool for restoring an existing seat or rebuilding context from artifacts.

Great for

  • Developers authoring OpenRig rig spec files that need a new member to branch from a prior Claude or Codex conversation
  • Teams using rig expand payloads to add members dynamically with traceable session origins
  • Anyone deciding between fork, rebuild, resume, and fresh launches for a new seat

Skip it if

  • Restoring or continuing an existing managed seat: this skill creates a new seat, and restore is the correct path for continuity (wrong tool, not risky).
  • Rebuilding understanding from artifacts or packets: the skill says to use rebuild mode instead, since collapsing the two is explicitly disallowed.
  • Terminal runtimes: the schema rejects session_source on terminal, so the skill does not apply there.

Try asking

  • “Write a rig spec member 'reviewer-2' that forks from an existing Claude native session id”
  • “Add a Codex member to a rig expand payload that starts from a prior thread via native_id”
  • “Explain why my fork seat shows a new session token instead of the parent's token”
  • “Review a rig spec to confirm session_source uses mode fork and ref.kind native_id”
Step-by-step guide: how to use Session Source ForkInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the Apache-2.0 licence and an attribution note.

    session-source-fork.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip session-source-fork.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip session-source-fork.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Use native_id as the only ref kind in v1; other kinds like artifact_path are rejected before launch.
  • Check the outcome and persisted identity after launch, since wording alone does not prove the intended continuity was created.
  • Pair with seat-continuity-and-handover when you need handover context on top of a fork.

What's inside

  • SKILL.md

Redistributed unmodified from mvschwarz/openrig under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.