What is real.
What comes next.
No imaginary release dates and no feature theatre. The desktop core is here; the beta now focuses on stability, security and coherent workflows. AI Agents and commercial plans stay open until they deserve a clear answer.
Release hardening and product truth
Verify macOS and Windows packaging, updater manifests, download integrity and rollback behavior.
Continuously test Nexus permissions, credential use/reveal boundaries, invitations, sessions and MCP writes.
Finish the VS Code-inspired shell, density, typography, tabs, panels, copy behavior and keyboard navigation.
Keep public docs, MCP search, website copy and actual application behavior aligned.
Deeper MCP workflows
Broader permission-aware tools, clearer client setup, stronger approval detail and audit history. MCP is the automation surface that already exists, so it earns the next investment.
- • Better resource discovery and active-Nexus context
- • Granular read/write approval policies
- • More useful API and operational tool contracts
- • Clear client identity and revocation
AI Agents and plans
We are deciding whether built-in agents add meaningful value when many users will bring their own MCP client. We are also designing plans only after real beta usage shows which limits are fair.
The roadmap is a conversation
Tell us where the real friction is.
A reproducible workflow problem is more valuable than a hundred abstract feature votes.
Submit a feature request