Fascinating platform. The API surface is much richer than I would have expected. Ooc, at what size do you think teams typically have use for this? I imagine you have to be running quite a few agents at scale before there's a strong usecase.
JoshPurtell 45 days ago [-]
Just like codex or opencode provide strong oss implementations of the core agent loop, our ambition (not achieved! hoping this is a solid start) is to provide a solid oss implementation of the context updating loop, memory, basic database + a backend sync layer. And evals + continual learning + gepa optimization.
Just like everyone can write their own agent, yet many opt for codex/claude code sdk/opencode, we think that at some point in our journey, many will also opt for standard implementations of these patterns, for projects big or small.
Realistically, though, the case for a standardized environment grows a lot stronger when you have multi-agent, permissioned actions, and generally just a lot more state than what you can get away with using only opencode + some glue. Insofar as big teams have ambitious products, they might be more likely to try it
Shindi 45 days ago [-]
Really cool project, it looks really useful. We’re moving past manual prompt optimization and considering different options for tuning long horizon tasks. We will likely go with Horizons
Charliecf 40 days ago [-]
Really cool!
Nikkau 44 days ago [-]
Not really OSS though
JoshPurtell 44 days ago [-]
Why, because of the Sentry license?
JimDabell 42 days ago [-]
Yeah, that’s not open source. You plan on releasing today’s version as open source two years from now, but it is not currently open source and won’t be for years. Even when it does become open source it will be a version that is two years out of date, not the current version.
Open source allows commercial competition. You apparently didn’t want that, so you chose a non-open source license that specifically forbids that. That’s your prerogative, but you shouldn’t tell people it is open source.
JoshPurtell 40 days ago [-]
I concede that it is not precisely OSS. But if I tell someone that it is source-available, they will expect some kind of license restriction for any use. If I tell someone OSS, they will expect mostly what the Sentry license entails, unless they are a competitor, in which case I really don't care what they think.
I wish there were a popular term that conveys exactly how Sentry license works. But, there isn't - so I think it's fair to say open source, maybe as a general term. I'll change it from OSS to open source
45 days ago [-]
45 days ago [-]
Rendered at 12:17:13 GMT+0000 (Coordinated Universal Time) with Vercel.
Just like everyone can write their own agent, yet many opt for codex/claude code sdk/opencode, we think that at some point in our journey, many will also opt for standard implementations of these patterns, for projects big or small.
Realistically, though, the case for a standardized environment grows a lot stronger when you have multi-agent, permissioned actions, and generally just a lot more state than what you can get away with using only opencode + some glue. Insofar as big teams have ambitious products, they might be more likely to try it
Open source allows commercial competition. You apparently didn’t want that, so you chose a non-open source license that specifically forbids that. That’s your prerogative, but you shouldn’t tell people it is open source.
I wish there were a popular term that conveys exactly how Sentry license works. But, there isn't - so I think it's fair to say open source, maybe as a general term. I'll change it from OSS to open source