…or I’m using it incorrectly. I understand the point: pull in the current context and ask a question, without polluting that context. But… It’s a completely useless feature. Here’s why. I’m fairly sure that most people who sidebar a) end up having to fork, and b) want to revisit that sidebar at some point, without having to parse JSONL files. /btw looks really convenient, at first. For the conversation, it spawns a process, that process is visible in the subagent list, and you can navigate to it. But…
- Leave it too long, and it gets reaped.
- Navigate back to the agents panel, it gets culled.
- Try to use the /btw command again, and it replays the prompt…from the beginning.
- Fork it, and it behaves similar to /fork except that…see above.
- You want to avoid /branch and /fork, because they clutter your agents panel and possibly pollute your context.
- You want to avoid spawning a new agent because it just clutters your panel.
- Forking a /btw conversation does the same thing as /fork, but has no level of persistence.
- The point of /btw seems like it would be to keep your tangent thoughts organized separate from your list of Agents, but they live and die in memory.
- Last, and best of all, the UI glitches in the CLI are abhorrent. Do you really need to summarize every turn in /btw in the main thread? I only hope that garbage isn’t being drawn into my project context window. Stupid feature. /rant submitted by /u/syllinger
Originally posted by u/syllinger on r/ClaudeCode
You must log in or # to comment.