MORATUS Desktop
MORATUS Desktop is the Windows version of the web app. It uses the same account, the same models, and the same memory. The key difference: chats and generated files stay on your own computer, and the agent works directly in the folders you approve.
Desktop is an agent that reads and edits your files, produces documents, runs commands in the terminal, and uses the browser in the side panel and, when needed, the Windows desktop. You see every step in the chat; you're asked to approve critical operations, and file changes can be undone.
Architecture
| Component | What it does | Where it runs |
|---|---|---|
| Electron shell | The window, system tray, menus, sign-in handoff to the system browser, and opening files. | Your computer |
| Local runtime | Serves the interface; writes chats, the library, and attachments to disk; forwards shared API requests; runs file tools. | Your computer |
| Interface | The same React code as Web. It has no Node access and talks to the local layer through a narrow bridge. | Your computer |
| Agent server | Runs model steps. Model provider keys are never included in the app package. | MORATUS servers |
| MORATUS API | Sign-in, model routing, billing, memory, scheduled tasks, and connector operations. | MORATUS servers |
How Desktop differs from Web
| Topic | Web | Desktop |
|---|---|---|
| Chat history | In your account; available from every device | On your computer's disk; not shown on other devices |
| Generated files | Private storage and the Library | The working folder, or Documents\Moratus |
| File tools | Run on the server | Run on your computer, in the local runtime |
| Working with folders | — | Directly in the folders you approve |
| Approval modes and checkpoints | — | Available |
| Browser, terminal, and computer control | — | In the side panel and on the desktop |
| Models | Fast, Expert, Auto | Fast, Expert, Apex, Auto |
| Account, credits, memory, projects, preferences | Shared | Shared |
When to use Desktop
- When you want to work directly with the files and folders on your computer: updating reports, editing spreadsheets, producing documents.
- For work that needs a terminal, such as coding, tests, builds, and development servers.
- When you want steps carried out on a website or in a desktop app (see Using the browser and Computer control (Computer Use)).
- When you want your chats and generated files to stay on your own disk (see Where your data lives).
A typical Desktop workflow
- Open Desktop and choose the folder you'll work in from the folder menu above the composer.
- If it's the first time you connect the folder, approve the trust dialog (see Working with folders and trust).
- Write the task, for example “Update the Q3 growth report and prepare a short Word summary for leadership.”
- The agent reads the files, keeps a to-do list for multi-step work, and shows every tool use as its own step in the chat. At steps that need approval, it waits for you.
- Review the result in the side panel's preview. If something isn't right, ask for changes or undo the response (see Checkpoints (undo)).
Frequently asked questions
- Do I need a separate account for Desktop? No. You sign in with the account you use on Web; your credits, memory, projects, and preferences are the same.
- Do my Desktop chats show up on Web? No. Desktop chats are stored on your computer and don't appear on other devices (see Where your data lives).
- Do I need an internet connection? Yes. Even though file tools run on your computer, model steps run on the agent server; without a connection the agent can't work.
- Which operating system does Desktop run on? MORATUS Desktop is the Windows version of the web app.