It started as exploration. I wanted to understand the agentic stack properly, and the way I learn a system is by building it — so in early 2026 I built one in Python, on ground that OpenClaw and pi had covered in TypeScript.
It did not stay an exercise. Both projects run production workloads today, and that is what shaped them: gates that can block a tool call before it runs, retries with backoff, history compaction, streaming that survives the user closing the tab, multi-tenant isolation with property tests behind it. You do not write those because they are interesting. You write them because something broke at nine on a Sunday.
What came out is two things worth having. Agentino is the loop — small enough to read, with three dependencies and no graph DSL. Runspace is everything around it: an open-source, agent-native alternative to Slack, where your agents sit in channels alongside people, plus the gateways that reach them on Telegram and WhatsApp, and a rendering layer that turns tool output into real components instead of walls of text.
Both are Apache-2.0. I am opening them because they are good, because I would rather they were used than sat in a private repo, and because the next stretch is more interesting with other people in it — more runtimes, more channels, more widget types, more backends behind the adapters.
If any of that is a problem you have, come and build on it. Issues, pull requests and awkward questions are all welcome.
Not a prototype. Everything below is implemented, tested and running somewhere.
Bug reports and feature requests are better as GitHub issues — they stay visible to everyone else who hits the same thing. Security problems should go through a private advisory, not email or Telegram.
Both projects are on the front page, with the one question that tells you which of them you need.
Back to the projects →