pi-side-chat

To explore alternatives without context switching, you can fork a side chat thread from the current context. This preserves your main conversation by creating a separate scratchpad to test hypotheses and gather clarifications in parallel.

Parallel reasoning uses a side chat scratchpad to investigate new ideas alongside an active task. It works by branching a separate thread from your current context, allowing you to gather clarifications and explore options without derailing the main thread.

To start a side chat for parallel exploration, run the /side command. This initiates a separate scratchpad thread where you can explore alternative directions while keeping your primary conversation focused and stable.

Yes, you need to keep model invocation disabled when using the side-chat workflow command. This prevents unintended execution and ensures your parallel scratchpad work does not disrupt the primary conversation context.

To bring findings back to your main task, use the side chat thread for decision support by collecting details and exploring alternatives. Once you identify the best findings, manually integrate them into your primary conversation to continue the active task.

Yes, you can use a side chat thread to gather clarifications during an active task. The forked thread acts as a parallel scratchpad, allowing you to resolve questions and test approaches without interrupting the main conversation flow.