OpenMuse starts with a simple idea: an application should not force everyone into one fixed way of working. You can split, move, and swap panels. The editor, file viewer, and AI agent supply separate capabilities that you can combine.
Desktop, browser, and mobile
The desktop client provides a flexible layout and local capabilities. The browser client opens directly with projects, an editor, and DSH. On mobile, you can find devices on the same account, see DSH task status, and continue a conversation. Each device has a distinct role.
Plugins define the boundary
The OpenMuse Host owns windows, resource authorization, plugin lifecycle, and permissions. The Helix editor, file viewer, and DSH agent join as separate plugins. We are developing public plugin protocols, manifests, and SDKs so more capabilities can join through the same boundary.
Open and inspectable
Source, licenses, and dependency origins are public. Plugin access to resources follows explicit permission boundaries. Explore the GitHub repository for code and design documents, or visit the Plugin Market to see current plugins.