Skip to content
BENIBIX Learn

/fork vs /subtask

People think /fork and /subtask both send a helper off and wait for its answer, and they do not. /fork copies the chat into a new background session. You keep working, and the copy never reports back. /subtask hands one task to a helper that gets the whole chat. When it is done, its result comes back into the chat you are in.

AI⌨️ Claude Code

/fork Command

It copies this chat into a new session in the back.

/fork copies the chat into a new background session, and you keep working here. The copy starts with the whole chat so far. It also gets your model, permission mode and effort level. Pass a prompt and the copy starts on it at once. The copy is told to use its own worktree before it changes code, so the two do not edit the same files.

Example
Jack and Claude agree on two ways to speed up a page. He forks the chat to try the second way while he and Claude keep going with the first.
Why it matters
Two ideas get tried at the same time, both with the full chat behind them.
Full entry
AI⌨️ Claude Code

/subtask Command

It hands a task to a helper that reports back here.

/subtask hands a task to a forked subagent. The helper gets the whole conversation so far and works on the task in the background while you keep going. When it is done, its result comes back into this conversation. It is only there when agent view is on. When agent view is off, /fork starts this kind of helper instead.

Example
Lucy is fixing a form and wants tests for it too. She types /subtask write tests for the form, keeps working, and the tests' summary lands in her chat when they are done.
Why it matters
A side job runs at the same time, and you still get its answer in the chat that needs it.
Full entry

In one line

/fork Command
It copies this chat into a new session in the back.
/subtask Command
It hands a task to a helper that reports back here.