@narumitw/pi-btw 0.62.0 → 0.63.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -13,6 +13,7 @@ Only context you explicitly bring back is loaded into the main editor.
13
13
  - Uses Pi's message components, a native-style working editor border, and a compact footer below the editor.
14
14
  - Offers fullscreen, side-thread-left, and side-thread-right workspaces with Pi's live main-thread view, mouse or keyboard pane focus, and a draggable remembered divider.
15
15
  - Renders supported Mermaid fences as width-safe, themed Unicode diagrams without a browser or network request.
16
+ - Manually previews and imports new main-thread context without stopping main work or rewriting earlier side exchanges.
16
17
  - Keeps side questions and answers out of the main conversation by default.
17
18
  - Brings back the latest answer, a question suffix, an exact range, or the complete thread only when requested.
18
19
  - Uses Pi's current model and thinking level or saved pi-btw choices.
@@ -56,7 +57,9 @@ Both routes require TUI mode and a model with usable credentials; see [Settings]
56
57
  Side questions and selected conversation context are sent to that model's provider.
57
58
  Bringing context back fills the main editor without submitting; replacing an existing draft requires confirmation.
58
59
  Ctrl+C cancels the response and discards the current draft and queued questions, but completed exchanges remain resumable in memory.
59
- Read the [workflow guide](./docs/workflows.md) for context selection, copying, search, steering, and draft recovery; `/new`, `/resume`, `/reload`, and restart discard retained threads.
60
+ While composing, use **Import main updates** (`F9` by default) to preview and confirm new main context; no content is imported automatically.
61
+ Imports can increase context size and provider cost; see [import scope and branch limits](./docs/workflows.md#import-main-updates).
62
+ Read the [workflow guide](./docs/workflows.md) for context selection, importing, copying, search, steering, and draft recovery; `/new`, `/resume`, `/fork`, `/reload`, and restart discard retained threads.
60
63
 
61
64
  ## ⚙️ Settings
62
65
 
@@ -142,6 +145,7 @@ The literal `/btw settings` remains a side question, not a settings subcommand.
142
145
  | `cycleThinkingLevel` | Inherit Pi's `app.thinking.cycle` | Cycle supported levels while composing or generating. |
143
146
  | `bringToMain` | `ctrl+r` | Open the bring-to-main chooser after a completed answer. |
144
147
  | `switchPane` | First available `f6`, `f7`, or `f8` | Switch keyboard focus between panes in a split workspace. |
148
+ | `importMainUpdates` | First available `f9`, `f10`, or `f11` | Preview and confirm main updates while the side composer is idle. |
145
149
 
146
150
  For example, merge these overrides into `pi-btw.json`:
147
151
 
@@ -182,11 +186,12 @@ The file is read for every `/btw` invocation, so edits apply without `/reload`.
182
186
  ## 🚧 Limitations
183
187
 
184
188
  - `/btw` supports TUI mode only.
189
+ - The side model does not execute tools. Answers appear only after the response completes, not token by token.
185
190
  - Only the active pane receives keyboard input; hovering or scrolling over the other pane does not move focus.
186
191
  - Resume state is memory-only and lasts only for the current extension instance.
187
- - A side thread retains the latest 40,000 characters of main-conversation context and adds a truncation notice when earlier content is omitted.
192
+ - Main-conversation context is a limited text snapshot, not the complete session; see [context scope](./docs/workflows.md#choose-context-and-resume-threads).
188
193
  - Clipboard access depends on Pi's host helper, the operating system, and the terminal.
189
- - The live workspace still uses a BTW-owned terminal handoff and private host-layout access because Pi has no public workspace-composition API; see the [core-alignment handoff](./docs/core-alignment.md) for tested safeguards, exact limits, and proposed APIs.
194
+ - The live workspace uses a separate TUI instance and BTW-owned private host-layout access because Pi has no public workspace-composition API; see the [core-alignment handoff](./docs/core-alignment.md) for tested safeguards, exact limits, and proposed APIs. This intentionally deviates from Pi's advice against a second terminal renderer: only one renderer owns the terminal at a time, without an official support guarantee. The [shared fullscreen handoff record](https://github.com/narumiruna/pi-extensions/blob/main/packages/pi-tui-kit/docs/fullscreen-handoff.md) records the Kit physical-lifecycle contract, two-consumer proof, release guards, and physical-terminal limits; layouts, input, and domain state stay in BTW.
190
195
  - Pi does not expose all effective renderer options or a public clipboard-read callback. BTW uses native automatic wheel behavior but does not inherit private host wheel overrides or right-click clipboard paste.
191
196
  - Conversation appearance follows native defaults, not custom host editor/footer extensions or private padding settings. BTW uses one-cell message padding and zero-cell editor padding; see the [appearance reference and before/after frames](./docs/native-appearance.md).
192
197
  - Malformed, unsupported, or oversized Mermaid diagrams remain readable as fenced source; partial parses also show a warning.