herdr-session-fork

Fork the current Pi session into a new Herdr tab with copied session history.

Updated May 18, 2026
One-click install
npx skills add https://github.com/blalor/pi-dot-dev --skill herdr-session-fork-blalor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: herdr-session-fork
Source: https://github.com/blalor/pi-dot-dev/tree/main/agent/skills/herdr-session-fork
Command: npx skills add https://github.com/blalor/pi-dot-dev --skill herdr-session-fork-blalor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Duplicating a running Pi conversation into a separate Herdr tab normally requires manually locating the workspace, checkout path, and session file, then wiring up a new tab and agent by hand. This Skill automates that discovery and startup so a forked session can continue independently from the copied transcript. ## Core Features & Use Cases - Automatic context discovery: Reads the current Herdr pane to extract the workspace, checkout path, and active Pi session file, with environment-variable fallbacks. - Safe fork startup: Creates a new tab, starts Pi with --fork, retries transient agent_pane_busy errors with bounded backoff, and verifies agent readiness before reporting. - Independent-session boundary: Disables the fork's intercom tool by default and preserves created tabs on failure with a printed recovery command. - Use Case: While debugging in a Pi session, fork the conversation into a second Herdr tab to explore an alternative fix without losing the original session's state. ## Quick Start Ask the agent to fork the current Pi session into a new Herdr tab, optionally providing a label for the fork.

Frequently Asked Questions about herdr-session-fork

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

FAQPage Schema
How do I fork a Pi session into a new Herdr tab?▼

Run the bundled fork-current-herdr-session.sh script with an optional label. It discovers the current pane's workspace, checkout, and session file, creates a tab, and starts Pi with the --fork flag automatically.

Does a forked Pi session share files with the original session?▼

Yes, the fork starts in the same checkout, so both sessions can see and modify the same files. For isolated edits, use a separate Worktrunk worktree or agree on a single-writer arrangement.

What dependencies are required to fork a Herdr Pi session?▼

The helper requires the herdr, pi, and jq executables on the PATH, plus a Herdr-managed pane running Pi. It checks for all three commands before proceeding and exits with an error if any is missing.

Why does Pi startup fail with agent_pane_busy in Herdr?▼

The agent_pane_busy error occurs when the new tab's shell is not yet ready for input. The helper retries startup with bounded backoff delays up to eight attempts before reporting failure and preserving the tab.

Can the forked session communicate with the source session via intercom?▼

By default no; the helper starts the fork with --exclude-tools intercom to keep it independent. Pass --allow-intercom only when the user explicitly requests inter-session coordination.