claude-code - 💡(How to fix) Fix [DOCS] /btw fork hotkey not documented

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/interactive-mode#side-questions-with-%2Fbtw

Section/Topic

Side questions with /btw

Current Documentation

Currently says: "Press Space, Enter, or Escape to dismiss the answer and return to the prompt."

What's Wrong or Missing?

Doesn't mention the "press f" option to fork a /btw

Suggested Improvement

  1. Mention the option exists
  2. Explain what forking actually does
  3. Add example of a forked dialogue

Impact

Low - Minor confusion or inconvenience

Additional Context

Local session shows the option. Just a documentation gap. Caused a confusion in my local session when reviewing previous planning sessions. Local session checked the docs and gave me:

"On /btw: per what I dug up, it's meant for quick asides that don't bloat the current session's context — not for forking. Your build-vs-buy pivot in Session 1 was a genuinely new direction, so /btw probably wasn't the right tool there; a fresh session (claude / claude -c) would have been cleaner. Use /btw for "noting a thought without derailing", not for "starting a new line of inquiry". (Caveat: I'm relaying a guide lookup, not first-hand verification — worth a quick /help if it matters.)"

After pressing it with ""/btw" I'd like to push back on since it has a fork option I assumed I was using it correctly" it returned "Conflict — my second lookup also found no fork option in the official /btw docs. The docs describe it as an ephemeral side-question overlay that doesn't enter conversation history, full stop. The guide agent suggested you might be thinking of /branch (which actually forks a session, inheriting context up to that point), or that a plugin/skill on your machine extends /btw.

Worth a 10-second check next time you hit it: if the picker offers multiple actions, screenshot or note the option labels — that'll tell us whether it's a built-in I'm missing, a plugin extension, or /branch you'd been reaching for. Until then I genuinely can't tell which of us is right, but if you saw a fork option in the UI then something on your install offers it."

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING