Product roadmap
A living view of approved development and the integrations we are researching. Priority expresses sequence, not a promised date.
Approved work moving through implementation and verification.
Check for stable Conduit releases and guide users through a safe update from Home.
The update flow will show the running version, ask before making changes, verify standalone downloads, and preserve the existing installation when an update fails.
Give roles bounded, evidence-backed repository context and reliable handoffs.
Memory stays local and project-scoped, ties every observation to source evidence, and invalidates context when that evidence changes.
Depends onLocal persistence foundation
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.
Roadmap order and scope may change as research develops. Phases describe the current planning state and do not commit to delivery dates.