We Built a Doc Editor That Replaces Google Docs

It became clear that what we needed was a live collaborative web-based document that humans and agents could be in at the same time making changes and leaving comments and doing track changes and all

that kind of stuff.

>> I'm I'm trying to write this thing for Saturday that's like an essay about a dinner I had at Squirrel uh this like restaurant in LA. And so to get there, it's like a bunch of text between me and

my agent to push to this proof dock.

Using my agents and proof to get here, one, speeds up creative writing for me.

And two, I think does make it stronger and better and easier. And I love that.

And I can see what it wrote versus what I wrote for me, which is really helpful and so much better than a Google doc.

work moves fast. And in the age of AI, the pressure isn't just to move faster.

It's to make sure what you send really sounds like you. From emails to proposals to stakeholder updates, generic and rush just doesn't cut it.

And if you've ever stared at a blank page knowing exactly what you want to say, but not how to start, Grammarly fixes that. Grammarly gives you one

fixes that. Grammarly gives you one place to think, write, and finish your work right where you already write. Most

AI tools either take over or stay out of the way. Grammarly doesn't neither. It

the way. Grammarly doesn't neither. It

helps you break the blank page, adjust your tone so message lands right for the specific person reading it, and work seamlessly across 500,000 apps and sites you're already in. It's loaded with

agents built for every step of your process. 90% of professionals say it's

process. 90% of professionals say it's helped them save time. 93% says it helps them get more done. This is AI that works with you, not over you. In a world of generic AI, don't sound like

everybody else. With Grammarly, you

everybody else. With Grammarly, you never will. Download Grammarly for free

never will. Download Grammarly for free at grammarly.com. That's grammarly.com.

at grammarly.com. That's grammarly.com.

And now back to the episode. Special

episode today. We have been building a live collaborative markdown editor for both humans and agents. It works in the browser. Um, we love it. Uh, we started

browser. Um, we love it. Uh, we started using it internally. It's like really kind of taken off inside of every. And

so today we are launching it as a full product that you can go use. It's

totally free at proofed editor.ai. It's

also open source. And we wanted to just do this episode to talk a little bit about Proof, what it is, why it's cool, how we built it, all that kind of stuff.

So for people who don't know uh Brandon you are the COO of every and Kieran you are the GM of Kora uh and also the father of compound engineering. I also

want to welcome Austin. Austin's our

head of growth and you're proof fans.

>> I think we should go back to you Dan and be like why is it even called proof?

Because it's not called proof because of what it is now. It just happens to sound good.

So like what was it originally and how do we get here too?

>> I know you talked about this for a while, maybe a year already. So yeah,

bring us through all the pieces in your brain and also Dan is saying we built this thing, but really Dan built this

thing and we're just adding thoughts and things. Dan built this whole thing while

things. Dan built this whole thing while growing the company, while being a CEO, just at the side vibe coding, and he's getting the vibes. He's so happy doing

this. Look at at him smile right now.

this. Look at at him smile right now.

It's It's his baby. So, that's really cool.

>> Yeah. So, the CEO built a new product on the side that now everybody uses. That's

sick. And Naveen just submitted a PR that uh Dan just merged. I just

submitted a PR that Dan's gonna no look merge probably >> obviously straight to production.

>> And so like it's like now everybody's like, "Oh, wait. I want this feature."

And um it's like kind of it's amazing. Um

but yeah, Dan, why don't you tell us why don't you tell everybody why did you start building proof originally? I mean,

if we want to go way back, you know, we incubated a text editor, a word processor at every called Lex, um, like almost three years ago, maybe more,

which was the first time that we sort of combined um, uh, text and AI together.

And so, and and that was that was built mostly by my co-founder uh, of every Nathan. We spun that out as a separate

Nathan. We spun that out as a separate company. Um, and that was like you're

company. Um, and that was like you're writing but you're uh you're writing with AI on the side or like in in line with you a little bit in the in the actual word processor but it

fundamentally is a word processor. I I

think approve as being very different which is um it's for this mode of writing that I've started to feel like a lot of us

internally at every starting to do which is for example when you're coding with AI you make a plan doc um and that's that document is mostly written by AI and maybe you're like going in and doing

some changes here and there or like asking it to change it for for you um and that's a whole different way of interacting with writing I I think a lot of people have, you know, said for a while, oh, I'll never read AI writing.

And it's like actually I read AI writing all the time. Um, and I actually the the other place where I started to feel the need for this is actually we did this um

company planning exercise um for our 2026 planning, Brandon set up these notion agents which helped us for anyone who was running a business inside of every you get interviewed by an agent

and then it turns that into a like 2026 plan doc. And I just remember looking at

plan doc. And I just remember looking at all those plans and being like, "Wow, these are amazing." But also Austin submitted this like super comprehensive growth plan, but has he like really like

looked at every single line of this and does he really stand behind every single thing? And so the original idea for

thing? And so the original idea for proof is like we needed a good way to tell what was human written, what was a AI written, but also like how much thought went into everything and and

what do you actually stand behind versus not and um and and so like the the original version of Proof, it was a Mac app and it had uh

a little gutter on the side that showed like uh purple for AI and green for human, which it still has. But what was really interesting is in making the Mac

app, I did all this stuff. I had it had like this it was a sick Mac app. It had

this like cool internal agent integration with like sub agents and like all this stuff. But in using it, I was like actually the killer feature is just being able to share um and just

being able to share docs. And because

what we find is, you know, if I'm if I'm working on a a little thing with an agent and I make a plan, I really want Kieran to be able to look at it and I really want Kieran to be able to like leave comments and I really want Kieran's agent to be able to look at it.

And so it just sort of became clear that what we needed was a live collaborative web-based document that um humans and agents could be in at the same time

making changes and leaving comments and doing track changes and all that kind of stuff. And that's sort of like that was

stuff. And that's sort of like that was sort of like the evolution of it.

>> And I will say when you were building like the provenance version of proof, I was like this is cool, but I don't really get it. When you say it out loud,

like it makes sense, but I wasn't like reaching for it. And I don't think a lot of people were. Like I think the editorial team was excited about it, but like everyone else was like, "Cool, Dan's off doing this thing. Editorial

team likes it. Don't really know you know exactly what's going on. And then

when you the second you made it a web app and you made it a collaborative thing that agents could and humans could work on together, basically every single one of us started doing everything in

there. Um,

there. Um, so it's kind of just an interesting story of like finding the fit and now it's like a serious fit.

>> And it's also whenever like everyone uses claws or cloth or some kind of agent to do work. So we're also at this time where suddenly like there is all

this work done and there's all all this stuff generated but like how do you share? It's like a first step to like

share? It's like a first step to like memory or sharing or collaboration within a team. And it just feels like this is very natural as a glue to bring

things together because humans can look at it like I can look at it. I can open it which is is is nice. I can trust it by looking at it. Um and an agent can do

it as well. like it's it's equally and I think this is cool because this your agent native philosophy like this app is really built from those principles of

like agent native and uh yeah I would would love to like this this is your first agent native app in this way like what did you learn doing it that way like what worked what didn't

work because you say I had all these agents inside but there are no agents inside but there are because there are agents like can Can you tell a little bit like what you learned there? That's

a really good question and yeah, I do think it has been really useful to do this because getting my hands in the code, I mean it's not they're not really

in the code because I vibe coded this whole thing, but getting my hands in architecting the code, I'll say that has really um helped me develop like deeper

opinions about how for example an agent native product can work and what are the different types of agent native products. So like for example

products. So like for example um you can be agent native without having an agent in your product uh because you can have you can be agent

native from an internal perspective. You

have an agent in your product that can do anything in the product or an external perspective any agent can connect into the product and do anything in the product and both are valid and sometimes you can have a product that

has both. Um,

has both. Um, and I did I did actually like the um the the internal version, but I think what I started to realize, especially once we had claws, once you have a claw, the

claw has so much context on you and what you're doing that um what you really just want is a claw in your document with you. You want you want like that

with you. You want you want like that that co-author hanging out with you. And

um having an having an internal agent that doesn't know any context is just sort of it feels like not it's not powerful. It's not that interesting. Um

powerful. It's not that interesting. Um

and I can I can imagine there are certain times where you might want a language model inside of it. Like for

example, we have this way to um we're we're working on a way to uh summarize the document for the social share. So

when I share it with you, you kind of get a little bit of a preview. And

that's like a nice little LLM summary.

And I think there actually could be really interesting use cases for LMS on sometimes, you know, Austin, you shared this document, for example, where we were having all of our clause

update the document and just went it just went nuts. It went crazy. And I

think having an LLM playing a little bit of a traffic cop role in inside of a document could be kind of interesting.

like there's lots of stuff to do, especially now that there's um now that text is so cheap to produce.

One thing that you care about is is provenence potentially. And and I think

provenence potentially. And and I think that was less important than I thought.

But like you also need I I have this feeling like I need a canonical version of a document that like doesn't get updated unless I really say yes. And

then I want the agent to have all these other versions that they can like mess around with. And we can take what's good

around with. And we can take what's good about each of the different versions and put it into the canonical version. So

that's what I love about getting to build this stuff is you start to get intuitions for now that we've relaxed this constraint. Now that agents can

this constraint. Now that agents can write inside of a text editor super easily and they can write a ton, it opens up all of these different possibilities for what you know what you might want your text editor to be.

especially if you're mostly optimizing it for the agents to do the writing. And

humans can write, but like usually when I'm writing in proof, it's like I feel like I'm God like coming down and just like giving my like little sentence or whatever. Uh because uh it's so rare.

whatever. Uh because uh it's so rare.

Um yeah >> I think we should I think a couple other things that I realized through using it a bunch is like I always knew that

giving context to an AI is so important.

But through proof, I realized how important it is to create like such a good plan, how much more effective it is to create a good plan and then say go do that plan. Proof is a place where you

that plan. Proof is a place where you can do that. You can work on the plan together and then say go do that plan.

Um, and I know we all have really good examples of that. The other thing that I realized is like Dan, when you first told me about it, I was like, "Oh, cool." But like we need a place to like

cool." But like we need a place to like save these things, you know, which is true and like we're going to launch that. But it actually doesn't matter

that. But it actually doesn't matter that much because the reality is like plans are really short. like they help you do long horizon things, but in the

grand scheme of things, they're just like a moment and then they don't matter anymore. Um, so that's been amazing.

anymore. Um, so that's been amazing.

Like I have five proof docu documents open right now and especially because I make them with my claw because my claw has a skill and it she just knows to

like make proof documents when I want to make a plan. I don't even need a place to save them because I just say, "Zoa, like pull up the Slack to Discord, Discord to Slack proof." And she sends

it to me. Um,

so those have been like interesting experiences that are different than, you know, normal working.

>> Yeah, totally. It it like it's it's part of it's it's all sort of a function of text is really cheap to produce. It's

really valuable, but it's also really cheap to produce. And so the way that you might design h how you work with text has to change. So um I can I'm

going to share my screen so we can um we can show proof. Um so this is what it looks like.

Um it's just uh this is the landing page. It it will actually be different

page. It it will actually be different by the time this episode airs, but this is the landing page and it's super simple. You just press start writing and

simple. You just press start writing and now you're now you're in a document.

That's that's all you have to do.

There's no login or nothing like that. I

can say um uh proof podcast agenda. And you can see it has this like kind of green thing over here which means I wrote this. And

I can do a little title. But the cool thing is and I probably have to change my sharing settings in order to show you this. Um

this. Um the cool thing is that what I can do is um

what I can do is I can press add agent over here and I can copy that link and post and give it to my claw R2 and I can say I'm recording a podcast.

Um can you fill in an agenda? Um, it's

about the proof launch. Um, and what you'll what you'll see in a second is R2 is going to actually join this document and write a bunch of stuff in there. And

then and you can see R2 here. Um, R2 is right here. He's got a little claw icon.

right here. He's got a little claw icon.

And you'll see him in a second actually start to sh uh start to uh write stuff in this document. And then I'm going to actually share it with the podcast crew here so you can see everybody else here

as well.

You can see we've got Brandon's in here.

We've got an anonymous collaborator. I

don't know who that is. Hopefully, it's

uh nothing nefarious.

Um >> that's me. I think

>> that's Kieran. And in just a second, we will cut through this, but in just a second, we will have our two posting a

uh a plan dot for us. And um let's hope it works. Live demos, folks.

it works. Live demos, folks.

>> It's it's not live live. So

>> it's not live live. That's true. That

Thank God. Here we go. We got a proof we got a proof launch podcast agenda. We

got one thing.

>> Woohoo.

>> All right, we're gonna Yeah. Go for it here.

>> Yeah. What what is very cool is you pasted this snippet inside your a agent there but you don't have any skill or anything

installed. It's just copy paste, right?

installed. It's just copy paste, right?

There's nothing more than copy paste which is very very easy. It's super low friction. It's just copy paste. And the

friction. It's just copy paste. And the

idea is to um yeah make it as ergonomic as possible. One of my things I've been

possible. One of my things I've been saying recently, one of my bits is, um, I think AX is just as important as UX in this new world. Um, and AX is just

agent experience versus user experience.

And what's really interesting about AX is if you want to optimize it, all you have to do is ask the agents. So, it's

really easy to be like, how would you have made this better? Um, and or how would you why did you get confused? and

how would you make it more ergonomic for yourself? And that lets you iterate the

yourself? And that lets you iterate the AX so that um it's super intuitive for any agent to use it. And that's what

what I've tried to do here where it's it is better if you have a skill, but it is um it is totally possible for the agent to just basically figure it out because

everything is available to it.

>> Yeah, that's really cool. And I think because of that, like I started using it immediately because it was so easy to get started. And then you feel it.

get started. And then you feel it.

You're like, "Oh, this is super handy."

And you're like, "Oh, but I want some refinement here. Let me create a skill

refinement here. Let me create a skill around this. Uh do something like that."

around this. Uh do something like that."

And then you're already using it and sharing it. So that is very good. Like I

sharing it. So that is very good. Like I

think that is the the major strength is that you can just immediately share this with an agent without logging in, creating accounts, anything. That is

very good.

>> And here we are. We've got our podcast agenda. And so you can see um you know

agenda. And so you can see um you know it's all purple. Um we still have Archu in here. We've got Brandon. We've got

in here. We've got Brandon. We've got

anonymous collaborator. And I can just go in here and say hello.

>> Oh, that didn't work. Um, wow. We've got

some bugs here, folks. Um, and I can just go in here and do hello, and it shows up green. And that's that's proof.

Um, and it has uh really changed, I think, the way the a lot of us work.

Austin, I'm kind of curious from your perspective, you know, on on the growth side, like are you using this and if so, how? Um,

and and how does it Yeah. How has it changed your workflow? We like to move really fast at every we're always shipping new features and we run five products internally with just 20 people.

It used to be that updating any of our landing pages was a huge time suck. But

then we started to use framer. Framer is

a website builder that works like a design tool, which means that the people who are closest to your brand and your customers can shape your landing pages themselves. Non-coders on our team use

themselves. Non-coders on our team use it all the time to ship website updates.

And the results honestly are beautiful.

It's really easy to use. There's

real-time collaboration, which means your team can design together, see changes instantly, and ship faster. A

robust CMS gives you everything you need for great SEO and content management. It

also has advanced analytics with integrated AB testing that lets you optimize and improve continuously. Then,

it's just one click to publish. Your

changes go live in seconds, so you can iterate at the speed of your ideas. And

it's not just us. Companies like

Perplexity, Miro, and Mix PPel trust Framer for their websites because the tool is enterprisegrade. They offer

premium hosting, enterprise security, and 99.99% uptime SLAs's. Whether you're launching

uptime SLAs's. Whether you're launching a new website, testing landing pages, or building out your full site, Framer gives you the tools and support to move fast and build something great. And

everyone on your team can use it. Learn

how you can get more out of your.com from a framer specialist. Or get started building today at framer.com/dan

for 30% off a Framer Pro annual plan.

That's framer.com/dan

for 30% off. Rules and restrictions may apply. Seriously, we use this tool all

apply. Seriously, we use this tool all the time. You should really check it

the time. You should really check it out. And now back to the episode.

out. And now back to the episode.

>> Yeah, I I use it in two like normie ways I really like. Two of them just happened today actually. One is um our colleague

today actually. One is um our colleague Rachel who produces the podcast made this uh like Slack based bot to make scheduling live streams easier. She made

it and called co-work sent it to me and was like, "Hey, can you install this into Slack for me since I have admin permissions?" and it didn't quite work

permissions?" and it didn't quite work right away. So, I went into cloud code

right away. So, I went into cloud code and the CLI and made some changes to it until it started working. And then at the end of the session, it's a thing I started doing with like a bunch of

people on our team who like me are not technical but are pushing on these tools. I asked Cloud Code like, "Hey,

tools. I asked Cloud Code like, "Hey, can you make a proof doc for Rachel so that she can see everything we did and just send it to her?" And especially cuz

it's so so like lightweight and easy and Claude especially on Opus 46 like knows how to recap that really well. I sent it to her and she was like, "Wow, this is so helpful that I can see like what you

did to improve this." And it was really funny. Dan, you and I were talking about

funny. Dan, you and I were talking about like how we were going to launch this thing I think on Monday. And I had this whole plan in my mind of like, "Oh, it's all about providence. It's all about you got to like send your boss this like

planning doc and they got to see what you wrote and what the agent wrote. And

I I had so much conviction about that a couple weeks ago on Monday. You were

like, I don't really care about that anymore. Like it matters, but it's like

anymore. Like it matters, but it's like actually this thing where it's like a it's like one space for agents and humans to work together is really powerful. So there's that. And the other

powerful. So there's that. And the other one that I've really loved as someone who does a lot of like personal creative writing and comes from a place at

Substack where people like hold their own voice and writing so precious to them in a way that makes sense and is actually like people on subse all the time of like I know who's writing with

AI and like I'm judging them, right?

Like I have loved proof as someone who writes about food each week for a newsletter because I'm often like I'll eat somewhere and then I'll text my claw like here's what I thought and I'm like

keep a running proof doc of my thoughts like from the eating I'm doing because that's the best way to like have a running dock and then I'll be like I usually tell it like make me an outline and then I get an outline it's always

updating and then I'll go in and write into the outline myself and I love that and I see what it wrote versus what I wrote for me which is really helpful and so much better than a Google doc. Like I

was doing that in Google Docs and one it's really clunky with agents in Google Docs. I'm not smart enough to figure it

Docs. I'm not smart enough to figure it out but also I can't track like what's me and what's the agent which is really important to me. So those those two which are a little more like personal work stuff has been really really

powerful for me.

>> I love that. I use it for that all the time. Um, like I use it I have basically

time. Um, like I use it I have basically my daily to-do list. I just do it in proof and I I every every week I make a new document, I pin it in Slack and then

I'm just, you know, it's we're doing a lot there's a lot of stuff happening all the time and anytime something happens, I'm just like, cool, throw it in my to to-do do and that makes it really easy for me to make sure, okay, at the end of

the day, what did I do? What did I not do? Okay, RTC2, my claw, can you just go

do? Okay, RTC2, my claw, can you just go take the stuff I didn't do and like push it into the next day or can we figure out how to like get it done? Can you

just do it? You know, that kind of stuff. It's really helpful for those

stuff. It's really helpful for those like kind of async document creation and and updating so that by the time you get into it, it's ready for you to just like get started.

>> Yeah, I I got really excited yesterday during the madness of all of our agents trying to update that doc for us because I think I think Kieran like you and actually it was funny all of the engine

all the GMs were like this is insane. I

can't focus. Way too much [ __ ] is happening is what we were trying to do is I was trying to build this like landing page that was an always on reach test forever of like you could always go

and see what is our team using for VI coding for writing for research and I was like oh can our claws just update it themselves and it's not quite there yet

they kept like duplicating and then like triplicating the page but it made me excited because it's like this thing will be there I think relatively soon right that It's like your agents can go

in and update stuff and my agent can read what Kieran's agent wrote and then I can read the changes. And for a company that's using like as many agents

as we have people and for someone who does a lot of strategy docs like in in this world, it seems like such an essential way of working now once we get it right.

>> Yeah, I that that's so true. And yeah,

there's this thing where it's like one agent who does one bad thing can pollute the entire document.

And that's a really interesting problem to solve. Like you don't have to do that

to solve. Like you don't have to do that and you don't have to worry about that in Google Docs because like humans there's a big social cost to like ruining someone else's document and um

humans are generally smart enough not to do that. But like agents with great

do that. But like agents with great power, they have a ton of power and zero responsibility. So like they often like

responsibility. So like they often like just do [ __ ] that you you would be like ah I don't think I would do it quite that way, you know? And I think that's a really interesting user experience challenge to figure out how do you how

could you have 10 agents in a document and make the output actually good.

>> Yeah. And the like the the the like humans plus agent collabs like I think if it's like only the agents are working in this and we'll see what they come up with is one thing or like only we're doing this and then our agents read it

is another thing. But go coming to a future where like we're somehow all working in there together whether it is like a a planning dock a piece of writing like I think we're we're headed

there and that's a entirely different way of working that we are breaking so that we can figure out how to make it work for everyone else.

>> Yeah. I think another another thing that proof makes me think about is as people who love writing and all of us here are writers um what does it mean for the

future of of writing um and there it feels to me like there's there's a class of writing where you actually want to read it from the AI more than you want to read it from the human which is kind of surprising and

interesting like that document that you made for Rachel Austin if you had written that document I don't think that she would have wanted to read But >> no, and I think the I I'll I'll share it

right here. I think it's like it's

right here. I think it's like it's interesting >> to see. I also don't really think that she should read it. I think like an agent should read it and summarize it for her. Can you see?

for her. Can you see?

>> That's also probably true. Yeah. Yeah.

>> Yeah. Okay, cool. So, like, yeah, the agent pushes this like there's so much stuff in here that I would never write or care about if I got this. Like say

say I built something like say I tried to ship something to prod and Dan like you were reviewing it and then you sent this back to me um like a version of this for like stuff I should have fixed.

I would probably scan the headlines to like loosely see what this thing is and then I would ask my claw to summarize it for me. And actually there's been a lot

for me. And actually there's been a lot of that now in how we work of like okay the agents are making big docks. It even

applies to like the open claw guide that that you worked on with Willie the other day of like I didn't read that whole thing. I had my agent recap it for me.

thing. I had my agent recap it for me.

And for something like that, that's what I want to do. But when you write your like essay on like the future of agent native architecture, I do want to sit

down and read it. And um it's going to be like it feels a little binary in my head, but I think it will keep expanding into more of a spectrum in that range of of what is what.

>> I definitely agree. I think that there's a lot of there's a lot of writing that is more on the information transfer end of things and less on the storytelling

and like personal experience and like vibe end of things that is probably better read by an agent if it's if it's pure information transfer because it's it's a little bit like um in the Matrix

where you like I know kung fu you know like that's kind of the experience that like having your agent like read a proof doc is is like I know kung fu now And um

it's just harder like you you actually don't need to know kung fu if your agent knows knows it. And um you can save your brain for things that you're good at.

>> I want to show my the the proof experience that I just had um because I think it kind of highlights like the

collaboration between like two humans and two agents. So, this is like a little bit meta because I wrote a proof doc about how or I didn't write it. I

had Codeex write a proof doc about exploring the idea of adding a dashboard to proof so that anytime you make a new proof or somebody shares a proof with

you, it saves into like a place that you can go so that you can see all your proof documents. Um, I have zero idea

proof documents. Um, I have zero idea how to code by the way. Um, I literally

can write CSS and HTML. Um, so I like basically went back and forth with Codeex a bunch and was like, "Okay, put this into a proof doc." Uh, and then it

made this proof doc. You can see the only thing in this entire document that has been edited by a human is Dan came in here and commented. Um, so basically

what happened was I had Codex write this proof doc. I went to our proof channel

proof doc. I went to our proof channel in Slack and I said and I dropped in the link and I said R2C2 which is Dan's uh

uh plus one uh to check it out and to let him let me know what uh he thinks. R2C2 knows Dan really well and gave a bunch of feedback

all of which was like really accurate.

Um, and uh, and then Dan, I think Dan on the side was like R2C2 like make those comments. Make those updates. It made

comments. Make those updates. It made

those updates and then Dan came in here, reviewed it, he added a couple comments.

So, you can see our uh, Proof does great commenting and agents can read the comments. So, Dan commented on here. I

comments. So, Dan commented on here. I

went through like I made a b a couple more comments. You can see on the left

more comments. You can see on the left side from the blue that like this is basically all agent written. Um yeah, so there's one comment on this. I told

Codeex go back in there, read the comments, um and then update the plan. It did that and then I told Codex to execute on that

plan and it did. Um, so

I mean that is like just sort of a loop that is kind of on repeat now um at at every where you make a you make a plan,

you send that plan to the the product owner's agent, the product owner's agent does a review, suggests stuff because you can agents can suggest stuff and

proof.

It does that then goes to the their owner who owns the product in this case is Dan says hey Dan I did that I made it some edits can you review Dan reviews gives a thumbs up and then I go back and

I I do it because this is like my future and proof >> it's pretty cool yeah it's like I saw that come in and then I talk with R2 a little bit about it and I just had R2

write you a little letter at the top being like here's what I like and here's what I don't like and then a technical appendix at the bottom being like here's how I would implement this and then that

let you take codeex and have codeex just like redo the whole thing and what you ended up building was way more on target with what we might actually use and it's pretty cool that you're just like

submitting PRs and I have not looked at the I have not looked at PR yet so it's possible uh if possible we need to start over on that one's a big feature but it's it's a whole new world like that

you're submitting PRs and that I can even build this like this is a very very complex app that I just did in my spare time in between meetings. And um and and

not only am I building it like you're submitting PRs, like Kieran submitting PRs, Nine submitting PRs, it's becoming this like collaborative thing that we're all contributing to. It's just a totally different way of um building products

that I'm really excited about.

>> And it's the exact type of writing that like makes so much more sense to be summarized by agents to flow in between

the three of you rather than any human reading the whole thing. Like I think like you said and like we're all people who care a lot about writing and good writing, the quality of it, the

production of it, the consumption of it, and that's like something to be protected. But when it comes to

protected. But when it comes to something like this, this is about information and ideas and both like accelerating how you distill them, accelerating how you implement them is

is like essential to to where we're headed. And I like it it makes me so

headed. And I like it it makes me so excited for how this works and also like what what is still valued and protected and kind of like the the other kind of

writing, right? Like to me they're like

writing, right? Like to me they're like it's I think it's easy when you think about this stuff but don't practice it to think that they're in conflict with each other and that one's going to take away the other one and then when you

practice it you're like this is actually a very different thing. Uh they're like totally like separate from each other.

>> Yeah. Would you Austin or Dan or Karen would you write would you write anything that's not a plan or something that's like I don't want to say throwaway but like

kind of throwaway like it doesn't have like a long lifespan in proof or would you go back to like docs or notion for that?

>> I'll show I'll show you one uh example.

So, like I'm I'm trying to write this thing for Saturday that's like an essay about a dinner I had at Squirrel, uh, this like restaurant in LA. And so, to get there, it's like a bunch of texts

between me and my agent to push to this proof doc. And I like having these three

proof doc. And I like having these three separ I'm I'm messaging my my claw because I have these ideas. I actually get most of my ideas when I'm like when I'm out on a

run. And so after I'm done running, I'll

run. And so after I'm done running, I'll just like text everything so I don't forget it, so they don't escape me. And

I like having these three different sections where it's like, give me this like bank of notes I can go look at so I don't forget stuff. Give me a outline of

ideas to write into if I want to. And

then like maybe you can draft it for me, but I actually only let the agent draft for me if I um monologue into it because then I'm like it it feels like it's like

70 to 90% my words that I'll use our speech to text to a monologue so that I can see it. And then my process here which I've started doing in proof is I

either like rewrite every line or I'm like okay I can like see the essay now.

It's actually very helpful to see it.

This is a lot of what Spiral does to our like writing partner. And then I'll either like start fresh or I'll just copy paste the outline into somewhere

new to get it. But using my agents and proof to get here one speeds up creative writing for me and two I think does make it stronger and better and easier. I do

sit here sometimes with some like uncomfortable feelings of like, oh, am I like taking a line the AI added in? And

I Dan, you and I talked about this, like a future version of this that I would love is if it if it identified what I monologued in because to me, those are my words, right? Like if I monologue something into the agent and it uses it,

those are my words and I want to know.

But I've started doing this a lot more.

>> I would love a little bit like if you go if you hover over that gutter, it just like popped out and said like, you know, from a from, you know, monologue or whatever. Like I think there's a lot of

whatever. Like I think there's a lot of interesting stuff to do there eventually once we kind of nail the most basic experience. This is I love this. This is

experience. This is I love this. This is

super cool. I love that you're using it for this. Uh it's so creative and and

for this. Uh it's so creative and and interesting. Um

interesting. Um >> yeah. Wow. Thanks for sharing. Awesome.

>> yeah. Wow. Thanks for sharing. Awesome.

>> Yep.

>> Um Kieran, what's on your mind? What are

you thinking about?

>> Yeah. What I like about this is like clearly we need something to share stuff and and this is a step and I like how

you build something very more more complex agent native like the way and you realize actually we need to like

just go back to like it's just writing and collaboration and for me it really feels like it's it's like a sketch pad.

or something like that where I brainstorm something. I like ah I don't

brainstorm something. I like ah I don't know like just put it there and then I text it to you or you send something to me and you can kind of share thoughts or nuggets with each other. I like it for

that a lot. One other way I like it for is when I do a brainstorm with the compound engineering plugin. There's a

step called brainstorm. At the end it will say share to proof. You just do that and then it will automatically share to proof and you have a a sharable link. I run and t-mox over SSH. So

link. I run and t-mox over SSH. So

technically thanks then then I can just click the link and it works. So that is nice. I can share it with people but

nice. I can share it with people but also I can just open it go in make suggestions in like an actual document and then just

tell the agent hey made some comments uh go work on them. So I also like it for iteration uh with the agent itself uh just for myself.

My question always with these things is like, yeah, but we have markdown files, right? Isn't this just a markdown file?

right? Isn't this just a markdown file?

And we have GitHub. Isn't this just a g a gist or isn't it just an issue? We

have linear, we have notion, we have all these tools and they pretty good CLIs and everything like that as well. And

and what I like about proof is yes, we have all of these, but there are all these connotations around them what a GitHub issue should be or like what a notion page should be and you don't want to like contaminate everything. So I

love actually that we don't have a place where you can see all your proof documents. So I would even argue we

documents. So I would even argue we shouldn't have an index with all your proof documents because the point is that if you think it's important you

keep that link somewhere and proof's job is not to organize documents. proof's

job is to communicate uh about writing and about ideas and about where it comes from and and I think it's very strong like and it's

super seam like just that it's so seamless to share it with your agent and and we don't know what's next but like the cool part is like Austin is saying yeah I want to see what I monologued

into and like I I also like going into document this was written by Brandon this was his agent. These were the like the history maybe on the document. I'm

like, well, let's see what we need to add and let's add that. So, for me, it's very exciting because we have all these things. We all feel these pains and

things. We all feel these pains and they're like we're just figuring out a new way to do this and I like that it's so bare bones. Uh yeah,

>> totally. It's uh I was very inspired by Naveen who runs Monologue where it's like it's a simple product that does one thing super well and I think that's

that's what I was trying to do here and it's actually surprisingly hard to make this even though it's simple. Um

>> it's very hard. Yes.

>> Yeah, it's hard. And uh Kieran, I love I love that you're you're kind of picking up that the lightness of it is what makes it good. Like you don't have to think about anything. There's no where does this go or anything like that. It

just works and that's what we're that's what we're after.

>> I still want to see your inbox feature, Brandon, but I'm just arguing.

>> I totally appreciate that. Like cuz

you're right and I have like five proof docs open right now and I really want to just like a quick place go to be like, "Yep, that's it."

it." >> Makes sense. Yeah. Maybe you promote a proof document to like a special place.

like proof documents are always there but if you create an account suddenly you can say put this in my special blah blah blah or something. Yeah,

>> I like um I I tried to make a a big like growth strategy plan in proof. I think

actually I was sending it uh Dan to you and Brandon as a notion doc and a proof doc because I like couldn't really craft it or figure it out. But I liked going back and forth in proof. And the thing

that felt intuitive to me was like let me and either one or multiple of my agents jam on this like campaign strategy and proof and then when it feels kind of like ready what right now

I'm I'm like using the CLI to move it to notion. But I think like that's what

notion. But I think like that's what makes sense to me is like let me actually oneclick it into notion for us for notion because that's where like our source of truth for planning and

information lives. And it's like, okay,

information lives. And it's like, okay, now it's like ready for that. It's

actually ready to move from lightweight to heavyweight. It's ready to move from

to heavyweight. It's ready to move from a from agent-based to like calendar integrated. And that's like not what

integrated. And that's like not what this that's a much more complex product and probably unnecessary what this project is, but like that's when it's ready for that and that started to make more sense to me.

>> Which leads me to ask you, Dan, this is going to be an open source product.

Does that mean that people can submit PRs or that they can just fork the repo and do their thing?

>> Both. Both. Um, but I think the the the most interesting thing is >> ideally you can integrate this into whatever app you want to build. Um, we

already have this internally. We have

Spiral. Spiral needs its own like live document editor. And this is like just a

document editor. And this is like just a really easy version that Marcus can just like throw into Spiral.

>> It's in compound engineer. It's in

competent engineering. Um well the ho the hosted version is in competent engineering but I think like you know for any kind of builder a it should be it could just be a good example of this is what you can make and how you might

want to architect things. Um if you're if you're vibe coding I know if you're a professional engineer you might look at and be like holy [ __ ] I can't believe this works.

Um, but be hopefully uh if you're if you're making any kind of app that has a text editor in it, which I think anybody that has a claw right now is running into this is like I need a text text

editor um for whatever app I'm making.

Hopefully it's just like a really easy drop in thing that you can use. So,

um that's proof everybody. I'm uh I'm I'm psyched that we got it out. Uh and

I'm psyched for the future. And uh thank you all for for joining and talking to me about it.

>> Thank you so much.

>> Thank you so much.

>> Thank you.

>> See you.

>> Oh my gosh, folks. You absolutely

positively have to smash that like button and subscribe to AI and I. Why?

Because this show is the epitome of awesomeness. It's like finding a

awesomeness. It's like finding a treasure chest in your backyard, but instead of gold, it's filled with pure unadulterated knowledge bombs about chat GPT. Every episode is a roller coaster

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

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