Core buildout
Launcher, search, and actions
App launch, command search, action panels, hotkeys, recent usage, and result ranking are the base surface.
Next: file search, cross-source actions, aliases, hotkey management, and more stable ranking.
Roadmap
Jingle desktop platform roadmap
Jingle is building a desktop command platform for individuals and teams. This roadmap outlines the staged direction across command entry, extensions, AI, connected accounts, team collaboration, and platform governance.
Roadmap status
Roadmap phases describe product progress. Preview capabilities are ready for early extension development and private integrations, in-development areas are actively being built, and planned areas represent committed direction while experience and timing continue to evolve. Release timing is communicated through official release notes.
Planned
Files, snippets, and clipboard
File search, file actions, text snippets, variable expansion, clipboard history, and quick notes will become the local productivity layer.
Planned direction: privacy filters, local indexing, snippet variables, pinned history, search, floating notes, and sync strategy.
Developer preview
Extensions and system commands
Extension packages, command views, menu bar entries, no-view commands, and system capabilities form the extensible desktop layer.
Next: scaffolding, package checks, permission display, window management, script commands, calculator, emoji, translator, calendar, Focus, and other frequent local tools.
Preview
AI commands and agent tools
AI should read user-approved context and call extension tools inside visible approval boundaries.
Next: Quick AI, AI Command templates, context selection, AI profile, schema-form argument editing, failure recovery, result explanation, and evals.
In development
Store, publishing, and updates
The extension ecosystem needs a public directory, private distribution, review, signing, updates, withdrawal, and install experience.
In progress: publishing flow, review queue, package signing, version compatibility, update policy, and user-readable permission descriptions.
In development
Connected accounts and OAuth
Public providers such as GitHub and Notion should use platform-owned OAuth, callbacks, refresh, revoke, and secure storage.
In progress: provider registry, Connect UI, state validation, token exchange, refresh, revoke, and connection diagnostics.
Planned
Team sharing and sync
The team edition will cover shared quicklinks, snippets, private extensions, organization members, personal settings, and desktop sync.
Planned direction: organization permissions, audit, conflict handling, import/export, theme/profile sync, disable-sync controls, and local-first deletion semantics.
Ongoing
Security, privacy, and governance
Credential boundaries, permission display, extension review, redacted logs, and compatibility policy decide whether the platform can open up long term.
Ongoing work: permission model, review rules, redacted error reporting, compatibility matrix, and user-inspectable surfaces.
Platform principles
View developer roadmapJingle is focused on desktop workflows. Mobile apps are outside the current roadmap.
Account credentials are managed by the platform security boundary; extensions do not directly hold OAuth tokens or refresh tokens.
Sync follows local-first and explicit opt-in principles. Local ownership remains the default boundary.