Skip to main content
Moxus Desktop is Moxus’s native AI programming workspace. It brings project sessions, Agent activity, terminals, file changes, and generated deliverables together in one desktop app. Unlike Cursor, Claude Code, or Codex, Moxus Desktop does not require you to enter a Moxus API key manually. Sign in to your Moxus account and select any model available to that account.
Download the current macOS or Windows installer from the Moxus Desktop download page. The app checks for updates at startup and in Settings → About.

​
What you can do

Work by project

Open a local folder and keep multiple independent AI sessions in the same project.

Use general sessions

Start a task without opening a project. The work stays in a separate Moxus workspace.

Follow execution

View messages, commands, approvals, terminal activity, and file changes while a task runs.

Review results in context

Preview files, diffs, PDFs, images, videos, and local web pages beside the conversation.

Search the live web

Search for current information and review the search process and clickable sources.

Manage multiple sessions

Search, rename, pin, or archive sessions to keep project work organized.

​
Before you start

You need:
  • A Moxus account that can sign in to the desktop app.
  • Account balance available for the target model.
  • An installer matching your operating system.
Normal use of Moxus Desktop does not require creating or copying an API key. API keys are used for API calls and third-party clients.

​
First use

1

Install and open Moxus Desktop

Download the installer for your operating system, complete the installation, and open the app.
2

Sign in to Moxus

Sign in with the same account you use on the Moxus website. The app will load the models available to that account.
3

Choose a project or create a general session

Select a local project folder for an existing codebase. Create a general session for ideas, planning, or tasks outside a project.
4

Select a model and send a task

Select a model in the input area, describe the work, and send it. The workspace streams the response and Agent activity.
5

Review changes and deliverables

Before keeping or using the result, inspect file changes, terminal output, previews, and generated deliverables from the conversation or right panel.

​
Projects, sessions, and general workspaces

​
Project workspaces

A project workspace is linked to the local folder you select. Use it for codebase development, feature changes, troubleshooting, or tasks that need existing files. A project can contain multiple sessions, so each task keeps its own conversation and context.

​
General sessions

General sessions do not require a local project. They are useful for planning, research, short scripts, document work, or validating an idea before entering a codebase. General-session work is stored in a separate Moxus workspace and is not written into a project folder by default.

​
Independent sessions

Switching projects or sessions does not mix their conversation histories. A running session can continue while you view another one. When you reopen the app, recoverable history is reloaded when available. The sidebar supports searching, renaming, pinning, and archiving sessions; archiving hides a session from the regular list without deleting it.

​
Queued follow-ups

You can enter follow-up requests while a task is running and queue them for sending. Edit queued messages before they are sent when you need to add constraints, change direction, or provide the next step.

​
How Agent activity is shown

In addition to the final answer, a request may show: Review changes in the diff and preview panels. Pay particular attention to approvals involving projects, files, or running services.
When a task requires it, Moxus Desktop can read and modify content in the opened workspace. Confirm the selected folder and review every approval and file change. Unless your organization permits it, do not place credentials, production keys, or other sensitive information in prompts or project files.

​
Files, terminals, and deliverables

​
File review and previews

The right panel can show a file tree and preview common text files, images, Markdown, PDFs, videos, diffs, and local web pages. After reviewing a turn’s file changes, you can apply or roll them back. DOCX, XLSX, PPTX, and other Office files usually open in the operating system’s default app.

​
Session terminals

Terminal tabs belong to the current session. Command output and running processes stay associated with the task that created them and do not mix with other projects or conversations.

​
Generated deliverables

Moxus Desktop can generate document deliverables such as PPTX, DOCX, XLSX, and PDF. Generated files appear in the conversation as artifact cards and can be opened, downloaded, or shown in their folder. Charts and SVG diagrams can appear directly in the conversation; PDFs and videos can be previewed in the app, while Office files usually open in the system default app.

​
Models and billing

The Desktop model list is determined by your Moxus account and the models available to its group. A model may be missing because it is not enabled for Desktop or because your account group does not have access. Requests consume your Moxus account balance. See Models and pricing for current prices and Dashboard and usage for request records. Desktop also keeps local account records for completed desktop requests for reference.

​
Updates

Moxus Desktop checks for updates at launch, after remaining open for a while, and when the window returns to the foreground. You can also check manually from the sidebar update entry or in Settings → About. Install an available update in the app and restart as prompted.

​
Frequently asked questions

Confirm that the same Moxus account can sign in on the website, then check your network and try again. If the website works but the desktop app does not, include the error and app version when contacting support.
Desktop only shows models enabled for your account group and supported by Desktop. Check Models and pricing first. If the model exists there but is missing in Desktop, provide the full model name to your administrator.
Open the approval row and read the requested operation before continuing. Rejecting an approval may stop the current step; enter a new request if you want the task completed another way.
Open the artifact card in the message that generated the file, then use Open, Download, or Show in folder. Files created in a project can also be found in the project tree and change list.
Check the latest process information and terminal output, then open Dashboard and usage to confirm whether the request reached Moxus, which model was used, and whether an API error was recorded.