// transcript — 80 segments
0:00 Introduction to /btw
0:01 Anthropic just dropped one of the most useful features in Claude Code ever.
0:06 It's called /btw. It saves you twice the tokens and allows you to do things in
0:10 half the time. And I don't really think a lot of people know about it. Now,
0:13 previously, if I was having a conversation with Claude Code, let's say
0:17 I ask it to scrape a,000 paperclick agency owner leads and then give them to
0:20 me in a Google sheet. I've wanted to ask a question to Claude Code in the middle
0:24 of this. It might have been related to the skill to the context that we just
0:28 loaded in our token window. Well, the only way for me to do this would have
0:31 literally been to open up another Cloud Code thread, ask it a question, tell me
0:37 about scrape leads, and then have it go on its way. The issue with that,
0:40 obviously, is every time you load a new instance of Cloud Code, you're consuming
0:43 a tremendous number of tokens that aren't actually related to the work that
0:46 you're doing. You basically have like a fixed 10 to 20,000 token cost every
0:50 single time you open a new window. And there was no way not to consume that.
0:55 Well, that's where /BTW comes in handy. Now, I could tell it to scrape 10,000
0:59 PPC agency owner leads. But if halfway through I have either a follow-up
1:03 question about this, or maybe I want it to give it to me in a CSV, all I need to
1:08 do is type /btw and then write what I want to say. So, sorry, I meant a CSV. This will
1:15 dynamically open a new window called the /BTW window that allows us to insert
1:20 information through the conversation chain without actually interrupting the
1:24 thread. I can also ask it questions about let's say the specific skill
1:28 taking advantage of a lot of the functionality and features here. So I
1:30 How /btw Works
1:32 could say /btw tell me how this skill works while it's currently working on the skill it'll
1:38 also go through the skill documentation and then instead of forcing me to reload
1:42 all of my tokens now it's giving me uh context and information in this little
1:46 answering thread. And you can see it's actually doing that while it's also
1:49 debugging the rest of everything up above. So based on what I've read so far
1:52 here's how all of it works. This is a window that doesn't close as the context
1:55 continues to pump above here. And so it's also just a lot more convenient
1:57 because now we have this little side window. We can have a conversation with
2:01 it without necessarily needing like 20 parallel instances. So this is a big
2:06 deal. Previously before BTW, you know, I was spending significantly more in token
2:09 costs. Anytime I wanted to ask a question that was related to the context
2:13 of the first thread, but maybe didn't want to interrupt that main thread, I
2:16 had to open up a whole new cloud code session and then in that cloud code
2:19 session say something like, "Hey, go find me the conversation context from,
2:23 you know, the conversation I was just having on X, Y, and Z." We have to
2:27 refind assets. We have to split our context. There's just a tremendous
2:30 amount of work that basically we need to do, uh, you know, in order to get that
2:34 done. But with BTW now, we can actually have the main conversation window up
2:37 here and then have a little side conversation down here without actually
2:41 having to like parallelize without actually having to, you know, switch our
2:44 our our context and then start multitasking and so on and so forth. So,
2:48 it's way cheaper. You have everything in a unified context window just on one
2:52 thread. So, the quality of the responses probably goes up. Terms of how this
2:56 works, it's about as simple as possible. You just type /btw.
3:00 You have to be in a terminal version of Claude Code as of the time of this
3:03 video, but I bet you that's going to change. You then give it the request in
3:07 the same message. So, don't just type /btw and then press enter. That's not
3:12 going to work. You have to type /btw space whatever the heck you want. That's
3:16 going to open up this little side panel here with the /btwin in yellow. And then
3:20 you sort of have three options. You can read through this, then press space,
3:22 Benefits of Unified Context
3:25 enter, or escape to dismiss. When you do this, I'm going to press space over
3:28 here. you'll just snap right back to the main thread and that'll open you up to
3:32 ask other questions. What's going on with these, I don't know, errors, for
3:36 instance. That'll allow Claude to actually answer me without me actually
3:39 having to pause this every 5 seconds, I can actually gain context while things
3:42 are going on. If you don't currently have this, it's pretty simple and
3:46 straightforward to get. Make sure on the top leftand corner of your anti-gravity
3:51 Visual Studio Code instance, you open the extension, click on the settings. If
3:55 you don't already have access to this, it's probably because your cla code
3:58 either extension or maybe your cloud code for desktop functionality is not
4:03 updated. So, make sure that autoupdate is on. If you have a specific issue with
4:07 this, you can actually go click install specific version. And then you can
4:10 update to the main version here, which is 2.1.73, in this case, uh, 36 minutes ago. Um,
4:16 you know, you can also just uninstall Cloud Code if you're using the VS Code
4:20 instant, and then reinstall it. That usually works fine. Once you're done
4:24 with that, head over to settings and then at the very bottom here, you're
4:27 going to always want to have use terminal on. Otherwise, you're going to
4:31 have to manually go into Claude's GUI and then type / terminal, which while
4:35 possible is just kind of annoying to do and it usually takes a fair amount of
4:39 time. Just because of how cloud code works and the fact that the terminal
4:42 version was first, they usually develop the new features for terminal despite
4:45 the fact that you might have seen me use the GUI in other videos. I do that more
4:49 for simplicity, not for cutting edge features. So definitely take a look at
4:52 that. That'll open up this new terminal thing and then you could say, "Hey,
4:54 Implementing /btw
4:56 what's up?" And while it's answering, you could ask something else as well.
5:00 Hopefully that clarifies things and you guys now know everything you need to
5:04 know to crush the /BTW feature. Change your workflow. Take advantage of both
5:08 the in-built parallelization and the