For the last year we've been building AI workspaces. With every new product, we found ourselves rebuilding the same context layer and infrastructure. We tried existing solutions, but we'd either have to lock into one provider or have to manage the storage infrastructure. What we wanted was an API that's stateful and isn't tied to a specific provider. So that we didn't have to think about compaction, differing schemas, or running the infrastructure ourselves.
Since we'd already built most of the constituent parts, we’ve decided to release Twigg.
The API is deliberately simple. You create a chat and get back an ID. When you have a new prompt or tool result, you send that plus the ID. There's no need to store or manage context yourself. It appends the new prompt and assembles the history for you. To switch models, you change one field in the next request.
The dashboard covers most of what you'd want to configure: tool schemas, system prompts, context window limits and retention settings.
We'd like to hear from anyone who has run into the same problems. How are you hosting your context right now, and what would make you not want to hand it to a third party?
Comments URL: [https://news.ycombinator.com/item?id=49727072](https://news.ycombinator.com/item?id=49727072)
Points: 1