Command center
Launch commands, switch context, and operate repeat workflows without leaving the keyboard.
Jingle / 金狗
A faster way to work with your desktop.
Jingle is a command center for launching workflows, connecting extensions, and giving AI the context it needs to help without taking over your workspace.
Search apps, commands, files, and agents⌘K
Recent commands
Open project notes
Create launch plan
Review today's changes
Extension actions
Run connected workflows from one surface instead of switching apps.
AI with context
Attach files, memories, and tools while keeping approval visible.
Local context readyReturn to run
Features
Everything starts from the command surface.
Built for repeated work: quick to invoke, easy to scan, and explicit about what runs.
Extension store
Connect apps, run extension views, and bring provider actions into one predictable surface.
AI workspace
Give AI workflows the right files, tools, memories, and approval boundaries.
Local knowledge
Keep working context local-first, searchable, editable, and visible to the user.
Workflow
Find, act, and hand off in one place.
Find anything
Search, open, and act across apps.
Do the work
Run extension commands with native-feeling views.
Hand off safely
Let agents use approved tools and local context.
Extensions
Connect the tools your work already depends on.
GHDeveloper preview
GitHub
Issues, pull requests, notifications, and repository workflows.
NDeveloper preview
Notion
Pages, databases, capture flows, and workspace search.
RBuilt-in
Reminders
Native reminders, due dates, quick capture, and local task flows.
Roadmap
Jingle's desktop platform roadmap.
Jingle is building a desktop workflow platform around launcher commands, extensions, AI tools, team distribution, and cross-device sync. The roadmap presents product progress and future direction by stage.
Core buildout
Launcher and file search
App launch, command search, file search, action panels, aliases, and hotkeys are the base of the desktop surface.
Developer preview
Extension ecosystem and store
Extension packages, runtime SDK, developer tooling, review, publishing, and public or private distribution need one complete loop.
Preview
AI commands and tool calls
AI commands call extension tools, explain inputs, show approvals, and leave inspectable results.
Planned
Team sharing
Shared quicklinks, snippets, private extensions, member permissions, and organization settings will move as part of the team edition.
Planned
Windows, clipboard, and system commands
Window management, clipboard history, snippet expansion, system commands, calculator, and emoji need native-level ergonomics.
In development
Connected accounts and OAuth
Public integrations need platform-owned OAuth, callbacks, token refresh, revoke, and a standard Connect UI.
Planned
Migration, import, and sync
Settings, extensions, quicklinks, snippets, history, and local knowledge need import, backup, and sync paths.
Ongoing
Security, privacy, and governance
Credential boundaries, permission display, extension review, redacted reporting, and compatibility policy decide whether the platform can open up long term.
Trust
Designed for user-controlled automation.
Credential boundaries
Sensitive credentials belong to host-managed secure storage, not plain extension settings.
User control
Users should understand which context is local, which is shared, and what agents can access.
Inspectable state
Connections, memories, and tool permissions are designed as inspectable product surfaces.
Explore the Jingle product roadmap.
See desktop platform capabilities, upcoming direction, and developer resources.