Our primary focus is a stateful API for you to manage / interact with agents. We manage all of the complicated parts (conversation persistence, sandboxes, MCPs, etc), which allow users to focus on building their product-specific agents on top.
On our managed platform, you can buy credits which you can spend on tokens and on sandboxes (which are priced at cost + a 5% fee). If you want to self host, you can also do that.
> A detailed I noted on permissions - looks like they're all prefixed with "always" - I think allow/deny/ask make more sense ?
Yeah, the wording can probably be improved here, thanks for the feedback!
I think a lot of people are building their harnesses this way more recently, but last year, Claude, Codex (and other harnesses) were storing everything on a big json file on disk.
Codex has (to my knowledge) always stored sessions in append-only .jsonl files. Whether you store an append-only log in a file or a database makes no difference.
It really feels like I'm being gaslight here into believing "durable agents" are novel. All I'm seeing is the API that is behind any Chat Web UI. Persistence, resumability, recovery from errors and branching and forking have been table stakes there since the release of the first ChatGPT.
On our managed platform, you can buy credits which you can spend on tokens and on sandboxes (which are priced at cost + a 5% fee). If you want to self host, you can also do that.
> A detailed I noted on permissions - looks like they're all prefixed with "always" - I think allow/deny/ask make more sense ?
Yeah, the wording can probably be improved here, thanks for the feedback!