Postgres-native agent-loop runtime in Rust. Invoke an LLM agent and its tool dispatch from SQL like a stored procedure — the agent reads and writes your tables directly, with a small trait-based kernel and everything else as a plugin.
Multi-model LLM debate and second-opinion validation. Broadcasts a prompt to several models — HTTP providers or local CLIs — has them argue over N rounds, and returns a synthesized answer plus an agreement/disagreement report.
The hands-on follow-up to the why-I-built-it post. Real commands, real outputs: install Stele, wire it into your agent, store artifacts with citations, supersede facts, time-travel with as_of, stash oversized tool output, and run recall through two strategies. Five minutes to install, the rest is just typing.
I said the implementation needed another quarter. Three weeks later I’d shipped Stele — source-backed, time-traveling, sovereign agent memory that plugs into seven coding assistants. What it does, the three goals driving it, what’s solid on main, and what’s still wobbly. The honest version, including the parts that aren’t built yet.
Local-first MCP server that indexes code and docs into Postgres + pgvector for hybrid retrieval by LLM coding clients.