Sovereign Ai Sdk

Sovereign AI SDK

The **Sovereign AI SDK** — an embeddable `createAgent()` agent-loop engine (open-core, MIT: [`@yevgetman/sov-sdk`](packages/sdk) + [`@yevgetman/sov-protocol`](packages/protocol)) — together with the runtime and Claude-Code-style TUI harness built on top of it (TypeScript on Bun, async-generator turn loop, `Tool` factory with fail-closed defaults, content-block messages) with a Hermes-pattern learning layer on top (persistent memory, trajectory capture, background review).

This is **runtime code**. The business data it operates against lives in a separate repo: `~/code/sovereign-ai-docs/`. This repo reads that one as a *harness bundle* and never writes to business-scope files; runtime state lives under `$HARNESS_HOME` (default `~/.harness`) unless a later phase introduces explicit bundle-state writers.

Surfaces

The same runtime drives several run modes — pick by how you want to reach it:

• Local TUI (sov) — the default. The Go Bubble Tea client backed by a per-invocation loopback server: interactive chat in your terminal. See usage › Quick Start.
• Headless line driver (sov drive) — stdin/stdout, no TTY: pipe a prompt in, read events out. For scripting, semantic tests, and CI. See usage › CLI Subcommands.
• Machine runner (sov run --json --stdin) — one prompt from all stdin, JSONL events out. For harness adapters that need a stable machine contract rather than the human drive transcript.
• OpenAI-compatible API (sov serve) — a drop-in OpenAI HTTP backend (Open WebUI, LibreChat, the openai SDKs). Stateless completions. See usage › OpenAI-compatible HTTP API.
• Secure remote gateway (sov gateway) — the harness's rich native HTTP+SSE protocol exposed off-loopback with bearer auth: turns, streaming, tool events, permission prompts, sl