/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.
/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.
/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.
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.