Vibe Check: Claude Cowork Is Claude Code for the Rest of Us

Source material

Full source text

If you're a non-technical person, you are used to a world where you send a prompt and then you get a response within a couple minutes.

And once you send a prompt or a chat you can't do anything else with that AI.

This is built for working with your AIs in an async way.

This new cloud core app is a really good example of Agent 8 of architectures, which means at the bottom of the app, instead of having like software that works by deterministic rules, you have an agent and the agent is wired up to the UI of the app.

I've been in anthropic for a little bit, but this is the product that my team has built here.

We've sprinted at this for the last week and a half.

What we're trying to do...

Last week and a half?

That's it?

Come on!

We've got a new anthropic drop.

So, anthropic just dropped "Claud Co-Work", which is basically cloud code for non-technical people.

We got access to it early at every, and so I'm going to give you a quick run-through of what it is and how it works.

We will have a full write-up on every in a few hours probably.

We're just kind of figuring out how to do these things.

So, I'm going to add Kieran.

Kieran is here.

Hello Kieran, how are you doing?

Hey, what's up?

So, I'm just telling everybody, if you just got here, we are about to do a vibe check of anthropic's new "Claud Co-Work" feature, which is basically cloud code for non-technical folks.

I'm going to just demo it for you right now in here.

Let me just share my screen.

All right, so this is what it looks like.

It's "Claud Co-Work".

So, you'll see we've got the chat over here to the left.

You've still got regular chat.

You've got code here, and then we've got "Co-Work".

So, it's three to three Cs.

It starts with "Let's knock something off your list".

I love the copywriting here.

You can tell from the way they did this that it's really designed to do deeper tasks on your computer than maybe chat is.

So, create a file or crunch data or make a prototype, send a message, organize files.

It's got over here progress.

It's got artifacts, context.

We've been playing around with this for a couple hours now.

I think it's cool.

I think it's cool.

I think there's a lot of really interesting questions from the UX perspective of chat versus code versus co-work.

And I think you can really think of co-work as being...

It's like chat that has access to your computer and runs for a long time, which is essentially cloud code, but just less intimidating.

So, a couple of things that we did that I think are kind of interesting to look at.

Okay, so here's an example of it working.

I asked it to go to the every.to website and find five competitive companies that do the kind of consulting that we do and then analyze our positioning.

And you'll see it just went and used my computer.

It's running in a long loop.

So, this is a really interesting one where you can do this with regular cloud.

Like, cloud can do this, but the number of iterations that it's going through, this is many, many, many minutes of iterations.

So, it looks a lot more like...

Actually, can you make this mark down?

So, it looks a lot more like cloud code, but it's friendly enough for anyone to use.

Well, we'll look at the...

Another thing I had to do, I have a dinner that I have to go to tomorrow night that I had to prepare some remarks for.

And I asked it to basically go to my Gmail and prepare remarks.

It has a connector to Gmail and to Google Calendar, but the connector wasn't working I think because this is very beta and was not out when I was testing this.

And let's see.

And I asked it to draft a response.

And it drafted a response.

And I think the response is actually pretty good.

So, this actually sounds like me.

This is kind of crazy.

Here, you've got to look at this because this is...

That's an implication for Cora.

So basically, the setup was I have a dinner tomorrow that I have to do remarks for.

And I asked it.

And the whole organized dinner was asking me, can you tell me what you want to talk about?

And so, I just said, find the email and draft a response based on what you think I would say.

And this is something that I could...

I think I actually could send with minimal edits, which is pretty cool.

Are you seeing this, Kieran?

Yes.

Looks good.

I think one of the things that's good about this is it's gone through many, many steps to both identify what I would say and how I would say it and has all the context, which is pretty cool.

Yeah.

Go for it.

Yeah.

So, how is Go Work different than chat?

Go Work is more made to...

You can share your screen.

But it's more made to go longer, really work on something.

So it's more focused on getting some work done.

And this is what we know in closed code already, like when you trigger Ultra Think or your trigger planning modes, things like that.

So it is similar in certain ways, but also it will unlock a lot of things that you use as a developer in closed codes that now suddenly work very well for non-developer tasks.

Yeah.

So I'm sure to see this being a thing that just really accelerates our growth team or our people who are in our consulting business who want to do some of these tasks and maybe are using Cloud Code, but maybe it's a little bit less intuitive.

It should be released now.

I think that they're maybe holding it back, but the blog post is live.

So you can take a look at the blog post.

It's a co-work research preview.

I'll throw it in the chat.

And yeah.

So I think it'll be out soon.

I'll like I can check with my anthropic people.

But okay, let me go back to this.

So I also asked it to do a calendar audit.

It looks like it's actually still running on this, which is crazy.

I asked this like an hour ago.

Go through the past month of my calendar and do an audit.

Tell me how this reflects my priorities and whether it's aligned with my goals.

Just browse on Chrome.

Can you share your screen again, please?

Oh, shoot.

Yeah.

Thanks.

Yeah.

Go through the past month of my calendar and do an audit.

Tell me how this relates to my goals.

And it just, you know, it's been browsing on my computer for like hours and hours.

One thing that's, or not hours and hours, but like for about an hour.

One thing that's different about this, which I think is really interesting is in Claude, when you start a chat and it's responding, you have to stop it in order to send a new message.

But this just I can just add to the queue.

So this is a little bit more like the this is more like the Claude code experience.

So I think this is this is one of those situations where it's built for you to send stuff as it's working and it's not like a back like one message, one response, one message, one response.

So it's really more built for long, long tasks.

Yeah.

And it has the to do task also built in on the right, which is nice.

So you can see where it is and what it's doing.

Yeah, exactly.

Another thing I did is I fed it a book and I this is a book that I it's called The Outsider that I've been reading for a book that I'm writing.

And I just asked it to like basically read the book, read the entire book and construct a taxonomy of all the main characters and ideas.

And looks like it did this.

And this is something that you could also do with with the with regular Claude, but it would be it would just be less detailed.

This is really interesting.

So yeah, so if you want to trigger those longer running tasks, like you can just say, no, you make a plan do this.

So I assume if you just push it to do that more, it will just run for longer.

So if you say take an hour to read through every single email, it won't give up as easily as before.

And it will just keep going.

So yes, try those things.

Yeah, it has a it has a it does have a plan mode.

It said I have not used the plan mode yet, but that's pretty cool.

I also asked it to go through our post hog analytics and do some data gathering.

So we published this guide if you haven't seen this guide, it's like I keep talking about this.

Everyone and everybody's like making fun of me because I can't stop talking about agent native architectures.

We published this guide last week and we have these we have these buttons read with Claude Riu, Chechi, and I was curious, OK, how many people click these buttons?

And that's the kind of thing where I would go ask Andrei who runs our platform and be like, can you go look this up?

But instead, I just said, can you go into post?

I just went to work and I said, can you go into post hog and just find all this stuff?

And it said, OK, total chat with Claude Button Cooks 4000.

That's actually freaking crazy.

Oh, my God.

We should get money.

We should referral referral fees, baby.

What about chat with chat?

You be T.

What about?

Copy for agent and so this is cool because we we were in a rush since we started this morning and we didn't have any MCP set up.

What we just did was we connected Chrome and then is logged in on Chrome in post hoc.

So just browse to the thing that got the things.

So that's very handy.

Like M.P.P.

just make sure you connect Chrome.

That's a very good one to add already.

You can also do that with the normal, but it's very good at browsing and figuring things out, especially now it doesn't stop as quickly, which is really, really handy.

So anything you can do in a browser, you can now use co-work for to like use longer running tasks and kick off things and you can use multiple tabs as well.

So you can have five tabs being controlled by Claude and running, which is great.

Totally.

Totally.

And it sounds like this is down for people.

So come hang out on the street.

It's down for me as well, but for that it's working.

So I'm the only one that's open for.

So we've got a monopoly here on an anthropic co-work content.

So if you're here and you have stuff you want me to try, just let me know.

I'm happy to throw it in the chat and make sure I have something fun to do.

Make sure that you use every, you read every because every is the only subscription that you need to stay at the edge of AI.

Every dot T O we've got these vibe checks.

When new models come out, we get them beforehand.

We had this several hours ago.

We knew it was coming since last week.

And we always have all the up to the minute stuff that you might need.

We also have a bundle of apps that we make.

We have an app like the one that Kieran makes called Cora, which is an assistant, an email assistant.

We have one called sparkle that helps you organize your files.

We've got spiral, which helps you write.

And we've also got monologue, which is a speech to text app, which I will show you shortly.

And let's actually go back to let's actually go back to the Claude demo real quick.

And Kieran, if you see anyone asking questions, just yeah, yeah, there's one good question from Hunter.

And he says, how good is it at research?

Like one of the things I love Claude's normal for is the deep research.

Like, does that exist?

So maybe we can see if it can do deep research on something.

Yeah, let me know.

Let me know if you have a research query you want me to try, but like I can show you, you know, actually, you know what, I'm going to share a different screen.

Hold on.

Plus share screen.

Okay.

I'm figuring out my live stream setup.

This is the first time that we've really done a live stream for a vibe check.

So now you should be able to see my screen again.

So for research, like, okay, it depends on what you mean by research, right?

Because this is a research query.

Can you connect to post hog and tell me for the agent native guide that we post last week, how many people clicked the chat?

Like that is research.

And it does give me actually like a really good answer, which this is so interesting.

Okay.

But like another form of research that we talked about is, okay, analyze my competitors.

This is specifically analyze our competitors for the every consulting business.

And I'm going to say open and proof.

Proof is the agent native markdown editor that I built over the weekend.

Can you believe I just said that?

And so this is a research document that Claude co-work put together, which, you know, it's not like, it's not the medias thing I've ever seen.

Let's see.

I think this is not bad.

I'm not noticing like a super significant difference between this and like what a normal quad would pull out, but I can see the research itself is more is much more extensive than normal Claude would do.

And let me just actually throw this into normal.

You can see also, so if you do deep research, the research agents in chat, that's pretty extensive normally, but here you can see more.

So yeah, I don't know, maybe that is also available in that version.

We're still figuring out what everything is that is available, but it's very close to what you can do in Claude code.

So the kind of fusion of chats and Claude codes is co-work.

Yeah.

Yeah.

This is very like you can see that they're calling these tasks as opposed to chats.

So it's supposed to be, I think here's, here's a good way to think about it.

A good way to think about it is if you're a non-technical person, you are used to a world where you send a prompt and then you get a response within a couple of minutes.

And once you send a prompt or a chat, you can't do anything else with that AI.

You have to like move on to something else.

This is built for working with your AIs in an async way.

So everything is set up like the idea of a task, the idea of having a queue.

This is all set up so that you can say, go do something and then not think about it for a while and then come back, which is very different from Claude where the normal Claude app you're, you're kind of, you're, you're trying to, you're trying to get an answer pretty quick.

And I think that's the best mental shift.

I think the real question that I have is, is this deserving of its own tab?

For one, one reason it might be is there's a difference between like how you might treat one of these versus one of these.

Like these are more throwaway.

These are probably like bigger chunks of work, but honestly, it's like kind of confusing.

I would rather just, I think that they, I would rather just have it all in one tab and then have it do different levels of research and thinking and, and async based on the task and maybe based on, you know, a setting like saying like really fucking think about this.

I don't know.

What do you think you're in?

How would you solve that?

Yeah.

I mean, for me, it's also confusing.

It's like, oh great.

There's another tab and I have to like first think where to go, but I do get it because I've seen this transition as engineers as an engineer.

Like we had the like copy paste into chat GPT obviously.

And then like that evolved into cursor, like more agentic, which evolved to like, I don't look at code anymore.

And I think there will be a similar transition for people that do research or co-work.

Like maybe now people are used to go into Chrome and like seeing what's going on, what's happening to towards more of like, I'm just going to let it rip and do its thing.

And then after it gets back, I'm going to review whatever the output is rather than understanding every single step all the way.

And then you're like clearly already there.

That's how you're thinking.

But I do understand if you're not there, if you're more like in the chat thing, where it's like, oh, do this now.

Why don't you look at this?

Like if you have this conversation, it's maybe more chats and co-work is more you handle the task to your agent and your agent comes back and you review the work and you can follow up, but you can give extra directions.

But I do understand to introduce a new tab because there you need to shift your mind to do that.

And we're doing that.

But I understand lots of people in the world, especially that are not coders still have to make that transition where you just hand off something and then let it do stuff for 30 minutes or an hour and then come back and review that.

So I do understand why they want to separate it, even though it's all the same technology because chat, code and co-work, it's all the same model.

And it's very similar, like harnessing around it.

It is philosophically or how you use it, maybe a little bit different.

So I guess that's why they did that.

Yeah, it's interesting too, because when we did this original vibe check, when we got it a couple hours ago, we had me and Kieran and a couple other people on the phone from internally at every and we were demoing it together.

And their initial reaction was like, I don't know how this is different.

Is this even that useful compared to regular cloud or cloud code?

Because a lot of them are just using cloud code directly.

And I think that was a really interesting thing for me where you're not going to actually realize how useful this is until you get your hands on it.

There's probably going to be a learning curve on it where if you're a non-technical user who is not used to the idea that you can just hand off your work and then come back, it's probably going to take a while to actually figure that out and get used to this as a UX paradigm.

So maybe there's some benefit then to having it be a separate tab so people can basically realize, oh yeah, this is different and I should treat this differently.

It's a real adjustment.

Yeah.

Yeah.

Yeah.

And that's...

So if you want to learn about that adjustment, we're writing about that for coding, but you could really apply whatever is happening to coding probably for co-work as well, like how that shift happens, how that goes.

So yeah, like we thought about, we wrote about some of these things and I created a plugin around this idea.

So what I will do in the coming days as well is like see if the pattern or the paradigm of compound engineering, if that applies to co-work.

And I get that working in co-work because I would be very curious to expand that and see if it works inside here as well.

Anthony, I see that you're from Anthropic.

Do you want to come on the stream?

I'm going to send you a link.

I would love to hear what you have to say about this and anything that we should try or anything that's missing.

Here, give me a sec.

Copy.

Let's see.

All right.

I sent you a stream link.

Come on, feel free if you're not feeling it, that's also totally fine.

Yeah, he says it looks or is closer to closed codes than chats.

And it feels like that because all the tools like the Ask User Question tool, stuff like that have a UI, which is nice.

So you can ask it to say, "Hey, can you interview me, ask me a few questions?"

And there's like a nice UI with multiple choice and stuff like that.

So yeah, it's really cool that you wipe out.

It is really cool.

Okay.

So let's keep looking at this.

It's still working.

One of the things I noticed is when it was erroring, it gave an error from Cloud Code, like the internal error message is Cloud Code.

So it seems like it really is just like a UI wrapper on Cloud Code rather than a different agent harness or maybe like a Cloud SDK.

Anthony, if we're wrong about that or anybody else from Anthropic who's listening, I'd be very curious for your thumbs up or thumbs down on that.

But that's an interesting design choice not to use just like actual Cloud Code.

I assume that's because it's already in the app, so it's pretty easy.

You don't need to use the SDK, but it's a really interesting thing to see.

One thing that I want to show people in case you have not been watching everything that we're doing at Every and if you haven't been, I don't know why you would not.

I don't know what's wrong with you.

But one thing that's really cool that we're thinking a lot about is Agent Native Architectures.

And Agent Native Architecture, this app is a really good example.

This new Cloud Co-Work app is a really good example of Agent Native Architectures where we think about Agent Native Architectures as sort of like Cloud Code and a trench coat, which means at the bottom of the app, instead of having software, you have software that works by deterministic rules, you have an agent.

And the agent is wired up to the UI of the app.

And so when you click a button, it is actually just going to the agent with a prompt.

And I think this is a new way of building applications that we've been working on internally at Every.

If you're interested in that, I highly recommend that you look at this guide.

We'll put a link in the chat.

But this guide goes through how to use or how to build Agent Native Architectures.

It's pretty cool.

And it makes you build stuff.

I built this.

This is a Markdown Editor that I built with Cloud Code over the weekend.

So in the last couple of days, I built this whole thing.

It helps me track.

We use it internally.

It's called Proof.

It helps me track.

When I get a plan from Cloud, it helps me track, okay, what things have I approved?

So you can see I'm approving things here.

So I can track what have I approved?

What have I looked at?

What's done?

What's not done?

And yeah, there's a lot of cool stuff here.

I'm going to stop laughing about Agent Native and go back to Cloud.

Kieran, anything you want to add here?

Really what I'm curious for is like as a Power user, can I load my own plugins and stuff like that?

And there were questions about can we get you to custom MCPs?

I think all the MCPs you can do.

And also this app has access to your machine.

So it can use Apple Script to load things on your machine, which is really cool.

Yeah, and yeah, I'm really curious for how, where does it go?

Like clearly it's trying to get cold codes to the normal user, but I think as a Power user, I would use this as well, because in the morning I start up cold codes to make a daily planning.

Like, well, what am I going to work on for the day?

But it feels, it's probably nicer to do in an app.

And also if this translates to mobile, this is super powerful because you can do more powerful work on your phone that's not necessarily code related.

So yeah, we need to experiment, but there are lots of interesting things.

I'm very curious as a Power user, even though it is the same technology, maybe it's a new way to use it, which is interesting.

Yeah.

So this is my calendar audit that I asked it to do.

So I asked it to audit my calendar and compare it to my goals.

I reviewed your entire month of calendar activity.

So this is something that regular Cloud probably would not do.

I have a lot of meetings and standups.

So that's an interesting one.

I actually don't go to a lot of these, so that's probably not fair.

And I also have a lot of one-on-ones.

I have a lot of podcasts scheduled, which I'm starting to get rid of.

It actually did a pretty good job.

Content media, health, non-negotiable, blah, blah, blah, blah.

Many days have 10 to 15 plus scheduled events.

That sounds probably right.

This is interesting.

It said, "What are your top priorities?"

I would expect Cloud to know this.

I wonder if it has access to all my memories yet, because Cloud definitely knows what my priorities are.

But anyway, this is pretty cool.

I like this.

Let's see if it did.

Oh, we did.

We got the text on me.

It feels like it's slowly lazy loading all the conversation history, so it doesn't...

This isn't happening.

This is already done.

It just didn't load it.

I feel like a lot of the affordances here, they haven't built the statuses yet, so it's easy to see.

In the code tab, for example, I could pretty easily see usually what I've merged and what's waiting for me and stuff.

But this is just an unorganized list, I guess, by recency.

There's no visual differentiation, which is interesting.

Hello, Kate.

Our editor-in-chief, Kate, is just off camera.

Kate, things are going well.

We've got 2,300 people here.

So looking at Cloud code together.

That's so exciting.

Yeah.

Oh, you want...

Okay.

Let me just...

Yeah, maybe I should try that.

If anyone from Anthropic wants to come on the stream and talk to us, I can see you commenting in the chat.

I'll send you a link to StreamYard.

Just say, "Yes, I would like to come on the stream and chat."

We're very, very friendly, and I think a lot of people would love to hear from you if you're already here.

I will update the app.

This is actually important.

I have a beta build right now, so this is something that was not...

I haven't updated my app, and I'm a little afraid to do it on a live stream.

Do you have it in your app?

I'm curious.

I'm trying to get it working.

It was down for a while here.

It looks like some...

It's back up again.

Cool.

Anybody have other questions or things they want me to try?

I'm taking requests, so ask any interesting queries.

Most interesting query we'll put in every when we do our vibe check.

Let's see.

I wonder if I could use this to code.

I'm kind of like...

Let's see.

Oh, it did our audit of the Avery Agent Native guide.

Can you see if it has artifacts as well?

It does.

It's similar, maybe?

Okay.

It does have...

Well, it didn't do this one in an artifact, but we do have artifacts in another place.

Let me just find it.

I do the effects that the context is clearly spelled out on the right.

Yeah.

That is nice.

Yeah, context is here.

I saw the artifacts tab somewhere.

Yeah, it's just like a friendlier version of Cloud Code to me.

Yeah, mine is working as well.

Can you find my every proof repo in Cascade Projects?

Basically, I want you to do a summary of the new feature, the provenance, the new feature provenance tracking that I've been building in every proof.

And write it up in a nice HTML file artifact that I can send to Kieran to explain to him how the new provenance is going to work.

I think this is a combination of something that is kind of...

It's Dev work related, but it's probably not something I would ask Cloud Code to do.

I don't have access to your Mac's file system in this Linux VM environment.

Interesting.

That's interesting because it definitely does have access.

Let's see.

One of the things that gets confusing about this, I guess, is when it's running on your computer versus when it's not.

I think it's sort of unintuitive to the average person probably that when you're using it in chat, it is all online.

And when you're using it in here, it's actually on your own computer.

I'm very curious how they thought about making that clear from a UX perspective.

And if anyone is from Anthropex on this stream, why does it think that it can't access my Mac's file system?

Maybe I have to add that folder specifically.

Oh, yeah, that's what it is.

That's so interesting.

I just wanted to YOLO, give it YOLO access to my file system, to be honest with you.

Look at all these projects, by the way.

This is how you know I have a problem.

These are all vibe-coded projects, basically.

Let's see.

Every proof.

You know what?

It's this one.

Okay.

Always allow.

All right.

And now, the nice thing about monologue.

So monologue is one of our apps at Every.

There's a shortcut for this.

I can just click it and then repaste.

Cool.

But, yeah, what I really want, I just wanted to access my whole computer.

That's interesting.

It has that file cleaning prompt.

I wonder how that works if it can't access...

Yeah, I'm testing it now as well.

I'm trying to see if I can use the skills I already have.

Oh, interesting.

So I said organize and hide out my downloads and then it seems like it figured out...

This is so agent-native.

It figured out how to select...

It's as if I selected that folder in the UI.

Because I specifically asked for it.

That's cool.

I think that's a really smart affordance.

I wish it had gotten activated here, too.

Ideally, it knows that I'm trying to access a folder in Cascade Projects and it is as if I clicked this.

Hmm.

Are you sure?

It's the natural...

Let's see if this is actually working.

Felix, are you joining?

Amazing.

Let me just find you on the X app, X the everything app.

If you can share my screen, I'm going to show a short thing while you do that.

This is helpful.

All right.

I'm going to remove...

There you go.

You're off to the races.

I was trying this out.

Help me generate a VST plugin, ask me user questions.

I found a little...

I found some things.

Basically the ask user question I love because it's this UI.

It runs you through and you can hit 12345, which is very nice.

The weird thing is I didn't answer it and it started automatically skipping this.

Maybe it's fixed now.

In the other one, it started automatically...

Oh, yeah, here, skipping.

There we go.

See?

If your mouse is not on here, it just thinks, "Oh, this user is not here, so we're going to skip this altogether," which is very confusing.

But also I love it because I'm a dangerously skipped permissions person and I understand.

But it's weird because if you're here, scroll all the way up, it will skip to the next.

It's a little bit strange here.

But the cool part is here, I can say three and it will go and continue.

I like that it keeps going and it's set to keep going and finish.

The skip UI here is a little bit weird, but let's say multi-tab delay.

You can see it's working with my skill or skills juice.

Oh, yeah, it is mine.

Happy Sharp Hopper is just the local place where this is happening.

Say this...

This is an interface that never existed before, which is cool.

It's a little bit weird because it's inline here, but in reality, you're answering.

I'm sure it's sending requests.

So the skipping part is very confusing.

I don't know why it's skipping now, but I would rather say maybe when I start the session, what kind of session it is, like if it's a YOLO, let's go session, or where it pings me and very clearly in the co-work tab says, "Hey, you need to answer a question here.

I need your attention."

Because there's something to be said to both and now it's somewhere in the middle where it's not super clear.

So I'd rather have it yell at me and say, "Yo, I need your input on something."

And I don't want to give input on creating or using things, but if it will change the direction of what this will be with the Ask User question probably that is handy to have.

So far, this.

Interesting.

I have a...

Since we have...

It seems like there are some anthropic people on here.

I do have a feeling about Ask User question.

I'm curious what you think here.

There's a limit to how many characters it displays, and then it just goes over and hides the rest of my answer, and that just annoys the shit out of me.

Do you know what I'm talking about?

Yeah, I know.

It needs to be a little bit more flexible.

Also, I want like why not 20 options?

Why is five the maximum or something?

Sometimes you just have 20 that you need to...

I get it, but also...

Stop questions, go build.

So that is nice.

Just make it now.

It did not really...

like it's still doing stuff there, but here...

I mean, it's a little bit wonky still.

But I love the Ask User question flow.

It's very useful.

Okay, so it does it here, and you see the to-do write, which is here on the right.

I was distracted.

What plugin are you building here?

Can you back me up?

I just wanted to think about it.

Yeah.

I have a skill called the Juice skill, which knows everything about VST development.

And I asked the KU, "Help me brainstorm a VST plugin."

And we're doing a delay.

It's an audio effect.

So digital sound processing that you use in your music making.

And I'm making a delay now, and it's building the delay.

And normally the building of the delay is great for, but sometimes you want to brainstorm.

You don't want to build.

And that's why I like co-work, because I just want to brainstorm a little bit.

And the cool part is it has these skills.

So yeah.

I want to interrupt you really quick here, because we have a member of the team from Anthropic here on the stream.

Felix, welcome.

Hi, friends.

How are you?

Hey.

And how are you?

I've never met before.

Tell me about you.

What do you do at Anthropic?

How are you involved in this?

How am I involved in this?

I've been in Anthropic for a little bit, but this is the product that my team has built here.

We've sprinted at this for the last week and a half.

What we're trying to do here-- The last week and a half?

That's it?

Go on.

To be clear, I think many people have had the idea that something like Cloud Code for non-coding work would be helpful and useful to people.

And fundamentally, what we're going to do here is we do want to help people out with their work, whether that's a personal thing or a corporate thing.

And we've had a different number of prototypes, in particular before Christmas.

But I think over the holidays, one thing we have seen-- I'm sure many people have seen this-- is that an increasing number of people is using Cloud Code for almost anything, just like we are.

We're automating our entire lives with Cloud Code.

So we're thinking, what is this small, early thing that we can try out and shift to people and iterate with them together to really figure out what is the right user experience, what is the right thing we need to build?

And this is it.

This is the research preview very early alpha.

A lot of rough edges, as you've already seen.

There's a lot of things about it that I think we're going to improve very quickly.

But this is our attempt to build in the open and work together with people out there.

I love it.

Tell us about some of the design decisions you made.

An early one, for example, is there's a third tab instead of maybe adding a co-work mode into the chat tab.

How did you think about-- and what was the process to come to the design that you have currently for how the product works?

It's a great question.

So I think one belief I have is that the current user interface that you see across a gen-take application is not just an enthropic, but across the industry is probably going to change pretty dramatically in about a year or two.

Right now we have these hyper-specialized individual input fields, and we have a lot of custom scaffolding around the specific tasks that you're going to do.

But as we see the intelligence of models improve, and as we also maybe holistically as an industry figure out a little bit of the generalization problem, I expect that we're actually going to see a smaller number of interfaces for a wider range of use cases.

So now what we're doing is the reason we broke it out is because we want to be pretty transparent that this separate thing is a construction site.

That we're letting you into our kitchen.

We want to work together with you.

We want to ship almost every single day some new features, some bug fixes, try out some things.

So this separate tab is fairly experimental.

You could say on the frontier or the bleeding edge, but it's just a little bit less polished and a little faster pace.

And that's one of the main reasons for a separate tab.

There are some technical reasons too.

I could tell you one of them is that currently this is running on your computer, so your chats are local, they're not shared with other devices.

We're being a little bit more aggressive in how many agenda capabilities we give cloud.

Those are the main reasons.

How did you think about, because I feel like that's such a huge UX hurdle to get over.

How did you think about letting people know, hey, this is actually running on your computer versus chat, which is in the same application as not?

Yeah, that seems so hard.

Yeah.

I think the dream that I have, and I'm sure many people have this dream, the dream that I have is that it doesn't really matter.

Like where your code runs, it should be technical implementation detail and it should matter to people as much as when you visit the newyorktimes.com, like is it using web sockets or not?

And it's like, who cares?

I think for us right now, it's an opportunity to move a little bit faster and to ship a little bit quicker and also like work a little bit closer with the people for whom we're building this.

I have the strong belief that it's very hard to figure out a great product in isolation by yourself.

You sort of like go up into a cave and you work on something for a year and eventually comes out.

I think it's really hard to build a good product that way.

And I often like to remind people that like even the first iPhone was missing a bunch of things that we sort of consider to be table stakes.

So yeah, I think it's a pretty big hurdle, but we're okay with that for now because we do want people who are signing up for this ride to sign up for it fairly intentionally.

I think that's a really interesting pattern is like let's ship really fast and we'll ship it as a new thing in the app that maybe fewer people will click on so that we can get it out in the open and start iterating together rather than like try to make it perfect, especially in this world where it says, you said you were working on this version for week and a half, which is kind of insane.

Kieran, do you have any questions?

Yeah, I'm curious.

Like clearly this is the version that's out now, but like what is the version like in your head?

It's like, what are the like, where do you want to go next?

Or like, what are the things you're dreaming about?

You used the word dream.

What are those things where you want to want to go?

Because I'm sure everyone on the team had like wild IDs and then we're like, no, we need to ship Monday.

So let's just like, what are, if you can share any of those, we'd love to hear those.

I love that question so much because I think I actually have the same question for the two of you, which is where do you want this to go?

What do you want to do?

I've already heard you say you kind of want to give it to an access to the entire computer, the multiple choice thing where like, actually, can we like shift around a little bit and how we want to want to do this?

I think right now I am much more in a mode of, okay, let's see what people think and then try out a billion things.

Some of them will probably be the wrong thing.

Some of them will be the right thing.

But I think it's much more interesting to me what people want to do with this, rather than like, what's my own personal dream or vision?

In the things that I've sort of built in the past, this was always, this was always the thing that happened, right?

You have like an idea of how people will use the thing that you built.

They actually find a use for it in all these other ways, and then you lean into that.

So I'm really hoping that we can learn a lot about what do people want, what do people not want, what do they like, what do they dislike?

I'm sure people will dislike a few things about this, and then we like adjust and iterate on it.

That's a really cool thing about GoFork here.

Yeah.

So Boris is very good in building Cloud Code in a way that people can figure out what they want.

Is there a way, like, do you use that strategy in a way as well, where you give some building blocks or things for us?

Like, for example, can I include my own plugins or skills?

Or like, is there a way for people to experiment inside GoFork as well in that, like, maybe the non-coding way?

Or is it really like, this is the product?

That's what it is.

Because there's a cool balance between how Cloud Code works and people that use it, because it's super hackable.

Is there a similar philosophy in GoFork as well for non-coders?

Yeah, like, very composable, right?

The first thing you said about Boris being very good at steering Cloud Code in this direction of shipping early and then iterating on it and seeing how people use it, it's really funny that you mentioned that.

Because I think one of the reasons we've shipped today, maybe shipped a little earlier, was because Boris pushed me and was like, "Hey, you should probably show this to people.

See what they do."

And on the composable piece, I think the thing that I found most impressive in my own work over the last couple of weeks and maybe sort of the last two months is that I'm really leaning into skills.

So instead of like previously writing MCP tools, and like this very specific harness that is like very tailored towards just Cloud, I instead just write skills.

I still write a binary and then I describe in a skill how to do something.

I'm like, "What's a good example?"

I'm working on like a marathon training plan for myself and I wrote a little binary that fetches all my athletic activities from various pages.

But then I just write in markdown in a skill file, "Hey, Cloud, if you want to make a training plan, like please follow the following guidelines."

We do automatically load any skill you have installed in Cloud AI into GoFork.

And I think that's probably going to be increasingly, especially as well as it's larger and especially with O plus four five, it is so good at following skills.

So skills is probably the primary hackable surface that I'm exploiting right now.

That's great.

One thing you said earlier in the conversation is you think that there's going to be fewer like UI services.

Does that mean that like over time there'll be fewer UI services?

Does that mean because there's a lot of debate over the last couple of years about is chat the final form factor for AI and everyone's like, "No, we need more UI."

Are you putting your stake in the ground as natural language actually is here to stay and we're going to have fewer UI services where you just talk to an agent, maybe an agent orchestrator that goes and talks to a bunch of other agents and that's the kind of form factor you're pushing towards.

So it looks a little bit like how Cloud Code does today.

Yeah, I think this is still very heavily debated and there's certainly no anthropic viewpoint.

I'm not even sure that there's a viewpoint that my fairly small team would like holistically agree with.

I think people have very different visions about how will people interact with AI and models in the future.

If you ask me very personally, I think I believe two things.

One is that the chat input and it's very as forums, not just for models, but in general.

Like the idea of this text box and you put into the text box where you want.

If you generalize it enough to say even google.com or the address bar in Chrome is like, "I want something input box."

I think that is going to stick around for much longer than we all think.

This first thing I think, I think we will continue to have something that looks like a search, "I want something box."

The second question is like how many separate boxes do you have?

Like do you have one box for code?

Do you have another box for maybe like a personal attainment?

Do you have another box for healthcare related concerns?

I'm not sure we're going to have too many boxes of those.

There too maybe I would go back to Google.

I think I sort of remember the early 2000s where you did different search box for every single Google sub product.

Increasingly, you just type what you wanted to your Chrome search bar and you don't actually go to a sub page of something.

I'm in the mode right now of looking specifically for a shopping thing so I go to Google shopping.

I would be surprised if we don't see a similar generalization that is smarter about figuring out what you want to do in the future.

We might still have different interfaces where it sort of splits out.

I understand that you're trying to do X, therefore I'm going to show you UI for X, but the entrance point.

I think the interesting counterpoint to that is something like Microsoft Excel, which I think it also has some similarities to the way that just generally AI works.

It's this general purpose product.

It's super simple to get started.

You can make things endlessly complex with Excel and then Excel sort of spawned the B2B sass wave.

You probably don't get B2B sass with that Excel.

I think there's also the other argument that you have these sort of really general tools and then people find power workflows within them that then get split out.

Yeah.

Yeah.

I think Excel is such a beautiful example of so many things because it's like for many developers, something that sort of exists a little bit on the periphery.

I've often heard the analogies between how many daily active users Excel has versus how many developers even exist on the planet.

It's an interesting number.

I think the thing that I find interesting about Excel and the commitment it has from its power users is that those power users are not too interested in marginal productivity gains or marginal UI or UX gains over deep familiarity with the product.

I think that's interesting.

I think there's a lesson there in some shape or form.

I think I've actually seen that across like various other surfaces where you as a developer sometimes look at someone's workflow and you say, "Oh, I can make this workflow slightly better for you if I make you a specific use case tool over here on the side."

Then people sort of fail to adopt that thing because they're actually more comfortable doing specific things within their product.

As an example, I think that's a lesson that I was previously at Slack for many years.

There's a lesson that I've learned there over and over again is that you can make these separate surfaces that you think might serve people's use cases much better, but they will continue to just do it in chat.

That's a really, really good lesson.

I love that.

Speaking of that, I think today is for the non-developers, but I feel like there's a lot of developers who are watching this right now.

You're someone who's...

You built this, so you're deep into how to build agent-native applications.

This is something that we've been thinking about and talking about a lot at every...

We just published a guide called Agent-Native Architectures.

We've been thinking about what are the core principles of agent-native apps.

I'm really curious if these resonate with you, if you think they're wrong or if there are things that you would add that are part of how you guys at Anthropic think about building agents.

An example is Parity.

One of the things that we think about when we build agents internally at every is whatever the user can do through the UI, the agent should be able to do.

I see that a little bit...

That's basically how Cloud Code works, but I see that a little bit in what you built with Co-Work where, for example, if you didn't pick the file picker, it'll automatically determine that you are asking it to pick a particular folder and it will do that for you without you having to touch the UI.

That would be an example of Parity.

Another one is Granularity, which is basically tools should be mostly at a lower level than features and the features should live in the prompt or the skill so that you can combine tools in new ways that you didn't predict previously.

And then that allows for the third one, which is Composability, which is you can combine those new ways and you get the fourth one, which is Emergent Capabilities.

People are just doing it for stuff that you didn't expect and you see the latent demand and then you build for that.

This is essentially, I think, a lot of my summary of how Cloud Code works.

I'm curious of how this sounds to you and if you think that we're missing anything or there are any things that you've learned from doing this in production at a huge scale that could make people better at building these kinds of applications.

I think this really resonates with me.

I think one thing that's hidden in Emergent Capabilities is the inability, I think, especially individuals in silo teams have to predict how an agent actually ends up being super useful if you give it fairly primitive tools.

I think pushing down tools into a general space is very powerful.

The more composable they become, the more generalizable the tool is, the more you will benefit from improvements on model intelligence.

I think for many developers that I've been talking to in the past, it seems like the rate at which model intelligence and model's ability to call tools effectively improves is actually much faster than your ability to maybe churn out additional tools and educate users on them.

I think if you take a step back and you think, "How can I build a very generalizable tool?"

You have a much better chance to build something that can adapt to new use cases.

I think that resonates with me quite a bit.

What about the tradeoffs?

I've been talking to Kieran about the tradeoffs and tools.

Kieran, do you want to talk about what you notice in Quora and what you're thinking about?

Yeah, so I think putting things in a prompt is great and then having the tools.

We need to now suddenly create tools that then read skills or something like that.

We have to invent this meta layer.

Skills is just in time prompt injection.

We need to create that thing.

Now everyone that's building stuff, unless you use Claude codes or the Claude SDK, it's all built.

It's this thing.

Now there's this struggle of, "Oh, but tools are that you can describe stuff in a tool."

Or you create a tool that then wraps around it and then calls something else.

There's this friction there.

It is great to make things composable.

If originally you create, for example, five tool calls, want to search email, read email, this and this and this.

But you can also say, "No, we do just do an execute tool call and we create skills that can do those things."

Or an MCP or some obstruction there.

There's this change happening and obviously this is like the Claude SDK is a very good push for that.

But I feel friction there.

I'm sure you felt that friction too.

So maybe you have some best practices for people that are stuck in the old fashioned AI world and need to go to the more agent native things that you learned or that you've noticed because you've implemented on top of, I assume Claude SDK maybe or some variant like there is.

So you use that and you implement things on top.

So I'm very curious if you learned anything there.

I'm not sure that I have any wisdom from the mountain that is going to be more valuable than yours.

But I think what you're saying that resonates with me is that you need to make a call.

Which part of the outputs do you want to be non-feministic and where are you comfortable relying on model intelligence?

And every single time you do rely on model intelligence, if you pick a cheaper model or a dumber model, then those parts also go down in quality.

And I like to break up my workflows into the non-deterministic and the repeatable parts.

I think the more repeatable something is and the more easily I can say this will never change and if it gets smarter, I'm not going to benefit here at all.

I think that's a place where it might make sense to write a tool.

And in a sense, we're already doing that.

We're not implementing...

You could give Claude a very generalizable write assembly code tool.

We could just call GCC and figure out whatever you want.

But we don't.

We give it...

We give it like a huge...

Yes!

Right?

Because...

That's dense ideals.

That's the most granular you can get.

Yeah.

But I will say that I think when I talk to developers out there, depending on how sci-fi you are, I think even that assumption is a little bit...

I wouldn't bet too much money on it.

But assumption is certainly under attack.

The idea of should you give Claude any tool at all or should it just be like Claude hears memories start writing ones and zeros, go wild.

It's an interesting area.

It's hard for me to know right now.

No one knows.

But you learn stuff.

You created skills for exactly this reason because you needed more than just a slash command and a sub-agent.

We need to ClaudeMD to be better.

But I guess that's why skills were created and clearly that's working well.

I resonate with you saying skills are amazing.

This is also like I'm creating skills every day and I love them.

So clearly there's something there.

But when do you not have it be a skill?

It's very interesting to me.

I think this is such a fun conversation.

Someone you should actually talk to at some point is Barry.

Because Barry is the one who is at least inside the company.

Our skills person is the person who essentially came up with skills.

And for us fundamentally skills for a little bit of a byproduct of the same tension that you're describing.

So what we wanted to do is we wanted to make a very easy way for people inside the company to get dashboards.

And we use one of the popular data providers where we keep a lot of our data.

And we were trying to figure out, okay, do we build really specific tools that fetch that data and then compress it down into like a specific format?

The first couple of dashboards Claude and the building looked a little, you know, this was before 4.5.

The dashboards were not ideal.

Every third or fourth dashboard it generated was like a little lackluster.

So we did think about, okay, do we like super parameterize it and basically build like a fixed dashboard that you, Claude, then only plugs in your data into.

But in that process while building that we sort of discovered, hey, if you just tell Claude how to effectively query this data source that it can use SQL and that it please follows the following design guidelines for making dashboards, suddenly you get something very, very good and you get it very good every single time.

And then you also give people, and this is the emerging capabilities part, then you also give people the opportunity to say, hey, Claude, I understand that you're following these principles for dashboards, but I also want, I don't know, different chart type or I want to combine it with other data.

And that's then where things really open up.

Right.

Hmm.

That is really interesting.

I feel like the one way to talk about why you might want to scale instead of just having it have GCC and just everything is just in time is it's like about sharing something repeatable with other people that you can talk about and there is something actually that not everything should be just in time because you want to do the same thing over time with a group of people.

And that's that's kind of a skill, I guess.

Yeah.

Yeah.

And that's sort of how we operate too as humans, right?

Like when I joined the company, someone tells me how to book a flight, like, yeah, yeah, yeah, yeah, yeah, yeah.

How do you get a room?

I think a lot of us sort of operate even as humans on a long list of markdown files.

Let's start with it.

Felix, I want to give you an option.

You've been very generous with your time.

I want to give you an option to hop off if you want.

We would love to keep chatting.

We have endless questions, but I'm sure you have a lot going on.

Do you need to go or do you want to keep chatting?

I think this is a good time for me to bounce, but I'm not going to go before both of you give me like one thing you would like us to change.

I mean, my easy one is just you'll have access to my whole computer.

Okay.

Okay.

So, I want to make it easier for me to know whether it's working on my computer or working in the cloud on a chat and make it easy for me to use it on mobile.

Okay.

Yeah.

Plus one on the mobile, but my favorite thing would be the ability to add my plugins.

So just my marketplace with plugins.

I just want to hook it up to GitHub.

Fair enough.

Yeah.

Yeah.

So, I'm like adding things in the app and then copying it there.

Probably I can just copy it somewhere, but just native support for a marketplace and then adding it and syncing it.

That would be absolutely great.

Thank you.

I appreciate both of those quite a bit.

We're going to take those back, going to tell the team about it.

And for everyone else on the chat, find us on the internet, send us what you think.

We're quite interested in hearing from people and adjusting our roadmap.

Thank you so much, Felix.

Thanks for building this.

Thanks for joining.

Thank you.

Have a good one.

All right.

That was awesome.

So cool.

Thank you.

Yeah.

And we have so many people on this stream.

There's almost 10,000 people here.

Oh my God.

If you're joining us for the first time, we just had Felix on.

Felix is a member of the technical staff at an anthropic and he was talking to us about cloud co-work.

If you are looking at this stream, then you probably know what cloud co-work is, but I will share my screen and show you again in case you're wondering.

It is a new version of cloud.

That's sort of like cloud code for non-technical people.

It looks a little bit like this.

We've been testing it at every, we're the only subscription you need to stay at the edge of AI, every.to.

We get access to this stuff before it comes out and we do vibe checks like this.

We do them live.

We also write them on every.to.

So we got this earlier today.

We were just testing it out.

Here's an example of a task I gave it.

You'll notice it looks a lot like normal cloud, like the normal cloud chat.

The differences are a bit subtle, but I think that they, it does make a big difference.

So instead of a chat, you have tasks.

When you look at the, you know, this for this query, or maybe like, let me find a better example of this.

Like this query, for example.

You'll see that the code ran for a really long time.

If I asked the same query, I wanted to go to our every agent native guide and walk through it to a UX review.

Cloud would have stopped after a couple of turns and given me a pretty good answer, but this does a lot more research.

So because it's working on your computer, it's going to be able to work for a long time.

And I think that's sort of the key thing that you can take away from when you might want to use cowork and how it might work differently than regular cloud, which is for the first time if you're non-technical, you can ask your computer to do something and walk away for a while.

And then you can also ask it to do many things in parallel.

So this is an experience that if you're using cloud code, you have a lot with programming, but I think most non-technical people are still in the kind of like turn by turn era of using chat and just expecting a response almost immediately.

And this is much more of a built to be an async experience for non-coding tasks like data analysis or research or writing documents, like all that kind of stuff.

Like Felix said, they built this in a week and a half, which is crazy.

Which is the new normal, by the way.

So anyone who's like coming up with a PRD in two weeks, nope, you ship the whole thing a week and a half.

A hundred percent.

There are some rough edges here, but they're going to be improving them really quickly.

I think it's really cool.

The pattern that he shared that I really think is interesting is I was kind of asking why even add a new tab, like a co-work tab.

And he said, we essentially needed a playground to like mess around and do stuff that is a little bit less polished.

And so it's nice to have this extra tab, which is an interesting pattern in AI where now you can build so quickly.

We need more patterns for what to do with that.

Kieran, any reflections from our conversation with him or anything you're thinking about right now?

Yeah, I think it's like why use co-work over chat or code?

I think that is always my first question.

And I think if you're a non-technical user, just think of co-work as something that is chat.

Just try co-work as the new version of chats, the better version or a different flavor and just open it and do the same things you've been doing in chat.

But you see that it is different and you can do things.

Like one really, really important thing is in chat, if it is responding, you cannot send a new message.

When it does something, you're like, oh, wait, wait, that's wrong.

With co-work, you can cue a message.

And while it's working, say something new.

So just those tiny things are very, very handy.

So just try co-work instead of chat.

It has skills like you can generate documents, Excel sheets, PowerPoint presentations, PDFs.

It can do all those things.

So if you are applying to jobs, just upload everything and say, hey, can you rewrite my resume for this job?

And try it out, things you would manually do normally.

And also connect Chrome.

You can enable it.

Maybe you can show us how to do that in connections.

If you go into your settings and go into, I guess, is it connectors or is it -- Yeah.

It's in connectors.

Or -- Yeah, control Chrome.

So you can add that in there and then it will just be able to basically use Chrome on your computer, which is really cool.

One of the things I had to do that is totally new and interesting is -- do I have it?

I had it go through my Twitter feed, my X feed, and I asked it to just tell me what was hot right now.

What are people talking about?

And that's really cool.

That's ordinarily something that you would have had to pay a lot of money for an API for, and this can just do that without really a problem, which I love.

I love it.

Here it is.

And if you use Chrome and you're logged in on things in Chrome, it's already there.

So you don't need to log in again.

It just uses your Chrome itself.

Yeah.

Exactly.

And I use Atlas, so I had to log in all this stuff.

If you use Chrome, it's great.

So look, it just read my Twitter feed.

That's so cool.

There's so many possibilities if you're a writer or a marketer or anyone that does research, especially research on things that don't have APIs that you can now do without much trouble.

And to your point earlier, Kieran, when you're thinking about, okay, what would I even use this for?

I think that one of the things that we try to embody at every is we try to be really curious and know that if you're trying new technology for the first time, the first five things you do probably aren't going to work.

But there's something really fun about being curious right now because Felix, for example, the guy who made this doesn't even know how we're going to use it.

He needs people like us, anyone who's watching this stream, to mess around with it and figure out all the new interesting emergent ways that it could be used so that he can make the product better.

So it's the first time where the software developer is more like setting up a playground but has no idea how the playground is going to be used.

And the users are the ones that are being creative and figuring out things to do.

And so if you approach this with curiosity, it's like a huge opportunity over the next couple of weeks to figure out what this is for.

I think another important thing is people tend to have this thing that I like to call capability blindness, which is I tried this once before three months ago, it's never going to work with AI.

And the really interesting thing about AI is it changes every couple months.

I freaking, Opus 4.5 just totally changed everything.

Stuff that had never worked before started working now.

And so if there's something that you really want AI to do, like for me, that has always been I wanted to do copy edits.

Ooh, we should see if it can do copy edits.

I'm going to set that up.

So I've always wanted to do copy edits.

And every time something new comes out, I just try it because I know at some point in the next couple months, it's going to start working.

So I'm going to actually set that up.

I think that would be a really fun demo.

Kieran, do you want to talk about anything on your mind so that I can take a little bit of time and make the make get the copy edit set up?

Yes.

I'll share my here.

I'll just share a screen here.

So yeah, if you share my screen.

Oh, sorry.

Yeah.

Forgot that you were that I was your consumer screen.

Okay.

We're professionals, everyone.

Yes, obviously.

We started live streaming last week.

Give us some slack.

Yeah.

Cool.

Yeah.

So we talked about skills a lot.

And my thing like, what the hell is a skill?

Isn't that just a prompt?

Yeah, it's a prompt, but it's also more.

It's more like, yeah, and what can you do with it?

So this is the most hackable way for co work.

So if you want to personalize your co work experience, this is the way anthropic says so I asked what are all the skills I have and how can you use them?

So for example, these are document creation skills.

And it just learns how to create Excel sheets.

And these are some of my own.

I love Swiss design.

So I have like a Swiss design skill, Gemini image gen, where you can get nano banana images inside both codes.

I have a DHH Ruby style to roast my coat.

And yeah, all these things.

So I just create skills for everything.

So I have a 3d print skill where I needed to print some 3d things and I was like, I'm sure cold codes can do this.

And so I created the skill and Andy skills normally what I do is I go to chat and like say, can you generate a key deep research how Dan shipper writes.

So for example, if I like Dan's writing, I might do this and actually, I don't know that guy's kind of a blowhard.

I know.

So normally what I do is I enable deep research here and go hard and it run deep research runs for like an hour sometimes, which is great.

And then I say, can you create a skill for this?

So I'll just fake do this.

But then I create a skill for this and there is this thing in Claude in capabilities that you can enable, which is really cool that example skills.

So you go to capabilities example skills and there's a skill creator from anthropic.

If you enable this after you did deep research or anything, you can say create a skill out of this.

Well, obviously you can do that here as well.

So you can do research and co-work and create a skill out of this and it will be loaded inside here.

So for example, now, KU design with Swiss design, a very beautiful chair for me and create a STL so that I can 3D print this miniature four centimeters high.

So let's see.

So I do this and it's shoot them KU design.

Okay, so hopefully it's loading the two skills here.

You can see the context it pulled in the Swiss design skill and the 3D print skill.

So I like that that you can really clearly see this.

And what it does, the skill will just inject a prompt where it says, just do these things, make it look good.

Don't use inter or whatever.

This is the aesthetics.

So it's now doing things.

And there is also in skills, you can put like scripts, Python scripts, whatever script you want, binary scripts, anything you want to run.

So if you want something programmatic, you can encapsulate that into a script and put it in a skill.

So every time it runs, for example, you want to check if it's the shape or if it's following a certain like static or if it's actually linting well, you can encapsulate all that in the skill and trigger it as well.

So it's now doing this, which is really cool.

And the skill will create a STL file, which I can then 3D print.

So we'll see like a chair, obviously is maybe a little bit hard, but why not?

So this this is how you can create your version of co work with skills.

So you can capture and find the things you do and encapsulate your style and everything you do into a skill and then have it available here.

What is cool here is on the right side, you can see the STLs out the preview.

There's a preview.

Let's look at the preview.

Okay, so it's a little bit hacky still because or here the sidebar.

There we go.

Okay, this is the chair.

Beautiful.

So this SVG is not 3D.

Let's see.

Can we can we look at this?

No, we cannot look at this.

But yeah, we have STL.

Let's see if I can open this.

Open in bamboo studio.

I'll see if this looks any good.

I'll share my other screen.

Share screen and then we go to den.

So here is my Swiss design chair.

We need the skill here and go.

Oh, yeah.

So the actually the 3D skill is is all my machine, but I'll share it.

I'll push it to the to the interwebs.

And that was actually my request to yeah to Felix is like, can I automatically like pull these things into my my coding experience or like in co work that I if I push them online.

So yeah, I will share this but it's yeah, make your own things go wild and it's kind of funny to then print this all printed and take a picture later.

I love it.

So I if you've just joined one of the things we're talking about with Claude co work, I think that one of my bars for AGI is can it do copy edits in a Google Doc?

Like it's surprisingly hard to get these things to do that.

So what we have at every obviously publish every single day, we have a very high bar for the copy that we publish.

We want to make sure everything is like really, really clean and beautiful.

And so we have a skill that's in Claude that is our every proofreader skill.

And what I wanted what I wanted to do is see can Claude co work copy edit a Google Doc.

So this is the Google Doc.

This is an article we published last week by Katy Parrott, who's one of our writers, who's fantastic.

She's gonna be the one writing the vibe check on co work for later today.

So look out for that on every every dot to.

So I just said like, okay, I have an every proofreader file, I just downloaded this go file and gave it gave it to it in documents.

Can you go to this Google Doc and make edits as suggest changes?

And then this is actually really interesting.

So like, it's just hard for a us to do this because the answer go through the the the copy editor and just look for every for each rule and the copy editor, it has to go through every part of the document and find all the violations.

And that's just like really hard to do.

But you can see, I said, go do this.

This is not something that I don't think that the regular clock to really do this maybe Claude if he's in a Chrome could but other than that, it cannot do it, you can see it loaded the document, it's getting all the text, it's scrolled through the whole document.

And it's now clicking on it looks like it's clicking on suggesting let me see if I could actually find the Chrome tab that it has opened.

Yep.

So you can see that it's here's what it's doing.

It is to go it successfully got itself into suggesting mode.

And now what it looks like is it's searching using find and replace for errors that it found.

And we'll see I need to double click on editor and chief to select it and type the replacement.

Let me triple click near to select and manually make the edit.

This is so interesting.

I feel like watching this is like watching a video game.

I'm like, oh, yeah, come on, Claude.

Yeah.

It's really entertaining.

Yeah.

Yeah.

So Google Docs is like the final boss of stuff for AIs to use because it's just like so it's such ultimately such a simple application, but it's the way that they built it is so complicated.

It's like not actually real HTML.

It's like a whole it's just just really hard.

So yeah, it's just struggling.

So if you're at anthropic and you're watching this, if you could please improve your computer use to actually be able to use Google Docs, well, that would like totally change my life and change the life of Kate, our editor in chief and a bunch of other people here.

So yeah, please, please do that.

And also everything about AIs like a video game.

Absolutely true.

Karen, go for it.

Yeah.

So I'm thinking so we have this skill, but is it like the skills can be maybe optimized now to actually make use of sub agents and things like that that maybe were never available.

So it might be also time to rewrite our skills a little bit if you create a skills for cloth.

Maybe we can push it to use sub agents or you execute scripts more or like do some things in a programmatic way.

So there might be an opportunity also to do more of that.

Yeah.

Katy Parrott who wrote this article says surely this is the cleanest copy that has ever copied.

It's true.

It actually hasn't found many errors because Katy didn't make any.

But we'll see.

It's still working on editor in chief with dashes.

It's doing something.

Thank God this is working.

This is able to work async because if I had to like, we were actually, you know, looking over the overt shoulder for forever, it would not be particularly useful.

Yeah, we'll do a live stream or cloth should do live streams of it's doing work.

Yeah.

Yeah.

Actually, that's a really fun.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

It's a really fun thing to do.

This is going to be a lot more like the UX in Cloud Code where you can just send messages even if it's working and it will deal with the messages.

You don't have to wait for it to respond to your last one.

I think that's really good and important for async conversations.

We got our first compact.

The bane of every Cloud app user's existence is compact.

We'll see coming up after the break.

That's great.

We'll see you in Cloud Code.

We'll see you in Cloud Code.

Or forgot what I was doing and does something completely different.

We'll see.

One thing, it says Q, which is a little bit confusing because Q in my head would mean like do this after you finished one before.

But it's actually a little bit smarter.

If you say, "Stop.

Stop.

Stop what you're doing.

This is terrible."

It will actually look at the text and think like, "Hey, do I need to change anything what I'm doing right now?"

It does either pick it up immediately or if it's like after this, do this, it will actually queue it.

There is a little bit more flexible than just injecting it.

It will look at it whenever you add it, which is good to understand as well.

I wonder if Cloud is getting performance anxiety because it knows that 13,000 people are watching it.

Okay, dude.

I told him it was 13 people.

They're watching this.

Please just type.

You're so close.

If you want more extremely smart and insightful takes on AI, you should subscribe to Every.

Every is the only subscription you need to stay at the edge of AI.

It's every.to.

We have a pretty cool business.

We do ideas, apps, and training at the edge of AI.

On the idea side, we have a daily newsletter.

We get our hands on stuff like Cloud co-work early.

On the day that these things come out, we do vibe checks, which tell you from our team as we're using these in our day-to-day life and work, what is it good for, what is not good for.

That happens for products.

It happens for new models.

When Opus 4.5 came out, we had a review on the day of.

I can show you that.

We also develop apps ourselves.

I'll talk about the apps in a second.

This is the article that we wrote on the day that Opus 4.5 came out.

This is by Katie.

This is Katie's article with by Kieran and by me.

If you've been seeing all of the hype about Cloud Code and Opus 4.5, we started talking about it November 24, 2025, the day it came out.

We said it's the coding model we've been waiting for.

It took people about a month to catch up to that.

If you really, really want to know what's going on at the edge of AI, it's really good.

I'm biased, but I think this is a really good read and vibe checks are really good.

We also have apps.

We have four apps that we build.

As part of every, we have one called Cora, which Kieran builds, which is an AI email assistant.

Cora.computer.

We have one called monologue, which is a speech-to-text app.

You can see monologue right here.

This is monologue talking, and it will type in here.

I don't want to mess up our buddy, Claude.

It's sort of like WhisperFlow or SuperWhisper.

It copied it to the keyboard.

You see it.

It just pasted my text in there.

We've got a couple other ones, Spyro, which is an agentic ghostwriter, and Spyro, which is a file cleaner.

It's all available for one subscription.

You pay one price, and you get access to all the ideas, so everything that we write, all the apps.

So four AI apps at the edge of AI, and training.

We have camps that you can go to.

We're doing a cursor camp, where the team from Cursors is joining us in a couple days, and you get to learn directly from the cursor team.

You saw we had Felix from Anthropikon earlier.

We do these all the time.

We basically teach you how we build.

So everyone at Every is a builder and a writer, and as we're using these tools like Cloud Co-Work and Cloud Code to build apps and do writing and do design and all that kind of stuff, we bring you along for the ride.

You should subscribe, every.to.

And we're still on this extremely scintillating view of Cloud trying to make suggested changes in a Google Doc, and I think we can call this one just -- we need a Google Doc copy edit benchmark, and it has failed.

That benchmark is not saturated.

We're still not an AGI, folks, so stay tuned for hopefully the next model.

>> Anthony Morris from Anthropik, huge fan of Quora.

I love to hear that.

Karen, does that make you feel good?

>> Yes.

We have a few Anthropik peeps using it.

>> That's pretty great.

>> Thank you.

>> Yeah.

>> Karen, what's on your mind?

>> I think on my mind is I want to try this out.

This makes me very excited.

This feels like something that was missing.

Even as a coder, I want to use this, so if you are using Cloud Code, probably this is easier for you to use, and I really want to just see what it can do, how we can use it in our daily lives.

I would love iOS integration, like scheduling things, pushing things to my phone, like me chatting with it.

Also, one thing that looks like it's not super present now is storage.

Currently, you can store or connect it to your local computer, but what if you're on your phone?

Is there some persistence?

There are projects in the chat site, but there are no projects in the co-work site.

I'm very curious how to use this, but what I love is it hooks into the skills and things I already have.

What I'm going to do is whenever I would have started up a chat window, I'm now going to start up a co-work window and just see how it behaves and goes and just go from there.

>> Yeah, I think that's a good one.

We're going to have to write the vibe check in a few and probably also do some other work.

I am curious if you had to give this a rating.

When we do vibe checks, we have red, yellow, green, and then we have a gold medal for paradigm shifting.

When we did Opus 4.5, I think you and I were both at the paradigm shift level for comparison.

Where do you put this if you had to give it a red, yellow, green, or a gold medal?

>> I would rate it from just playing with it, like the UI and execution, I would say yellow because it's kind of janky.

But it's very interesting.

We can say what we want, but it is kind of janky.

But that's what they said.

We made this to try out.

I see anthropic is very, very good at listening to people.

I'm sure someone on the team here saw me click something or you do something there already pushing changes to this.

Because that's how fast they go.

I think we should experiment more with the interface, what it is, and giving this Claude's code moment to more people.

Having more people that do normal work also starts to feel a paradigm shift of async work and really handing something to an agent.

I think this could be that.

Because I don't see any other company do it like this.

And obviously Claude is very -- it's a very good harness.

Let's milk it.

Let's make it better.

I would say ID, green, execution today right now, yellow.

I think that's spot on.

Anthony Morris said I have a PR up already from something Dan said.

>> Exactly.

That's why we do these.

>> Welcome to the anthropic product meeting happening live on X with your friendly neighborhood product testers.

I love how there's already going to be changes in the product from this.

For anyone watching or listening, you should give more feedback.

Do it in the chat.

Send it to people on X.

They really actually do iterate pretty quick.

And I think it's fine that this is a yellow.

And the way that I think about it is obviously there's a Claude code moment on X over the last couple of weeks.

And that was the thing that they immediately shipped something.

How many founders were building a Claude code for -- we were calling it Claude code easy mode.

Because we were batting around internally at every two.

And they just built it.

They just went ahead and built it.

And I think that's so cool.

And it shows they have their finger on the pulse of what people want.

That's the thing that I think is good about a lot of anthropic stuff.

You can tell they use it themselves.

And they're using it in a very AI native and aging native way.

Absolutely.

They get it.

But they're also listening.

They get it.

But they also leave out things because they want to listen as well.

They're not like this is the way.

They're like this is a way and we're listening very carefully.

And then they make iterations.

Which is great.

Speaking of which, this is a way that if you want to build an AI, this is a way to think about doing it.

We have a guide up on every -- about agent native architectures.

So this is -- if you're a developer, this is going to be really good for a developer.

It's also totally good if you're a non-developer.

You just click read with Claude or read with chat GPT.

And it will tell you about what this is.

But this basically boils down a lot of principles that we've kind of intuited from the way that anthropic builds Claude code and now Claude for Claude co-work.

And turns it into a really easy guide to think about how do you build software in this era where agents are at the core of software instead of software being this sort of like deterministic thing that is built with deterministic code that are rules that are laid out beforehand by a programmer.

Instead, the core of something like Claude code or Claude co-work is just an agent.

And features are really just prompts to that agent to get work done.

And that opens up a whole new territory of software to build.

And it opens up who gets to build software.

So if you're a non-technical person and you're feeling like, oh, I can't really build software, I promise you you can.

You should really try Claude code.

You should really try just a Claude app.

Or now it's worth trying Claude co-work.

I think that it could be really good for vibe coding stuff.

And if you're thinking about how to structure your apps, it's actually kind of not intuitive because it's a whole new world for the way that you do programming.

And so a lot of the a lot of program intuition, I think, is outdated and a lot of therefore a lot of A.I. Intuition about how to build software is outdated.

So you need guides like these to help push your A.I. to do the right thing and build the build the thing in the right way.

I think we're getting close to time.

I'm going to need to hop off.

We're both going to need to hop off and get some actual work done.

This is fantastic.

It's so fun.

We do vibe checks for every new thing that come out.

We're doing this.

These live streams is a new thing.

Usually we just write them.

But you should expect next time there's a new model drop or a new product release that we will have a live stream vibe check with our internal testing.

Remember, we get all this stuff before it comes out and we'll tell you what we like and what we don't like.

Kieran, any final words before we head off the stream?

No, cheers.

Thank you, everyone.

Thank you.

Check it out.

Check out every try.

See you.

Yeah.

>> It's about chat GPT.

Every episode is a roller coaster of emotions, insights and laughter that will leave you on the edge of your seat craving for more.

It's not just a show.

It's a journey into the future with Dan Shipper as the captain of the spaceship.

So do yourself a favor.

Hit like, smash subscribe and strap in for the ride of your life.

And now, without any further ado, let me just say, Dan, I'm absolutely hopelessly in love with you.