skills.rest
MaxWolf-01
MaxWolf-01COMMUNITY
Explore all skills by this author →
Website𝕏@MaxWolf_01GitHub

fork

Spawns a subagent that inherits the full conversation transcript for context-heavy delegated tasks.

3|Updated Jan 10, 2026
Search Tags:#claude code#agent workflow#tmux#subagent#task delegation#context inheritance#session fork
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill fork-maxwolf-01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fork
Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/fork
Command: npx skills add https://github.com/MaxWolf-01/agents --skill fork-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delegating a context-heavy side task normally requires writing a detailed brief so the subagent understands the situation. This Skill eliminates that by forking the session: the new agent inherits the entire conversation transcript, so the shared mental model transfers for free. ## Core Features & Use Cases - Transcript Inheritance: The fork reprocesses the full parent transcript, so no briefing document is needed for context-heavy work. - Bounded Directives: Each fork receives one explicit bounded directive covering scope, allowed output paths, and safety constraints. - CLI Fallback: When the fork subagent type is unavailable, a documented tmux + claude CLI workflow forks the session with minted session IDs for resumability. - Use Case: Offload a noisy investigation or heavy artifact build from the main conversation, then collect the result from the fork's output path without polluting the primary context. ## Quick Start Ask the agent to fork this session to investigate the failing test suite and write its findings to a scratch file.

Frequently Asked Questions about fork

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

FAQPage Schema
How do I fork a Claude Code session to delegate a task?▼

Use the Agent tool with subagent_type "fork" and give it one bounded directive. The fork inherits the full conversation transcript, so no brief is needed. This requires CLAUDE_CODE_FORK_SUBAGENT=1 set in the settings env.

When should I fork a session instead of using a regular subagent?▼

Fork when the task needs the shared mental model from the current conversation, such as a heavy artifact build or noisy investigation. A task expressible in a few self-contained sentences should go to an ordinary subagent instead.

What if the fork subagent type is not available?▼

Fall back to the documented CLI workflow: mint a session ID with uuidgen, then launch claude -p --resume <parent-id> --fork-session --session-id <fork-id> inside a detached tmux session with CLAUDECODE unset.

Why does a forked session need --dangerously-skip-permissions?▼

Headless CLI runs cannot answer permission prompts and session grants do not carry over, so the flag is required. It is acceptable only because the fork's directive is explicitly bounded to a single task and named output paths.

What are the limitations of session forking?▼

The fork reprocesses the entire parent transcript, which is cheap in cached tokens but adds real latency that grows with context size. Forks are fire-and-forget, so results are collected from the log or output path after completion.

Related Skills

Explore More Software Engineering Skills→
wan-huiyanwan-huiyan
3

fan-out-cost-control

Controls parallel agent fan-out cost through model selection, bounded context, and nested consultation limits.

Community
Intermediate
tvishwanadhatvishwanadha

review-codex

Dispatch reviewer:self-review into a Codex thread for parallel review.

Community
Advanced
em-jonesem-jones
1

td-task-management

Track task lifecycles and persist context across AI agent sessions.

Community
Advanced
hadpadrahulhadpadrahul

gsd-fast

Execute small, self-contained coding tasks inline without subagents or planning.

Community
Basic