B (3:25)

Yeah. Yeah, let's do it.

A (3:26)

So what are we looking at right now, Boris?

B (3:29)

Yeah, so this is the, this is the cloud desktop app. So you just download it. Cowork is only available for macOS, you know, Windows coming soon. There's a few different tabs in the desktop app. So there's the chat, that's the default. There's Cowork, that's the new one. And there's code, and that's just Claude code. Cowork under the hood, it's actually just quad code. And so, you know, the agent that makes quad code awesome, we call it the Quad Agent. It's also available as the cloud Agent SDK. So you can use it programmatically. You can, you know, all sorts of companies build all sorts of cool things on top of it. We actually use that same exact SDK directly in Cowork. So it's like, you know, it's pretty cool. It's just kind of one layer across everything. We have the best agent, have the best agentic model, might as well use it. And so what I'll do is just to kind of show how to use this thing. And, you know, like, when I think about agentic AI, this word agentic has sort of lost all meaning because it's just like used so much. So I feel like probably A lot of listeners have heard the word agent, but they don't actually know what it means or, you know, they think it's like some like cool AI or something. But it actually has a very specific meaning in the AI world, which I think has kind of been lost because a lot of the products that people have released and called agentic in the past are not actually agentic. And so when you think about the AI products that everyone's used, obviously cloud code, chat based apps where you just chat with the app back and forth, send some messages. The biggest difference with agents is it can take action and it's not just text and it's not just web searching, but it can actually use tools on your computer. It can interact with the world. And so for Anthropic, from the very beginning, since before our models were good, before Quad three or whatever, this is a thing that we wanted to get really good at because we felt that it's very important. And so from the start we wanted our models to be really great at coding and then really great at tool use and then really great at computer use. So it's kind of cool. Like the last year, seeing how people have been hacking quad code, it's pretty obvious this is kind of the place that we should go. And so for people that have used quad code, none of this will be too surprising. These are actually things that you can do. So really what we're trying to do is make this something that everyone can use in a way that's safe. And so what I'm going to do is here on my desktop, I have this receipts folder. I have a few receipts in it. So I'm just going to give Cowork access to my desktop. And you have to pick which specific folders I can see. By default they can't see anything. So you have to kind of opt in to see, to let it access specific folders. And so I'm going to say, you know, I can say I have a receipts folder. Can you rename the files to match the dates on the receipts?

A (6:29)

So I think one interesting thing is when you're using Cowork, it's really like it's operating with your files. Like that's, that's a big sort of mindset shift that people should have. It's almost like your operating system. Is that right?

B (6:44)

Yeah, exactly. It's like it has your files, so the ones that you give it access to. But actually the even cooler thing is it can use all sorts of tools. And so like Files actually is like, you know, that's like, that's useful, but it's not, it's not like that. Cool. What's actually much more interesting is it can generate files for you. So, you know, it can make like presentations and things like this. It can interact with any tool over mcp and it has built in support for Chrome based browsers, so it can actually control your browser to do stuff. And so I'll kind of show that a little bit. So this is kind of the first step when you're first getting started with Cowork. The thing I recommend is do exactly what I just did, dismount the folder, give Cowork access to it and just play around with it. It's super useful for cleaning up files, organizing things like that. And so here it found these four receipts that I have. It's asking me if one of the receipts I guess is missing a date, so should it just rename the others? So I'll just say, you know, for one it's, let's say it's like up to you and then for two I'll say don't rename it. And we actually call this like reverse elicitation in the AI world. So what this means is when the model is unsure about something, it's going to ask you for clarification. And we've sort of taught the model to be pretty good at this. So instead of assuming if it's unsure about something, it's just going to ask you. And so yeah, in this case it renamed the receipts. So I'm just going to open this up to double check. Yeah, cool. And so the receipts were named a little bit better organized. And so maybe what I can try next is let's put this in a spreadsheet.

A (8:30)

So it takes control of your computer basically in that sense, right? If you allow it to take control.

B (8:37)

Yeah, yeah, that's right. So we put so much work into kind of safety and making sure that as this happens you don't accidentally shoot yourself in the foot and delete files or whatever. So there's just a huge amount of work that went into this. And it kind of starts at the model side where for anthropic, from the very beginning we were the AI safety lab. And that's the reason that we exist. And so there's a lot of work into alignment and mechanistic interpretability and all these ideas to make sure that the model does what you want in a way that's safe kind of at the model layer. And this literally means studying the neurons kind of the same way that you would study neurons in a human, and so you can identify structures and you can kind of study in a very scientific way as a black box also to make sure that it's safe. So this is called alignment. And then we do a whole bunch of other stuff. So there's actually a whole virtual machine running under the hood. And this is just to make sure that any actions taken are safe and don't affect your broader system. And then as of last week, there's also deletion protection. So if you accidentally delete something, then you're going to get prompted first. So the model can kind of make sure that that's actually a thing that you want to do. Obviously also, as we start interacting with the Internet, something like prompt injection is. Is quite scary. And so we built in a lot of protections against that. Obviously it's not perfect and it's something we're iterating on, but this is also part of the reason that we released this pretty early is we want to see how people use it. And a big part of making models safe isn't just studying them in a lab, but studying them in the wild to see how it's useful. And so this was pretty cool, right? So we have this folder first. It kind of renamed all my receipts. I asked it to make a sheet. It just made this spreadsheet. So it's already here. Maybe I don't want a spreadsheet. Maybe I want like a Google sheet.

A (10:27)

So actually, that's so interesting, right? Because like, I think where people stumble with tools like cowork and cloud code is because you can do anything. Making it. Of course that makes sense, making it a Google Sheet. But like, that's where it's so interesting that you can. You really can treat it like a teammate in that sense, right? Like go and do this thing. The world is your oyster. Whoa. What is happening right now?

B (10:55)

Yeah, so it's like it's opening the browser and so here it's going to ask me for permission just for this demo. I'm going to say always allow for the site, but you can just say like, allow once or deny. And so Quad's taking the wheel. It's making a spreadsheet for me. This is going to sort of take a while. And so this is one of the things that we're iterating on is like making this kind of computer use a lot faster. I remember, man, this is when I first joined Anthropic, and this was maybe this is like Sonnet 3.6 days or I forget what we called it, like Sonnet 3.5 new. And that was the first model that I think we really started to crack computers. And I remember I was sitting with my team and there was literally a researcher that ran into the room in the movies and was like, oh, my God, Quad knows how to use computers. And we just had it like, order a pizza and it picked a pineapple pizza and then ordered it, and it asked us for a credit card, and then we got that delivered to the office. But it was tedious. It took like an hour or something for it to click around. And since then, we've been improving the model's ability to use a computer. And so you can kind of see that here. So here the quad is typing and it's interacting with the spreadsheet and it can see what's on the screen. It can interact with it. Anything that's in your browser, it can just use.

A (12:12)

And could it use, like, email? You know, let's say we wanted to send this to somebody, you know, finance team, like, can you maybe we'll get into it later. But, you know, with things like connections and MCPs, is that possible?

B (12:28)

Yeah, yeah, totally. Okay, so let's like, let's make this, like, kind of a nice spreadsheet because we don't want to send like a badly formatted spreadsheet to our coworker, but let's make it nice and then we can ask Faud to send it. And so here it's kind of cool. It's like, you know, it's still early days and so there's some, like, form adding mistakes. It didn't paste it exactly correctly, but it noticed it so noticed that, you know, it's not actually split correctly. And so now it's trying to format it. So kind of notice this. And yeah, Greg, like, to your point, it's funny these, like, these use cases and the way that people are going to use these tools, like I said at the start, it's going to be so surprising. I'm just so excited to see how people use it. And sort of the crazy thing about them is they're so general purpose. It's sort of like a computer itself or like the Internet or something. Like you said when you first had an iPhone, you would never have predicted that there would be an Uber app at some point, but that's what happened. And I sort of feel like we're at the beginning of that. But for agents.

A (13:27)

Yeah, I think it's. It sounds so obvious in hindsight, like, of course you have a phone with gps, of course. Right. You're gonna, you're gonna have things like Uber and Doordash and stuff like that. But I feel like, yes, you're right. I think, like, what I'm trying to figure out in my mind, like I'm watching this and I'm like, this is really cool, but I'm thinking about like, okay, you know, how do I audit, like my entire company? Like, what are all the tasks that the company is doing? How are they interacting with files and how are they using the Internet and how are they sending things? And then what are opportunities I can use to like, make my team and also my life more productive? That's what's going through my head right now.

B (14:12)

Yeah, yeah, totally. That's a great way to think about it. And by the way, something that's kind of cool is, you know, as this is running, I'm just going to make a new task and do something else. So, you know, what are some cool episodes? Startup. Cool. And so while this one's running, we can like, we can let this one go too. And I often have a bunch of tasks running in parallel too. But yeah, that's exactly it. It's like you should just think about like, what, what's all like the tedious stuff that you do every day and you can just throw all this stuff to cowork. And I feel like this happened for coding over the last year because of course engineers and programmers are the earliest adopters. So when the tooling first became able to do that kind of work, engineers adopted it first. But now this is coming, now this is possible for everyone else to use too. So that's super exciting. And when we talk to engineers about the way they like to use quad code, they run a bunch of quads in parallel. They use it to automate the TDS stuff. And I don't know, man, like, for me, this is just the most fun I've ever had as an engineer because I get to do the stuff that I enjoy and I just feel so productive because quad does all the, you know, the stuff that I didn't want to do. Okay, so now we have this, like, we have this spreadsheet. This looks alright. It's not too bad. The data looks correct. You know, one thing that's missing though is, well, we, we can add maybe like the totals. But I think for the sake of the demo, what I'm going to do is I'm going to see if we can email it.

A (15:56)

So just reading for our audio listeners, can you open Gmail and Send the sheet to Amy and. Wow.

B (16:05)

Yeah, so I'm going to say always continue.

A (16:09)

So how is it going to know it's Amy, right? It's going to pull up the contacts within Gmail.

B (16:16)

Yeah, yeah, exactly. Yeah, that's exactly it. It's going to interact with it the same way that, you know, anyone else would interact with a computer. And it's the same thing. It can like click stuff. It can read the screen.

A (16:31)

Okay, so compose window open. Let me type Amy. So you have like multiple. When you're like locked in, so to speak, you're kind of. You have multiple of these windows open at or multiple virtual machines open at. At the same time.

B (16:45)

Yeah, yeah, I usually have a bunch of these, you know, like 5 or 5 or 10 or whatever. And so we can see the models, you know, trying to interact with this. And so it filled out Amy.

A (16:57)

And you know, by the way, just so, because this is, you know, going on YouTube, you know, you're going to have some haters in the comments, so we're just going to address them right now. Someone in the comments is going to be like, but that's so slow. I can do it faster myself or something. What is your reaction?

B (17:12)

Of course you can. Yeah, I could definitely do this much faster. And it's actually the same thing for a lot of quad code. Right. Especially at the beginning, I could do it much faster. But I think sort of two things happen. One is that the model just gets better at doing it quickly and this is just something I would expect over time. But then the second thing is because you can do multiple things in parallel, it's actually a big time saver. And so usually my workflow is I'll kick off a few different tasks in parallel and I'll just kind of go back and forth between them and kind of tend to my quads, make sure they're in a good place, see if they have any questions or anything like that. So it's really a different kind of workflow. I feel like now is the age of kind of multi clotting, of parallelism, of not going super deep on stuff, but kind of being more of a generalist and more tending to attending to your quads. And so this was this other chat that we kicked off earlier and in this case it sort of did some research. So that's pretty cool. So it didn't just go to, you know, like startup ideas podcast, website, but it searched the Internet, checked a bunch of different places, checked, like someone's notes about it. Yeah, 10, 10 rules for for quad code. Yeah, I'll find that interesting too. And let's see. So it seems like this is the email is probably all drafted, the draft has been saved. Please send. And I also use this for Slack too. A pretty common use case I've been doing maybe a couple times a week is I have a spreadsheet where we track all the team's work for the month or for the week or whatever. And instead of having to bug everyone on the team to fill out the status, we what I do is I ask Cowork to look at the spreadsheet. Any column that's not filled out, just message the engineer on swac and it does that really well. So I just ask it to do that and then I go get a coffee and I don't have to do that anymore.

A (19:10)

Do you think that Cowork is going to be the gateway drug to Claude Code? Because for a lot of beginners, non technical people, cloud code feels a bit overwhelming. But when I'm watching you do this, this feels, you know, approachable.

B (19:25)

Yeah, I mean I think it's like probably two kinds of users. And it's also, it's funny, Claude code is built originally in a terminal and you know, nowadays it's available in the Claude mobile app, it's available on the website, in the ide, on Slack, on GitHub. So you know, nowadays it's available everywhere. But originally it was built in a terminal and I never thought that most engineers would want to use a terminal because it's scary. It's like this thing that's sort of hidden away on the computer. Only the most hardcore engineers want to actually work in a terminal day in and day out. And so it's surprising to me that most engineers wanted to use it. What's even more surprising is a lot of non engineers started to use it and that was the craziest thing. And looking at the sales team at Anthropic, like the GTM team, half of them use quad code every week. And looking at other non technical people at Anthropic, like designers, product managers, data scientists, pretty much all of them use quad code every day. So that's been pretty surprising. But my hypothesis is what they would prefer is actually something a little bit more like this, where you don't have to deal with a terminal and all that kind of thing. You have a nice UI because you don't need access to bash and all that kind of stuff because the model will just do it for you.

A (20:38)

Yeah, I think what I would love with something like this is automating some of these processes. It's like, instead of doing one offs, it's like, anytime this happens, I want you to do this. That's my dream.

B (20:54)

Yeah. It's a cool idea. I'm excited to see, like, how it's tied into Skills. Also. I think it's something we're. We're thinking about. We haven't quite figured out yet. Yeah. Because, like, a skill, what is it? It's essentially kind of a repeatable way to do something. And so you saw that a little bit earlier up in this conversation, where, when Claude was generating this spreadsheet, I don't know if you saw, but it actually loaded the skill. And so we prepackaged the skill for Excel, and that's the way that Claude knows how to do it. And so if you have some weird file format, I don't know if you work with AutoCAD or if you work with Salesforce, whatever it is the tool that you use, you just make a skill and then Claude can do it for you.

A (21:35)

That's interesting. So if you have more skills, Cowork, and you're asking it to do things related to those skills, coworker is more likely to use those skills. So you might be able to get a better outcome out of Cowork if you do some upfront work to actually create some skills.

B (21:57)

I think so, yeah.

A (22:00)

Wow.

B (22:00)

Yeah, I think. I think that's exactly right.

A (22:03)

Yeah. Okay, well, that's good to know. And. And, you know, what else do we need to know about Cowork? Because I know there's, you know, there's extensions, there's skills, like, walk us through some of. Is there anything else that we need to know in order to get the most out of the product?

B (22:23)

You know, we tried to build Cowork just to be pretty simple. When we think about the different audiences we serve for an audience like engineers, they don't actually like simple. Like, simple is good by default. But engineers love to hack their tools. They love to customize their tools, so that's actually really important. So Claude code is just like the most customizable coding agent. It has just, like, so many extension points. There's like, there's skills, there's custom agents, there's hooks, there's an insane amount of configuration and settings that you can set. You know, there's a very sophisticated permission system. So there's all sorts of ways to customize it. And this is because we know every engineer works different, and everyone has different preferences. Everyone uses a different tech stack, everyone uses a different editor, everyone use a different os. So we wanted to make sure it's really customizable. For some of my Cowork, I think we're kind of starting in the opposite direction and just keep it really simple at the start. And so if you use Cowork, I would probably not customize too much. Like if you have Cowork installed and you install the Chrome extension, that's pretty much all you need. And it'll do everything else for you, I think over time, as you find yourself using maybe software that Cowork is not great at. Like, that's the point to think about writing skills. But that wouldn't be my starting point. Just start simple, like, you know, see how it works, see what's useful. And I think also the other thing, you know, it's just, it's so early. This feels to me a lot like Claude code a year ago, where, you know, we released it before. It was early, it was not very good yet. It was like super buggy. It kind of barely worked. Like the model was not very good at coding a year ago. And it kind of feels like that to me. But I think our work is actually a little bit better than Quad Code was when we first released it because it's actually useful and it's already a thing that I use every day. And yeah, I think in the first week we've seen so much more growth. It's been a multiple of the growth that we saw with Quad code the first week. So that's very exciting. It seems like this is something that people are already finding useful.

A (24:22)

We're recording this. What is it? January 2026. If we, if we come back here in 12 months, it's January 2027. How do you think people are going to be using Cowork? You know, I know you don't have a crystal ball. Exactly. But what sort of use cases and what is, what does the product look like? Like, describe the world in January 2027 with, with cowork.

B (24:47)

Oh, geez, Greg. I plan in like a one week timeline. The model is just changing so fast. It's so hard. And I just feel like the model, it's advancing exponentially and just my puny human meat brain can't grapple with the exponential. It's like we think in linears and so I think this kind of exponential is just very, very difficult to plan around. Okay. But if I had to speculate a year ago, I made, and I think Dario also made this prediction that by the end of the year, people Wouldn't be writing code anymore. And I think that was like, sometime mid, you know, last year or something. In, you know, I code every day. I ship, you know, 2, 300 PRs every month or something like that. And in the last two months, QuadCode has written 100% of my code. I haven't written a single line by hand. And this is something like. I also predicted this, you know, like way back, middle of last year. It was sort of not intuitive because if you just think about the experience at the time and you trace it linearly, there's just no way that the model would be at that point. So you really have to kind of believe in the exponential and just literally plot it out and kind of follow the way that the line goes. That's the only way that you would have predicted this. And it was absolutely right. And so I think for coding, this is something that we're going to start to see in more and more places for more and more kinds of code that the model is able to just do all of it. And when we think about cowork, I think it's somewhat similar. I think it's a little bit earlier. And I think what we're going to see is for all this kind of tedious tasks like connecting app A and B or kind of shuffling data back and forth or whatever, the model is just going to be able to do it and it's going to get increasingly good at it. I think in some ways it's a little scary, and in some ways I think it's really exciting because you don't have to spend your time on this toil some work anymore. You can just focus on the work that you enjoy. And also everyone, I think, just becomes much, much more productive because you have an army of quads that can do this.

A (26:54)

Okay, I like that feature. I like that feature a lot. It's a hard question. It's a hard question. It's sort of like the genies out of the bottle, and it's hard to predict where the genie is going to go. So I believe that Cowork is the gateway drug to Claude code. I think that people are going to start using it and they're going to develop vertical use cases for whatever it is their business is. Like you mentioned AutoCAD. You probably weren't thinking about AutoCAD when you were helping develop Cobalt Cowork. So I think there's going to be these verticals, and I think. I think that Cowork is going to be similar to, like, vertical job boards where there's very specific roles that you can hire to people. And I do think that there's going to be this combination between skills and these, like, digital teammates that you're going to, quote, unquote, hire.

B (27:53)

Yeah, that's. That's super interesting. Maybe we should make a bet and just see where it pans out in the year. You know, I have no idea, but it's definitely interesting to speculate because I just feel like the way this technology goes is so different than past technology waves. It's sort of similar to the Internet. It's sort of similar to computers, maybe like telephones or something before that, but the speed is just so much faster. And because it's kind of piggybacking on all of this, the Internet could not exist without telephones and kind of like phone lines being everywhere. You couldn't have dial up without it. You know, mobile phones couldn't exist without the Internet existing. So it's sort of like every layer of the stack, it just gets more and more powerful and it spreads more quickly. And so it's like on the back of all of this that AI can exist. And, yeah, it's just gonna be very exciting to see, to see where it goes.

A (28:42)

I want to shift gears just for the last 10 minutes because we mentioned Claude code. You had a. You had a post that went absolutely f viral, I think. You know what post? I'm going to talk about 99,000 bookmarks, which is crazy. And I'm going to share my screen. I want to go over it a little bit.

B (29:02)

This is me learning to use Twitter. I think I made an account like a decade ago, and I haven't really.

A (29:08)

Used it, so it's funny.

B (29:09)

Yeah, it's been fun to learn.

A (29:11)

You have, like, just a few tweets, but like this, you know, this one, you figured it out. You say, I'm Boris. I created Claude code. Lots of people have asked for how I use cloud code, so I want to show off my setup a bit. My setup might be surprisingly vanilla. Cloud code works great out of the box, so I personally don't customize it much. There is not no one correct. There's no one correct way to use Claude code. We intentionally built it in a way that you can use it, customize it, and hack it however you'd like. Each person on the cloud code team use it very differently. So here it goes. Could you just talk about some of the. Just expand on some of these and what you were saying on here? Because I thought it was really interesting.

B (29:53)

Yeah, I'd love to. This first one, it's very similar to what I was showing in Cowork, where my job now isn't to go super deep on one task, it's to do a bunch of tasks in parallel. When I'm working on quad code, I usually work in a terminal or on the mobile app. These are kind of the two services I use the most. But like I said, everyone on the team is different. Every user prefers something different. So we build all of these. And so usually what I do is I'll start a task in kind of one tab, and once Claude is thinking about it and starting to work on a plan, I'll move on to the second tab and I'll ask it to make a plan for the second thing. Then I'll move on to the third one, ask it to make a plan. And then finally, like when I've run out of immediate tasks to do, I'll go back to the first tab, I'll see if the plan looks good, I might go back and forth a little bit. And then once the plan looks good, I usually go into just auto accept edits right away. Because I think with Opus 4.5, once the plan is good, the model can just execute it pretty much perfectly. This is definitely not the case with previous models. And so I think there was a lot of excitement about Opus Port 4.5 over the last couple months. And I think this is kind of one of the big reasons. It's just gotten very good at coding, but also excellent at planning. So once the plan is good, the code is good. And so, yeah, my, my work now is just jumping between tabs, kind of tending to the quads, make sure they're unblocked, answering their questions with Cowork. I think, I think it's actually quite similar now.

A (31:17)

I like that. I'm going to, I'm going to quote you on that. Once the plan is good, the code is good. Because that's so true. Right? Because if you nail the plan, the code should, you know, the agents should do the work.

B (31:29)

Yeah, exactly. I think sometime last year there was all this buzz about spec driven development and it just feels like. It feels a little too cutesy and a little too rigid to me. But I think this is sort of a form of spec driven development. It's like there is some kind of spec. I think it's just like a plan. That's all it has to be. It's just a text file. It doesn't have to be in a particular format. Once you have that, you're good.

A (31:52)

Number two, you say I also run five to ten clods in parallel with my local clauds. As I code in my terminal, I will often hand off local sessions to web using and or manually kick off sessions in Chrome and sometimes I will teleport back and forth. I also start a few sessions from my phone, obviously from Claude iOS app you got to every morning and throughout the day and check in on them later. What do you mean by that?

B (32:17)

This morning I kicked off, I think like three quads. As soon as I woke up. I just had some thought in the morning about well, maybe I should build this thing or fix this bug or whatever else like checking Twitter and someone had a bug report. So I just opened my phone and you know, in the cloud app you on the, on the left side you click the little menu and there's a code tab so you can just like access quad code there. That's what I use for a lot of my code. And it's funny, I never would have guessed that this is the way that I code. If you asked me a year ago, I would never have predicted that. The way I code now is like probably half of it is just on my phone and it sort of just works and then web is kind of the other part. So once I've run out of tabs because it's just like, you know, it's kind of a pain to manage a bunch of different git checkouts because in each tab on my terminal I actually have a totally separate git checkout and I don't really use work trees or anything like that. I just keep it pretty simple. And in web if I just ran out of terminal tabs, I'll start like overflowing to web and starting tasks there.

A (33:15)

Beautiful. So yeah, I also. So recommending use iOS use web open multiple like that's what that's. You'll get the most out of it that way.

B (33:27)

Yeah, absolutely. Yeah. And we have an Android app now too. So yeah, just like use the mobile app and see how far that can take you if it's not giving you good results. Also make sure that you tune the environment set up and make sure that you invest in your claw md. That's super duper important and I talk about that in number four. Also.

A (33:46)

Number three, you say I use opus 4.5 with thinking for everything. It's the best coding model I've ever used. And even though it's bigger and slower than Sonnet, since you have to steer it less and it's better at tool use it's almost always faster than using a smaller model in the end and cheaper.

B (34:04)

It's sort of counterintuitive, and I had to explain this to people a few times, but because the model is smarter, it actually uses Wes tokens in the end and it uses so many less tokens, it's often cheaper than using a smaller, less intelligent model, even though the per token cost for that model is lower. So a little counterintuitive, but yeah, just use the smartest thing if you can.

A (34:28)

Well, we appreciate that. You know, we appreciate that. Number four. Our team shares a single Claude MD for the Claude code repo. We check it into git. The whole team contributes multiple times a week. Anytime we see Claude do something incorrectly, we add it to the md. So Claude knows not to do it next time. Other teams maintain their own Claude mds. It is each team's job to keep theirs up to date.

B (34:54)

And QuantumD is just a text file, so there's no special format. People ask this all the time. Is there some special format that it has to be in? No, it's just like. It's just a text file, so you can put whatever you want in it. This is a screenshot of our QuantumD. This is literally it. So just really simple and, you know, you could format this kind of however you want.

A (35:13)

Love it. And then finally, I think, yeah, number five. Oh, no, you have a. You got a few more. So number five. During code review, I'll often tag Claude on my coworkers PR to add something to the Claude MD as part of the PR, we use the Claude code GitHub action for this. It's our version of Dan Chipper's compounding engineering. What do you mean? What is compound engineering?

B (35:39)

Yeah. Oh, my God. So there's actually like two bugs in this tweet. I think Dan actually calls it compound engineering, not compounding engineering. And then the claw. This is me learning how to use X, but it's actually claude. There's no dot. I just didn't. I think there's like an actual user or something whose name is Claude. I didn't want to tag them, but yeah. So what you do is in quad code, you run this command install GitHub action. And what this does is it installs the Claude app in your GitHub repo. And what that lets you do is you can then ention Claude whenever you want and just have it make changes and it can just work on pr, so it'll push back to your branch and it'll push the changes right back. You can also tag it on issues. You can tag it kind of wherever. I do this multiple times a day. It's really, really useful. I think one of the most common use cases is just like little fixes. I think the other one is updating the quantumD to keep the knowledge base up to date. And you know, you should never have to comment about something twice. Back when I was at Meta, something that I did is. This is like in a previous life, in a previous job, something that I did is every code review that I did, I would keep a spreadsheet of all the issues that came up and whenever the same kind of issue came up again, I would just like tally it up in the spreadsheet. And whenever something hit, I think like five or ten tallies or something, I would write a lint rule. And what that is is it's a way to automate that part of the code review so I don't have to comment about it again. And that was back in the days before LLMs and before the model was any good at coding. And so this is the equivalent nowadays you just tag Claude and you have it update your CloudMD, which is your team's knowledge base. So really simple. And what this means is you don't have to point anything out twice. I'm curious to see what this looks like for cowork. I don't think we've figured that out yet, but definitely for quad code, CloudMD is kind of the. This is the one thing that you should all be updating all the time.

A (37:34)

Love it. Number six, most sessions start in plan mode. If my goal is to write a pull request, I will use plan mode, go back and forth with Claude until I like its plan. From there I switch into auto accept edits mode and CLAUDE can usually one shot it. A good plan is really important.

B (37:53)

Yeah. Like I said, planning is just the most underused feature in quad code. Actually a lot of people use it, but I would say still underused. I use it for almost all my sessions.

A (38:04)

Yeah, it's, it's a no brainer. So if you aren't already doing this, please do do. We've got, you know, we're not going to have time to do all of them. What are the. I don't think because you have a hard stop, do you want to pick one or two to end with?

B (38:24)

Yeah, let's do, let's do maybe number 13. Yeah, number 13. I think this is probably in addition to using Opus for when people ask about how to get better performance out of quad code. There's three things that I recommend almost every time. Number one is use Opus 4.5 with thinking. Always don't try to use a different model, because Opus will just give you better results and more efficiency overall. The second thing is make sure you have a good quad MD. And then the third thing is this tip number 13, which is give Claude a way to verify its output. And so we just kind of saw with cowork how good Claude is at using the Chrome extension in order to write email and in order to work with sheets. And it's exactly the same thing. If I'm building an app, I always use the Chrome extension to have Claude test its own work. And if Quad can verify its own output, the result is going to be way, way better. And it's sort of like, imagine that you're a painter and you make paintings and they have to be pretty good. They have to be maybe even photorealistic or something, or just some kind of very detailed style. And you have to wear a blindfold. You're just not going to be that good. It's not going to come out that great. Or is the same thing for an engineer, if you have to write code, but you can never run the code or you can never see the output and you can never see the website, it's just not going to be good. And so it's the same thing with Claude. As the model gets more intelligent, that first shot is going to get better and better. But really, you want to give it a way to verify the output and it'll be much better. So this is like running tests if you're an engineer starting a server. Also if you're an engineer or, you know, seeing. Seeing the output in a simulator or in a browser.

A (40:06)

Amazing. And the ultimate tip, I guess, is just get your hands dirty. Right?

B (40:11)

I think that's it. Yeah. I mean, there's no right. There's no one right way to use the stuff. Like, you know, see. See what's useful, see what's not. Find your own workflows. It's sort of. I heard someone describing Quad code as like a find your own path book. You know, like one of those books where you have to like, do you go to the dungeon or do you explore the forest, like this kind of thing, or like an old, like, RPG video game. It's kind of like that. It's very free form. There's no one right way to do it. So just see what works for you.

A (40:39)

Boris, I appreciate you taking the time, the generosity to spill the sauce and Just to share with us how we can get the most out of both Cowork and Claude Code. Everyone's thinking about it and everyone's trying to. Especially on this podcast, you know, the Startup Ideas Podcast. You have millions of people who are trying to figure out how I can be more productive and how I can build businesses around some of these things. So thank you. Thank you for the time. I'll include links on where to follow Boris. He doesn't tweet a lot, but when he tweets, it's worth paying attention to. And I just have. I want to leave with one thing, just because my audience would kill me if I didn't ask this. So, as you know, Boris, I'm from French Canada, and we speak French, obviously, in French Canada. And I call Claude Claude. Am I the only one?

B (41:33)

Man, you're probably not the only one. A lot of the world speaks French. Which one sounds better?

A (41:40)

I mean, to me, Claude sounds better. It's like Jean Claude Van Damme. Even though people would say Jean Claude Van Damme, it's like, that's my take. That's my hot take. To me, it sounds better.

B (41:53)

You know, Greg, I'm gonna. Today around the office, I'm just gonna call it Quode, and we'll see what people say. I'll report back.

A (41:59)

Okay, Report back. All right, sounds good. Boris, thanks again for coming on, and I'll see you next time.

B (42:05)

Yeah, thanks so much, Greg.