How MapleOS works
MapleOS behaves like a desktop OS with a start surface, windows, apps, files, and deep links. The goal is simple: let people move through real workflows without hopping between disconnected products.
Start menu and launcher
Browse programs by category, search quickly, and open what you need without losing orientation.
Windowed apps
Run multiple apps side by side so chat, files, notes, and tools can support one another in view.
VFS and files
Use File Explorer as the shared layer for project materials, local-first work, and explicit file access.
Deep links
Open programs directly with stable links like /desktop/start?open=id when you want fast entry into a task.
A typical MapleOS workflow
- Open from the desktop. Launch an app from the start menu or jump in with a deep link.
- Keep context visible. Place File Explorer, Office tools, AI Chat, or projects in separate windows.
- Grant only what is needed. If AI needs context, you can choose knowledge libraries, memory, or access controls deliberately.
- Turn patterns into workflows. When a task becomes repeatable, capture it with Blueprints and run it again safely.