- 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.
- 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
- 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
- Not really OSS though
- Why, because of the Sentry license?
