Major announcement
Conduit v0.5.1: a durable local foundation
Conduit now runs its project workflows on embedded local persistence, with safer recovery and cross-platform release checks.
Conduit v0.5.1 completes a major piece of groundwork: durable, local-first state for long-running agent work.
Local persistence without a cloud dependency
Project workflows now use an embedded Turso database owned by the Conduit process. Drafts, refinement revisions, run events, reviews, and recovery metadata stay local to the repository, while reusable global profiles live in the platform application-data directory.
The storage boundary is deliberately narrow. Spawned coding agents never receive database handles or connection details, and provider credentials remain in the operating-system vault or encrypted fallback rather than entering project state.
Safer startup and recovery
The release adds ordered, checksummed migrations, pre-migration backups, legacy state import, and a project lock that prevents two Conduit processes from owning the same project database. Transactions stay short and no database lock is held while an agent runs.
v0.5.1 also tightens shutdown behavior so terminal exits release storage locks cleanly, and makes release verification work consistently across supported platforms.
Built for what comes next
This persistence layer is the foundation for bounded agent memory and evidence-backed handoffs. Those capabilities are now in development, alongside a guided self-update experience. You can follow both on the public roadmap.
Install the latest standalone release from GitHub Releases, or read the documentation for setup and supported platforms.