Don't Want to Break a Long Workflow? Slip in a Side Question with /btw

While running a long task, have you ever suddenly wondered "what was that config file name again?" But you held back because asking now might disrupt the context of the work in progress. That is what /btw is for. The name comes from the English "by the way." It lets you leave the main work as is and slip in just a side question.

Definition

/btw is a command that asks a light side question without breaking the main workflow. The key points are two.

• Does not break the flow: It does not touch the context of the main work currently in progress.
• Leaves no record: The question and answer are not saved to the conversation history (context — the conversation content the AI remembers). It is like a sticky note that appears and disappears.

So it is a perfect fit for "I just want to ask quickly without dirtying the context."

How to Use (by difficulty)

Basics — A Quick Recheck

Type /btw in the chat box followed by what you are curious about.

/btw 아까 그 설정 파일 이름이 뭐였지?

Once you enter it, only the answer appears briefly on screen. And this question and answer do not remain in the main conversation history, so the context of the work in progress stays neatly intact.

Advanced — Checking During Work

/btw 방금 그 함수 어디 있었지?

Use it to quickly recheck content that already appeared on screen or information Claude knows. It feels like a quick glance to the side without stopping the main work.

Deeper — Branching a Side Question into Full Work

/btw 질문 → 답 화면에서 f 키

If you like the answer to a /btw question and think "I want to take this into real work," press the f key on the screen where the answer appeared. That branches the side question into a new session (a separate work conversation) so you can handle it in earnest.

Common Pitfall — It Does Not Read Files or Search

A /btw answer comes only from "what is already known." That is, Claude does not open a new file or search the code on the spot. It deliberately operates lightly so as not to touch the main workflow.

So for questions that actually require digging through files, like "how many functions are in this file?", it may not be accurate. Ask those properly in the main conversation. /btw is best used for light rechecks at the level of "that thing from earlier."

Real-World Example

A long automatic refactor had been running for a while. I suddenly wondered "where was this variable defined again?", but jumping into the main conversation now seemed like it would disrupt the context of the work in progress. So I slipped in this question.

/btw 이 변수 어디서 정의됐지?

I just checked the answer briefly, and the main work kept running with no effect. I resolved my curiosity while the flow of the main work was never once interrupted.

Using It Further

• Ask without breaking the flow: Ask briefly without stopping the main work in progress.
• Leave no record: Side questions stay outside the main conversation context, keeping it clean.
• For light rechecks only: Use it to confirm already-known content, like "what was that thing earlier?"
• Branch if you like it: Press f on the answer screen to grow a side question into full work.

Tip: While you delegate a long task and wait for the result, gather the random questions that come to mind and ask them with /btw. You can resolve your curiosity without ever interrupting the main work.

Summary

The core fits in one sentence. Do not break the flow; slip in a question with /btw. When something comes to mind during a long task, instead of jumping into the main conversation and disrupting the context, throw just a side question with /btw. Just note: questions that require digging through files are best asked properly in the main conversation.

Based on: Claude Code v2.1.154 (2026.05)