Rune: A Rust-Native AI Runtime — And Why It Needs Contributors

I have been building Rune over the past few weeks — a Rust-native AI runtime that acts as a personal agent gateway. It handles multi-provider routing, durable sessions, semantic memory, tool approval workflows, and federated multi-instance orchestration. It is moving fast — over 1,200 commits since mid-March and I use it daily. But it needs more hands. Here is what it is, where it is going, and how you can help. What Rune does Rune sits between your messaging channels (CLI, WebChat, API) and your model providers (OpenAI, Anthropic, Azure AI Foundry, Azure OpenAI). It adds the runtime layer that every serious agent deployment needs: Durable sessions — survive restarts, crashes, redeployments. Backed by PostgreSQL, SQLite, or Azure Cosmos DB. Tool call approval workflows — agents propose actions, operators approve or reject. Every decision is logged. Semantic memory and retrieval — context that persists across conversations. Provider routing — switch models per task, failover between pro