Product roadmap
A living view of shipped capabilities, approved development, and the integrations we are researching. Priority expresses sequence, not a promised date.
Available in published Conduit releases, within the documented compatibility gates.
Check for stable Conduit releases and guide users through a safe update from Home.
Shipped in v0.6.0. The update flow shows the running version, asks before making changes, verifies supported standalone downloads, and preserves the existing installation when an update fails.
Keep canonical workflow state in a project-owned local Turso database.
Conduit persists migrations, runs, results, recovery identity, and related workflow records in local state.db storage. Platform and standalone support remains limited to the combinations covered by release validation.
Use one structured assignment and response contract across supported coding harnesses.
Conduit separates its provider-independent protocol from native harness transport, normalizes runtime events, and validates authoritative final responses. Native adapters remain version and capability gated; this does not claim every provider version is validated.
Preserve verifiable role work across interrupted runs and resume only compatible work.
Shipped in v0.7.0. Conduit records workspace identity and Git lineage, retains recoverable work, and fails closed when a package, commit, assignment, repository, workspace, or lease cannot be verified.
Route bounded review corrections and promote completed work only after approval.
Shipped in v0.7.0. Reviewer findings can return to the owning role for bounded correction, and a run completes only after an approved verdict and verified fast-forward promotion.
No items match these filters.
Approved work moving through implementation and verification.
Carry verified lessons between independent agent runs without replaying raw transcripts.
The planned implementation keeps Turso as the canonical source of truth, uses Memvid as the default recoverable local index, and allows a configurable Hindsight adapter. Communication stays provider-independent, and retrieved knowledge must remain bounded, evidence-backed, and invalidated when its sources change.
Depends onLocal persistence, Universal agent communication, Memory lifecycle and provider implementation
No items match these filters.
Exploration, contract design, and scope validation before development.
Connect planned Conduit work with Linear issues without weakening local feature contracts.
Research is focused on authorization, issue mapping, synchronization boundaries, and a provider contract that keeps remote state explicit.
Support Jira-backed planning while preserving Conduit's review and ownership gates.
Planning covers deployment variants, authentication, field mapping, and how Jira workflows translate into Conduit lifecycle states.
Explore a predictable bridge between Asana tasks and Conduit feature packets.
Research will begin after the higher-priority provider contracts establish a reusable integration boundary.
Depends onRemote provider contract research
Explore ClickUp task mapping for teams planning agent work outside the repository.
The research phase will assess workspace structure, custom fields, authentication, and compatibility with the shared provider boundary.
Depends onRemote provider contract research
No items match these filters.
Shipped items describe released capabilities within their documented compatibility gates. Planned order and scope may change as research develops; phases do not commit to delivery dates.