How do I install the Agterm Fork skill?

Run npx skillmds@latest add isachivka/agterm-fork in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agterm Fork safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agterm Fork?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agterm Fork free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agterm Fork?

isachivka (@isachivka) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agterm Fork by isachivka — Agent Skill

Name: Agterm Fork
Author: isachivka

Agterm Fork

Fork the agent running in an agterm pane (Claude Code or Codex) into a sibling session: same workspace, same launch flags, full conversation history under a fresh session id, waiting at its prompt. The source session is untouched. Also wires a "Fork session" entry into agterm's custom-command palette.

isachivka 763f8ab 2 files · 14.9 KB Updated Sep 17, 2026

File contents

agterm-fork

Only inside agterm, and only with the agterm-backup capture hook — that hook's live record is where a session's own claude id comes from.

agterm-fork                      # fork the current pane
agterm-fork <pane-id> [left|right]   # fork any pane (what the palette entry calls)
agterm-fork --dry-run            # print the plan, create nothing
agterm-fork install              # wire the "Fork session" custom command
agterm-fork uninstall            # remove it

The plugin's bin/ is on PATH inside a Claude Code session, so run it by name. What fork does:

Reads the pane out of agtermctl tree, refuses if no claude or codex runs there.
Session id: the agterm-backup live record, falling back to a --resume already in the pane's argv. Never guessed — no id, no fork.
Launch flags (--dangerously-skip-permissions, --model, …) are inherited from the parent's argv, minus --resume/--continue/--fork-session.
agtermctl session new --after <pane> — the anchor carries the workspace, so the fork lands next to its parent — then types claude --resume <id> --fork-session <flags> or, for codex, codex fork <id> <flags> (codex forks natively).
Waits for claude's "resume full session as-is / from summary" question and answers 2, so the fork really carries the whole history (--no-answer to skip).
Stops there. The fork gets no task; the user opens it and drives it.

install writes ~/.local/bin/agterm-fork and a managed block in ~/.config/agterm/keymap.conf:

command "Fork session" cmd+ctrl+a>f $HOME/.local/bin/agterm-fork "$AGT_SESSION_ID" "$AGT_PANE"

so cmd+ctrl+a>f, or Ctrl-Shift-O → "Fork session", forks whatever session the cursor is on, no Claude involved. The wrapper resolves the newest installed copy of the skill at call time, because the plugin cache path carries a commit sha and would otherwise break on every update.

Focus stays where it was (--no-select). The fork gets its own live record, so agterm-backup covers it like any other session.

---name: agterm-forkdescription: Fork the agent running in an agterm pane (Claude Code or Codex) into a sibling session: same workspace, same launch flags, full conversation history under a fresh session id, waiting at its prompt. The source session is untouched. Also wires a "Fork session" entry into agterm's custom-command palette.---# agterm-forkOnly inside agterm, and only with the `agterm-backup` capture hook — that hook's liverecord is where a session's own claude id comes from.```bashagterm-fork # fork the current paneagterm-fork <pane-id> [left|right] # fork any pane (what the palette entry calls)agterm-fork --dry-run # print the plan, create nothingagterm-fork install # wire the "Fork session" custom commandagterm-fork uninstall # remove it```The plugin's `bin/` is on `PATH` inside a Claude Code session, so run it by name. What `fork` does:1. Reads the pane out of `agtermctl tree`, refuses if no claude or codex runs there.2. Session id: the `agterm-backup` live record, falling back to a `--resume` already in the pane's argv. Never guessed — no id, no fork.3. Launch flags (`--dangerously-skip-permissions`, `--model`, …) are inherited from the parent's argv, minus `--resume`/`--continue`/`--fork-session`.4. `agtermctl session new --after <pane>` — the anchor carries the workspace, so the fork lands next to its parent — then types `claude --resume <id> --fork-session <flags>` or, for codex, `codex fork <id> <flags>` (codex forks natively).5. Waits for claude's "resume full session as-is / from summary" question and answers **2**, so the fork really carries the whole history (`--no-answer` to skip).6. Stops there. **The fork gets no task**; the user opens it and drives it.`install` writes `~/.local/bin/agterm-fork` and a managed block in`~/.config/agterm/keymap.conf`:```command "Fork session" cmd+ctrl+a>f $HOME/.local/bin/agterm-fork "$AGT_SESSION_ID" "$AGT_PANE"```so `cmd+ctrl+a>f`, or `Ctrl-Shift-O` → "Fork session", forks whatever session the cursor ison, no Claudeinvolved. The wrapper resolves the newest installed copy of the skill at call time, becausethe plugin cache path carries a commit sha and would otherwise break on every update.Focus stays where it was (`--no-select`). The fork gets its own live record, so`agterm-backup` covers it like any other session.

Frequently asked questions