@pi-unipi/btw 2.0.1 → 2.0.2

package/README.md

@@ -1,6 +1,6 @@
 # @pi-unipi/btw
 
-Side conversations that run in parallel. Ask a question using `/btw` while the main agent keeps working — the answer streams into a modal overlay without interrupting the current task.
+Side conversations that run in parallel. Ask a question using `/unipi:btw` while the main agent keeps working — the answer streams into a modal overlay without interrupting the current task.
 
 BTW opens a real Pi sub-session with coding-tool access. Use it to clarify something, explore an idea, or think through next steps without derailing the main turn. When you're ready, inject the thread back or summarize it.
 
@@ -10,12 +10,12 @@ Based on [pi-btw](https://github.com/Neuron-Mr-White/pi-btw) by Dan Bachelder.
 
 | Command | Description |
 |---------|-------------|
-| `/btw [--save] <question>` | Ask a question in a side thread |
-| `/btw:new [question]` | Start a fresh thread with main-session context |
-| `/btw:tangent [--save] <question>` | Contextless tangent thread |
-| `/btw:clear` | Dismiss modal and clear thread |
-| `/btw:inject [instructions]` | Send full thread to main agent |
-| `/btw:summarize [instructions]` | Summarize thread and inject into main agent |
+| `/unipi:btw [--save] <question>` | Ask a question in a side thread |
+| `/unipi:btw-new [question]` | Start a fresh thread with main-session context |
+| `/unipi:btw-tangent [--save] <question>` | Contextless tangent thread |
+| `/unipi:btw-clear` | Dismiss modal and clear thread |
+| `/unipi:btw-inject [instructions]` | Send full thread to main agent |
+| `/unipi:btw-summarize [instructions]` | Summarize thread and inject into main agent |
 
 ### Keyboard Shortcuts
 
@@ -29,13 +29,13 @@ Based on [pi-btw](https://github.com/Neuron-Mr-White/pi-btw) by Dan Bachelder.
 ### Examples
 
 ```text
-/btw what file defines this route?
-/btw how would you refactor this parser?
-/btw --save summarize the last error in one sentence
-/btw:new let's start a fresh thread about auth
-/btw:tangent brainstorm from first principles without using the current chat context
-/btw:inject implement the plan we just discussed
-/btw:summarize turn that side thread into a short handoff
+/unipi:btw what file defines this route?
+/unipi:btw how would you refactor this parser?
+/unipi:btw --save summarize the last error in one sentence
+/unipi:btw-new let's start a fresh thread about auth
+/unipi:btw-tangent brainstorm from first principles without using the current chat context
+/unipi:btw-inject implement the plan we just discussed
+/unipi:btw-summarize turn that side thread into a short handoff
 ```
 
 ## Special Triggers
@@ -46,14 +46,14 @@ The BTW overlay opens top-centered so the main session remains visible underneat
 
 ## How It Works
 
-1. `/btw` creates or reuses a BTW sub-session
+1. `/unipi:btw` creates or reuses a BTW sub-session
 2. Your question runs in a real Pi session with tool access
 3. The answer streams into the BTW modal overlay
 4. The thread continues until you clear it or inject it back
 
-`/btw:inject` sends the full thread to the main agent as a user message. If Pi is busy, it queues as a follow-up. `/btw:summarize` does the same but summarizes first.
+`/unipi:btw-inject` sends the full thread to the main agent as a user message. If Pi is busy, it queues as a follow-up. `/unipi:btw-summarize` does the same but summarizes first.
 
-`/btw:tangent` starts a separate thread that doesn't inherit the main session's conversation context. Use it for unrelated exploration.
+`/unipi:btw-tangent` starts a separate thread that doesn't inherit the main session's conversation context. Use it for unrelated exploration.
 
 The `--save` flag saves that single exchange as a visible session note.
 

package/extensions/btw.ts

@@ -1,19 +1,19 @@
 /**
  * @pi-unipi/btw — Side Conversation Extension
  *
- * A /btw side conversation channel that opens a real pi sub-session
+ * A /unipi:btw side conversation channel that opens a real pi sub-session
  * with coding-tool access, running immediately even while the main
  * agent is still busy.
  *
  * Based on pi-btw by Dan Bachelder, adapted for the Unipi suite.
  *
  * Commands:
- *   /btw [--save] <question>   - Side conversation (contextual)
- *   /btw:tangent [--save] <q>  - Contextless tangent thread
- *   /btw:new [question]        - Fresh thread with main-session context
- *   /btw:clear                 - Dismiss and clear thread
- *   /btw:inject [instructions] - Send full thread to main agent
- *   /btw:summarize [instr]     - Summarize and inject into main agent
+ *   /unipi:btw [--save] <question>       - Side conversation (contextual)
+ *   /unipi:btw-tangent [--save] <q>      - Contextless tangent thread
+ *   /unipi:btw-new [question]            - Fresh thread with main-session context
+ *   /unipi:btw-clear                     - Dismiss and clear thread
+ *   /unipi:btw-inject [instructions]     - Send full thread to main agent
+ *   /unipi:btw-summarize [instructions]  - Summarize and inject into main agent
  */
 
 import {
@@ -44,6 +44,7 @@ import {
   type OverlayHandle,
   type TUI,
 } from "@mariozechner/pi-tui";
+import { BTW_COMMANDS, UNIPI_PREFIX } from "@pi-unipi/core";
 
 // ─── Constants ──────────────────────────────────────────────────────────────
 
@@ -1615,15 +1616,23 @@ export default function (pi: ExtensionAPI) {
 
   function parseOverlayBtwCommand(value: string): { name: string; args: string } | null {
     const trimmed = value.trim();
-    const match = trimmed.match(/^\/(btw:(?:new|tangent|clear|inject|summarize))(?:\s+(.*))?$/);
-    if (!match) {
-      return null;
+    const legacy = trimmed.match(/^\/(btw:(?:new|tangent|clear|inject|summarize))(?:\s+(.*))?$/);
+    if (legacy) {
+      return {
+        name: legacy[1],
+        args: legacy[2]?.trim() ?? "",
+      };
     }
 
-    return {
-      name: match[1],
-      args: match[2]?.trim() ?? "",
-    };
+    const unipi = trimmed.match(/^\/unipi:btw-(new|tangent|clear|inject|summarize)(?:\s+(.*))?$/);
+    if (unipi) {
+      return {
+        name: `btw:${unipi[1]}`,
+        args: unipi[2]?.trim() ?? "",
+      };
+    }
+
+    return null;
   }
 
   async function submitFromOverlay(ctx: ExtensionCommandContext | ExtensionContext, value: string): Promise<void> {
@@ -1928,42 +1937,42 @@ export default function (pi: ExtensionAPI) {
     });
   }
 
-  pi.registerCommand("btw", {
+  pi.registerCommand(`${UNIPI_PREFIX}${BTW_COMMANDS.BTW}`, {
     description: "Continue a side conversation in a focused BTW modal. Add --save to also persist a visible note.",
     handler: async (args, ctx) => {
       await dispatchBtwCommand("btw", args, ctx);
     },
   });
 
-  pi.registerCommand("btw:tangent", {
+  pi.registerCommand(`${UNIPI_PREFIX}${BTW_COMMANDS.TANGENT}`, {
     description: "Start or continue a contextless BTW tangent in the focused BTW modal.",
     handler: async (args, ctx) => {
       await dispatchBtwCommand("btw:tangent", args, ctx);
     },
   });
 
-  pi.registerCommand("btw:new", {
+  pi.registerCommand(`${UNIPI_PREFIX}${BTW_COMMANDS.NEW}`, {
     description: "Start a fresh BTW thread with main-session context. Optionally ask the first question immediately.",
     handler: async (args, ctx) => {
       await dispatchBtwCommand("btw:new", args, ctx);
     },
   });
 
-  pi.registerCommand("btw:clear", {
+  pi.registerCommand(`${UNIPI_PREFIX}${BTW_COMMANDS.CLEAR}`, {
     description: "Dismiss the BTW modal/widget and clear the current thread.",
     handler: async (args, ctx) => {
       await dispatchBtwCommand("btw:clear", args, ctx);
     },
   });
 
-  pi.registerCommand("btw:inject", {
+  pi.registerCommand(`${UNIPI_PREFIX}${BTW_COMMANDS.INJECT}`, {
     description: "Inject the full BTW thread into the main agent as a user message.",
     handler: async (args, ctx) => {
       await dispatchBtwCommand("btw:inject", args, ctx);
     },
   });
 
-  pi.registerCommand("btw:summarize", {
+  pi.registerCommand(`${UNIPI_PREFIX}${BTW_COMMANDS.SUMMARIZE}`, {
     description: "Summarize the BTW thread, then inject the summary into the main agent.",
     handler: async (args, ctx) => {
       await dispatchBtwCommand("btw:summarize", args, ctx);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@pi-unipi/btw",
-  "version": "2.0.1",
-  "description": "A pi extension for parallel side conversations with /btw — part of the Unipi suite",
+  "version": "2.0.2",
+  "description": "A pi extension for parallel side conversations with /unipi:btw — part of the Unipi suite",
   "type": "module",
   "license": "MIT",
   "author": "Neuron Mr White",

package/skills/btw/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: btw
-description: Helps you use the /btw side-conversation workflow effectively. Use when you want to think in parallel, ask side questions without interrupting ongoing work, or inject a side thread back into the main agent.
+description: Helps you use the /unipi:btw side-conversation workflow effectively. Use when you want to think in parallel, ask side questions without interrupting ongoing work, or inject a side thread back into the main agent.
 ---
 
 # BTW
@@ -21,14 +21,14 @@ Prefer the BTW workflow when the user wants to:
 Use these commands in your guidance to the user:
 
 ```text
-/btw <question>
-/btw --save <question>
-/btw:new [question]
-/btw:tangent <question>
-/btw:tangent --save <question>
-/btw:clear
-/btw:inject [instructions]
-/btw:summarize [instructions]
+/unipi:btw <question>
+/unipi:btw --save <question>
+/unipi:btw-new [question]
+/unipi:btw-tangent <question>
+/unipi:btw-tangent --save <question>
+/unipi:btw-clear
+/unipi:btw-inject [instructions]
+/unipi:btw-summarize [instructions]
 ```
 
 ## How to guide the user
@@ -38,7 +38,7 @@ Use these commands in your guidance to the user:
 Recommend:
 
 ```text
-/btw <question>
+/unipi:btw <question>
 ```
 
 Use this when the user wants an immediate aside and does not need a visible saved note.
@@ -48,7 +48,7 @@ Use this when the user wants an immediate aside and does not need a visible save
 Recommend:
 
 ```text
-/btw --save <question>
+/unipi:btw --save <question>
 ```
 
 Use this when the user wants the exchange to appear as a visible BTW note in the session transcript.
@@ -58,13 +58,13 @@ Use this when the user wants the exchange to appear as a visible BTW note in the
 Recommend:
 
 ```text
-/btw:new
+/unipi:btw-new
 ```
 
 or
 
 ```text
-/btw:new <question>
+/unipi:btw-new <question>
 ```
 
 Use this when the previous BTW discussion is no longer relevant, but you still want the new side thread to inherit the current main-session context.
@@ -74,13 +74,13 @@ Use this when the previous BTW discussion is no longer relevant, but you still w
 Recommend:
 
 ```text
-/btw:tangent <question>
+/unipi:btw-tangent <question>
 ```
 
 or
 
 ```text
-/btw:tangent --save <question>
+/unipi:btw-tangent --save <question>
 ```
 
 Use this when the user wants a side conversation that does not include the current main-session context.
@@ -90,7 +90,7 @@ Use this when the user wants a side conversation that does not include the curre
 Recommend:
 
 ```text
-/btw:inject <instructions>
+/unipi:btw-inject <instructions>
 ```
 
 Use this when the exact discussion matters and the user wants the main agent to act on it.
@@ -100,19 +100,19 @@ Use this when the exact discussion matters and the user wants the main agent to
 Recommend:
 
 ```text
-/btw:summarize <instructions>
+/unipi:btw-summarize <instructions>
 ```
 
 Use this when the thread is long and only the distilled outcome should go back into the main agent.
 
 ## Recommendation rules
 
-- Prefer `/btw` over normal chat when the user explicitly wants a side conversation.
-- Prefer `/btw:tangent` when the user wants that side conversation to be contextless.
-- Prefer `/btw:summarize` over `/btw:inject` for long exploratory threads.
-- Prefer `/btw:inject` when precise wording, detailed tradeoffs, or a full plan matters.
-- Suggest `/btw:new` before starting a totally unrelated side topic when main-session context is still useful.
-- Suggest `/btw:clear` when the widget/thread should be dismissed.
+- Prefer `/unipi:btw` over normal chat when the user explicitly wants a side conversation.
+- Prefer `/unipi:btw-tangent` when the user wants that side conversation to be contextless.
+- Prefer `/unipi:btw-summarize` over `/unipi:btw-inject` for long exploratory threads.
+- Prefer `/unipi:btw-inject` when precise wording, detailed tradeoffs, or a full plan matters.
+- Suggest `/unipi:btw-new` before starting a totally unrelated side topic when main-session context is still useful.
+- Suggest `/unipi:btw-clear` when the widget/thread should be dismissed.
 
 ## Response style
 
@@ -127,23 +127,23 @@ When helping the user use BTW:
 ### Example: brainstorm while coding continues
 
 ```text
-/btw what are the risks of switching this to optimistic updates?
+/unipi:btw what are the risks of switching this to optimistic updates?
 ```
 
 ### Example: create a clean new thread
 
 ```text
-/btw:new sketch a safer migration plan
+/unipi:btw-new sketch a safer migration plan
 ```
 
 ### Example: start a contextless tangent
 
 ```text
-/btw:tangent think through this from first principles without using the current chat context
+/unipi:btw-tangent think through this from first principles without using the current chat context
 ```
 
 ### Example: send the result back
 
 ```text
-/btw:summarize implement the recommended migration plan
+/unipi:btw-summarize implement the recommended migration plan
 ```