Dan Shipper

Like I think one of the problems with open clause is like their memory is kind of like shaky.

And like you might follow up an hour later being like, hey, did you fix that bug?

And I'll be like, what bug?

And you're like, I'm literally going to kill you.

Yeah, yeah, yeah.

So that's why I'm really – I'm more of like an agent maximalist.

Like we're going to have a lot of different agents doing a lot of different things.

And the ergonomics of a codex right now for staying organized to make sure you actually like finish the work that you do and it's done well is I think quite helpful.

But then for your claw, like I'm just constantly being like, okay, how's usage today or –

You know, like file this bug or like the whole way that we do bug reporting is changing first in proof.

But I'm hoping we do that through the rest of the org where because proof is agent native, meaning agents can use it as first class users, it has a bug report function.

And so agents just submit bug reports.

And the bug reports you get from agents are way better than the bug reports you get from humans, even if they're initiated by a human.

Because they can be like, hey, this is exactly what I did.

And here's the exact error message.

And here's the line of code where I think it might be, depending on how much they know.

And what happens is every morning, my agent, R2C2, then goes through all the issues that were submitted by agents and then

clusters them and says like here are the main issues that we need to solve um yeah and so that's just it just like totally changes how you how you work um even if you're using codecs mostly for coding yeah

Well, I don't think that there's any one answer to that question.

I agree.