@semanaut/zpi-btw
pi extension: /btw — ask a one-off side question answered by a separate model call, streamed into the live transcript and never written to the session. Minimal by design: no state, no branches, no config. Streaming and markdown rendering included; develop
Package details
Install @semanaut/zpi-btw from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@semanaut/zpi-btw- Package
@semanaut/zpi-btw- Version
1.1.0- Published
- Nov 4, 2026
- Downloads
- 1,068/mo · 241/wk
- Author
- semanaut
- License
- MIT
- Types
- extension
- Size
- 18.2 KB
- Dependencies
- 0 dependencies · 4 peers
Pi manifest JSON
{
"extensions": [
"./extensions/*.ts"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
@semanaut/zpi-btw
/btw — ask a one-off side question in pi.
The question inherits the full main-session context but is answered by a separate model call, so nothing enters the main conversation. The Q&A block streams into the live transcript and is never written to the session file or disk. The answer renders as markdown, with streaming display: deltas arrive in the block delta by delta.
The request is the session's own request — same system prompt, same tool declarations, same conversation, projected the way pi projects it for the model — so the model cannot tell a side question apart from a real turn. The one difference is that no tool ever runs: every tool call, whatever the tool, gets the same notice as its result and the model answers from what it already knows. Tool calls and thinking are not shown; only the answer text is.
Philosophy: minimal by design
/btw is deliberately bare-bones — a single command, a single question.
- No state — nothing to track, nothing to accumulate, no side-channel history.
- No branching — you are not managing a tree of parallel conversations.
- No configuration — no settings, no model overrides, no options to tune.
Just context plus one question: the answer appears below the current conversation and then it is gone. If you ever wanted a persistent or branching side conversation, you wanted a different tool.
Install
pi install npm:@semanaut/zpi-btwUsage
Type /btw <question> in pi. The answer appears in a transient block below the current conversation, with a working line under it while the side call runs; that line disappears once the answer lands, or reports interrupted / the failure text.