Desktop capabilities
Jingle status for launcher, file search, quicklinks, snippets, clipboard, window management, and system commands.
A mature desktop command center starts with high-frequency local actions. Extensions and AI sit above that foundation, but the base layer needs reliable launch, search, quicklinks, snippets, clipboard history, notes, window management, and system commands.
Capability Status
| Capability | Status | Target |
|---|---|---|
| App launch | Core buildout | Fast search, keyboard launch, recent usage, and result ranking |
| Command search | Core buildout | Search app commands, extension commands, agent tools, and local actions from one surface |
| File search | Planned | Search files, open files, copy paths, and run extension actions on files |
| Quicklinks | Planned | Saved URLs, templated parameters, dynamic queries, and team sharing |
| Snippets | Planned | Text snippets, variables, dates, clipboard input, and expansion across apps |
| Clipboard history | Planned | Searchable history, pinned items, privacy filters, and local-first storage |
| Quick notes | Planned | Floating notes, temporary capture, Markdown, search, and desktop sync |
| Window management | Planned | Move windows, resize windows, layout shortcuts, and multi-display state |
| System commands | Planned | Calculator, emoji, translator, calendar, Focus, script commands, sleep, lock, and other frequent local tools |
Product Boundary
- Desktop capabilities belong to the Jingle host and should not be reimplemented by each extension.
- Extensions can declare commands, actions, and file handling, but the host owns search indexing, hotkeys, clipboard permission, window permission, and system permission.
- Sensitive surfaces such as clipboard history, notes, and file search are local-first by default and need visible privacy controls.
Impact on Extension APIs
Desktop capabilities shape extension API boundaries:
- File search requires commands to receive file paths, MIME types, and selection context.
- Quicklinks require commands to support parameter templates, defaults, and readable input descriptions.
- Snippets and clipboard require clear read/write boundaries and explicit authorization where needed.
- Window management and system commands require a strict split between normal extension capabilities and host-level capabilities.
As these contracts stabilize, they will be added to the API reference and extension model docs.