feat: add /btw side-question slash command - #933
Open
gsabatie wants to merge 1 commit into
Open
Conversation
One-shot LLM reply that reuses session context with no tools and without mutating conversation history. Interactive TUI only; -p and ACP return an interactive-only message.
|
💯 👌👌 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
/btw <question>, a one-shot side question you can ask between turns,using the current system prompt and session history as read-only context,
with no tools. Neither the question nor the answer is added to the main
conversation history — the next model turn sends the same history as before
/btw. Only available while the agent is idle (blocked while a turn isrunning); interactive mode only,
-pand ACP reply with an interactive-onlymessage.
Demo
Design choices
[*self.messages, question]) and calls thebackend directly with
tools=[], so the model can't trigger tool callsduring the side question. Nothing is appended to
self.messages./status) via the normalaccounting path.
ExpandingBorderaside(
BtwMessage), with the usual Generating spinner during the call.Limitations
meta.jsonstats only rewrite when messages change;/statusislive in-memory.
-p) or ACP surfaces by design.