/fork

Branches the current chat into a new session, the original stays untouched.

/fork branches the current conversation into a copy and lets you pursue a different path in it. Aliases per the changelog: /branch, /duplicate.

✅ WHEN TO USE IT?

Try two different solution approaches in parallel

/fork — then test an alternative implementation path in the new chat

Hedge a risky attempt without endangering the main session

/fork — branch off before an experimental refactor

⛔ WHEN NOT TO?

The existing path should just continue

A fork creates an extra session you then have to manage, even though only linear continuation is needed.

Better: Keep writing normally in the current chat

Old failed attempts should disappear entirely

/fork keeps the original around, it doesn't clean anything up.

Better: Use /rewind to jump back to an earlier state

SOURCES