pi: fork vs clone sessions

♠ Problem statement: split a running Pi conversation / session into a second independent one whilst keeping the original. Pi has three similarly named albeit distinct operations: /fork /clone pi --fork <path|id> /fork opens a selector for an earlier user message, copies the active path up to the message’s parent into a new session, and puts the selected prompt back in the editor. This is for changing an earlier request. /clone copies the current active root-to-leaf path into a new session and switches the current Pi process to it. The old session file remains unchanged; retrieve it with /resume, or note its ID first and open it directly: /session /clone % pi --session 019feb2b The CLI spelling does something subtly different: % pi --help | grep -A5 -- '--session <path' --session <path|id> Use specific session file or partial UUID --session-id <id> Use exact project session ID, creating it if missing --fork <path|id> Fork specific session file or partial UUID into a new session…