Workflow Acceleration

SideQuestions

A long task is streaming and you want to check something the AI said ten minutes ago. Type @btw and ask. The answer streams into a small card above the input, the task keeps running, and the session history never changes.

Download

Ask Mid-Task, Get an Answer Mid-Task

The AI is twenty minutes into a long task and you need to check something it said earlier. Type @btw and your question in the chat input, or pick btw from the @ mention menu. A separate single-shot call answers from a snapshot of the conversation while the task keeps streaming.

  • Type @btw plus your question in the normal chat input
  • The question runs concurrently; the task never pauses
  • Answers from a snapshot of the conversation so far
  • Works when the AI is idle too

A Floating Card Above the Input

The answer streams into a small card above the chat input, not into the conversation. Stop it mid-stream, copy it, or step back and forward through the earlier side answers from this session.

  • Stop button while the answer streams
  • Copy the finished answer
  • Back and forward through earlier side answers from the session
  • Esc closes the card first; a second Esc stops the running task

The Session Never Notices

A side question reads a snapshot of the conversation and writes nothing back. The exchange never enters the session history, so the context the AI works with on its next turn is exactly the one you had before you asked.

  • No new messages in the session history
  • The running task continues untouched
  • Nothing queues behind the task and nothing replays
  • Side questions are text-only; attachments stay in the composer

The Inverse of a Sub-Agent

A sub-agent starts with a blank context and full tools. A side question is the opposite: it reads the whole conversation and gets no tools at all. It cannot read files or run commands, which is what makes it safe and fast to run beside a working task.

  • Full conversational context from a snapshot
  • Tool-free: cannot read files or run commands
  • Reuses the session provider with a minimal system prompt
  • No tool definitions on the request keeps each answer cheap

Fork When the Answer Deserves More

Some side answers open a thread worth pulling. Fork to new session starts a clean session containing your question and its answer as real messages, with full tools. Dig deeper there while the original task keeps running.

  • One action on the card: Fork to new session
  • A clean session holding just the question and its answer
  • Full tools in the forked session
  • The original session keeps its full history and its running task

Under the Hood

Concurrent by Design

The question runs as its own single-shot call while the main task keeps streaming. Nothing pauses, nothing queues, nothing replays.

Zero History Footprint

The exchange never enters the session history. The next turn of the task sees exactly the conversation it saw before you asked.

Cheap by Design

Reuses the session provider with a minimal system prompt and no tool definitions, so a side answer costs less than a normal turn.

Fork to Go Deeper

Turn a side answer into a clean new session holding the question and its answer, with full tools for the follow-up work.