Platform roadmap
Capability stages, availability, and direction for Jingle Developers.
The Jingle Developers roadmap covers extension packages, runtime APIs, connected accounts, OAuth, AI tools, distribution, and team collaboration. Each capability is marked by release stage so extension authors can see which contracts are available today and which areas to follow next.
Capability Matrix
| Capability area | Stage | Direction |
|---|---|---|
| App launch and command search | Core buildout | File search, aliases, hotkeys, recent items, ranking, and consistent actions across sources |
| Extension package model | Preview | Templates, scaffolding, packaging checks, compatibility policy, and public publishing |
| Extension UI components | Preview | Behavior consistency, accessibility, screenshot tests, visual guidelines, and cross-version contracts |
| Extension store | In development | Public directory, review queue, signing, updates, ratings, install/uninstall, and private distribution |
| Connected accounts | Preview | Standard Connect UI, provider registry, connection diagnostics, and permission display |
| OAuth / PKCE | In development | Authorization page, callback state validation, token exchange, refresh, revoke, and secure storage loop |
| AI commands | Preview | AI command templates, context selection, approval replay, failure recovery, and explainable results |
| Agent tool calls | Preview | Schema-form approvals, parameter editing, tool permission policy, audit logs, and eval coverage |
| Team features | Planned | Organizations, members, shared quicklinks, private extensions, team settings, and permission governance |
| Clipboard, snippets, and notes | Planned | Clipboard history, snippet expansion, variables, quick notes, search, sync, and privacy filters |
| Window and system commands | Planned | Window management, system commands, calculator, emoji, translator, calendar, Focus, script commands, and high-frequency local tools |
| Migration and sync | Planned | Import, export, backup, theme/profile sync, cross-device sync, conflict handling, and local-first deletion semantics |
| Security and governance | Ongoing | Extension permission declarations, review, signing, redacted logs, crash reporting, and compatibility governance |
Developer boundaries
- Extension authors can rely on package, runtime SDK, connected account, and agent-tool capabilities marked as “Preview”.
- OAuth, public store submission, signing, updates, and large-scale third-party publishing will be provided through platform-owned flows.
- Accounts, OAuth, teams, store, and sync are managed by platform security boundaries; extensions do not directly store OAuth tokens or refresh tokens.
- Jingle's current roadmap focuses on desktop workflows. Cross-device sync targets desktop platforms and future explicitly supported surfaces.
Near-term priorities
- Stabilize extension packages, runtime SDK, connected accounts, and agent-tool boundaries.
- Build platform OAuth and the standard Connect UI so public providers such as GitHub and Notion can complete a real authorization loop.
- Build extension distribution: templates, packaging checks, private distribution, public directory, and review.
- Expand into team sharing, snippets and clipboard, window management, sync, and governance.