I built something very similar for my company internally. The idea was that that the maintenance of the code is on the agent and the code is purely an optimization. If it breaks the agent runs it iteratively, fixes the code for next time. Happy to replace my tool with this and see how it does!

Super cool! Please let me know how it goes. Since agents are so good at writing code, we think letting the agent rewrite/test the code on failure is better than just using a prompt at runtime

I’m totally a target audience here. I’ve been trying so many different app switcher applications. My latest favorite one is “flashspace”. I would love that kind of functionality be part of this too if possible. Regardless I’ll give it a shot for a few weeks and see if it works for me. Thanks for sharing!

It would be really nice to have improved transparency in token usage and throttling imo.

Bluesky does this. In fact, the For You algorithm is a community built algorithm and way more popular than the native Discover algo.

Sort of feels like gastown enterprise edition

I think most people do want this. They want to own their data. If you ask someone if they post on IG, if they should own that, or IG, they'll tell you it's them.

The hard problem IMO is how do you incentivize companies from adopting this since walled gardens helps reduce competition.

We want more control over data that we've created, and more control over data that's about us. I'm not sure either of these concepts align well with "ownership" though. Property and data are concepts that don't mix.

Language nitpicking aside... you subvert the walls of their gardens and aggregate the walled-off data without the walls, so users face a choice not between:

- facebook

- everything else

but instead between

- facebook and everything else

- just facebook

But that approach only works if we can solve the "data I created" problems in a way that doesn't also require us to acknowledges facebook's walls.