Runne Engine

Runne Engine is the local-first, provider-neutral Rust runtime that executes AI coding agent workflows. It is the execution core of the Runne desktop command center, deliberately separated from the chat UI, the CLI, and the model providers.

The runtime owns the state

The runtime is the single owner of authoritative state. The CLI and the Tauri desktop host never touch state directly — they work with the runtime only through runtime-client and an authenticated canonical API. The Vue renderer receives only typed DTOs over Tauri IPC; it never sees raw runtime internals.

The chat window is a view. The runtime is the truth.

What the runtime does

A TaskRun is the independent unit of execution. The runtime takes a request, forms a TaskRun, drives its lifecycle, calls models, executes tools, applies policy, manages permissions and approvals, isolates the workspace, records events, enforces budgets, runs verification, saves state, and recovers after crashes — and exposes one API to several clients at once.

Provider-neutral

The runtime routes model calls through a provider-agnostic gateway. Replay/SSE, the bundled OpenAI effect, and the exact external effects for OpenAI and DeepSeek are implemented. Live provider/platform qualification, candidate and release qualification, and enrollment are separate, still-open gates — the presence of code is not itself a production claim.

Two ways to run

• Bundled desktop supervisor — the desktop app starts a bundled protected supervisor internally; no separate runned is pre-started (pnpm --filter @runne/desktop stage:bundled-daemon + tauri dev).
• External runtime — runned runs as a standalone daemon; the desktop app and the CLI connect to it (runned + tauri dev -- -- --external-runtime).

Repository shape

The runtime lives in the Runne monorepo:

• crates/ — 48 Rust crates (runtime core, daemon, providers, store, security, platform, MCP, tools, plugin host, CLI).
• local-engine/ — the bundled local-inference engine (GGUF / llama-cpp-2, CPU profile), its own Cargo workspace and lockfile.
• apps/desktop — the Tauri host.
• docs/ — the target-architecture and security contracts the runtime implements.

Related

• Installation — build, install, and run the engine.
• Concepts — TaskRun, attempts, durable state, grants, budgets.
• Architecture — control/execution planes and the crate map.
• CLI — the runne and runned binaries.
• Security — capability grants, sandbox, credentials.
• Principles — the shared commitments.