> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mibyanai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mibyan Desktop

> The complete guide to Mibyan Desktop: install, chat and Dev modes, workspace panes, connections, automation, settings, shortcuts, and troubleshooting

<img alt="Mibyan" className="block dark:hidden" width="220" src="https://mintcdn.com/nuqtaai/-NT8N9EMsatx6ezl/logo/mibyan-wordmark-light.png?fit=max&auto=format&n=-NT8N9EMsatx6ezl&q=85&s=bb7709764a04b79968760a98e8b546a3" data-path="logo/mibyan-wordmark-light.png" />

<img alt="Mibyan" className="hidden dark:block" width="220" src="https://mintcdn.com/nuqtaai/-NT8N9EMsatx6ezl/logo/mibyan-wordmark-dark.png?fit=max&auto=format&n=-NT8N9EMsatx6ezl&q=85&s=b6eedaf9d1462355a7d45a7eaa7736f7" data-path="logo/mibyan-wordmark-dark.png" />

**Mibyan Desktop** is the Mibyan agent as a native app for macOS, Windows, and Linux. You give it a goal, not the steps. It plans the work, picks the tools, works **inside your folders**, shows the result beside the conversation, and stops to ask before anything sensitive.

It is the same agent, skills, memory, and conversation history as the Mibyan command line and messaging gateway, in a real window with a file browser, terminals, a live preview, an in-app browser, voice, and a settings UI. No terminal is required.

<Note>
  Mibyan Desktop is a product of **Nuqta Technology LLC**. The public Mac release is opening through an early-access list on the Mibyan Desktop page. Installers exist for macOS, Windows, and Linux.
</Note>

## At a glance

| | |
| - | - |
| **Platforms** | macOS 12 or later (universal DMG and zip), Windows (NSIS installer and MSI), Linux (AppImage, `.deb`, `.rpm`) |
| **Account** | A Mibyan account. There is no guest mode, and your account session is never stored inside your projects |
| **Default model** | Mibyan 4.1 through your account, or your own provider and API key |
| **Where the agent runs** | On this computer, on a remote gateway, over SSH, or on Mibyan Cloud |
| **Languages** | Arabic and English interface and conversations, right-to-left supported |
| **Links** | The app registers the `mibyan://` link scheme, used for example to add an MCP server from a link |

## How it is built

Three parts, each in charge of one thing:

```mermaid theme={null}
flowchart LR
  subgraph Machine["Your computer"]
    E["Electron shell<br/>windows, files, git,<br/>install, updates"]
    R["Interface<br/>chat, panes, settings"]
  end
  B["Agent backend (gateway)<br/>sessions, tools, model calls, streaming"]
  E <--> R
  R <-- "live connection" --> B
  B --> L["Local backend<br/>on this computer"]
  B --> RM["Remote gateway<br/>LAN, VPN, internet"]
  B --> SS["SSH host"]
  B --> CL["Mibyan Cloud agent"]
```

* The **shell** owns your machine: windows, native files and git, installing, and updating.
* The **interface** owns what you see: navigation, layout, and presentation.
* The **agent backend** owns the work: sessions, tools, model calls, and streaming. Because of this, anything another Mibyan surface can change stays consistent everywhere.

The desktop app and the backend update on separate schedules, so you may see two version numbers. The app tells you clearly when one is behind the other (see [Install and update](/products/desktop-guide/install-and-update)).

## Your first launch

```mermaid theme={null}
flowchart TD
  A["Open Mibyan Desktop"] --> B["Sign in with your Mibyan account"]
  B --> C{"A backend is available?"}
  C -- "No" --> D["Choose: connect to an existing Mibyan<br/>or install locally"]
  D --> E["One-time install<br/>runs stage by stage"]
  C -- "Yes" --> F["Choose how Mibyan runs"]
  E --> F
  F --> G["Mibyan account, your own API key,<br/>or a local model"]
  G --> H["Pick a default model"]
  H --> I["Begin"]
```

<Steps>
  <Step title="Sign in">
    Sign in or create a Mibyan account. The same account works across Chat, Dev, the web, and the mobile app.
  </Step>

  <Step title="Choose a backend">
    If Desktop cannot find a usable runtime or a saved remote connection, it asks whether to **connect to an existing Mibyan** (a gateway you already run) or **install Mibyan locally** on this computer.
  </Step>

  <Step title="Let the one-time install finish">
    A local install downloads dependencies and configures the machine, with each step shown. It happens once. Later launches skip it.
  </Step>

  <Step title="Choose how Mibyan runs">
    Use your **Mibyan account** directly, bring your **own provider or API key** (OpenRouter, OpenAI, Gemini, xAI, Fireworks, and others), or connect a **local model** running on this device (for example Ollama, LM Studio, vLLM, or llama.cpp).
  </Step>

  <Step title="Pick a default model and begin">
    The default model can be changed any time from the model picker or in Settings.
  </Step>
</Steps>

## A tour of the window

```mermaid theme={null}
flowchart LR
  subgraph TB["Titlebar: sidebars, search, settings, memory graph, HUD, layout"]
  end
  subgraph LS["Left sidebar"]
    S1["New chat"]
    S2["Pinned and recent chats"]
    S3["Projects and worktrees"]
    S4["Capabilities, Connections,<br/>Artifacts, Scheduled jobs"]
  end
  subgraph CH["Center"]
    C1["Conversation"]
    C2["Composer"]
  end
  subgraph RS["Right sidebar"]
    R1["File system"]
    R2["Review (git changes)"]
    R3["Terminals"]
    R4["Preview and browser"]
  end
  subgraph SB["Status bar: model, approvals, gateway, agents, cron, context meter"]
  end
  TB --- LS
  LS --- CH
  CH --- RS
  RS --- SB
```

| Area | What lives there |
| - | - |
| **Titlebar** | Show or hide each sidebar, search chats and actions, the settings button, the memory graph, HUD mode, and the layout editor |
| **Left sidebar** | Your chats (pinned, recent, grouped by project or as one list), projects, and shortcuts to Capabilities, Connections, Artifacts, and Scheduled jobs |
| **Center** | The conversation with streaming answers and live tool activity, and the composer |
| **Right sidebar** | The file browser, the review pane for git changes, terminals, and the preview and in-app browser |
| **Status bar** | The current model, approval mode, gateway health, running agents, cron, webhooks, context meter, timers, and version. You choose what it shows |

## Chat and Dev

Desktop has two modes, switched from the top of the app:

<CardGroup cols={2}>
  <Card title="Chat" icon="comments">
    Think it through. Ask questions, draft, research, and brainstorm. The intro asks "How can I help?".
  </Card>

  <Card title="Dev" icon="code">
    Get it done. Open or create a **project**, and the agent works with its files, terminal, previews, and database tools. The intro asks "What would you like to build?", with recent projects, **Open project**, **New project**, and **Terminal**.
  </Card>
</CardGroup>

## What you can do

<CardGroup cols={2}>
  <Card title="Chat and projects" icon="folder-tree" href="/products/desktop-guide/chat-and-projects">
    Sessions, projects and worktrees, the composer, attachments, voice, approvals, checkpoints, and slash commands.
  </Card>

  <Card title="Workspace and panes" icon="table-columns" href="/products/desktop-guide/workspace">
    Files, review, terminals, live preview, in-app browser, artifacts, layouts, HUD, quick entry, the memory graph, and themes.
  </Card>

  <Card title="Connections and profiles" icon="network-wired" href="/products/desktop-guide/connections-and-profiles">
    Local, remote, SSH, and Mibyan Cloud gateways, plus profiles with their own config, skills, and persona.
  </Card>

  <Card title="Skills, tools, and automation" icon="bolt" href="/products/desktop-guide/skills-and-automation">
    Skills and the Skills Hub, toolsets, MCP servers, plugins, scheduled jobs, webhooks, and messaging platforms.
  </Card>

  <Card title="Settings reference" icon="sliders" href="/products/desktop-guide/settings">
    Every settings page: model, providers, usage, appearance, notifications, gateways, keys, and more.
  </Card>

  <Card title="Shortcuts and commands" icon="keyboard" href="/products/desktop-guide/shortcuts-and-commands">
    All keyboard shortcuts and every slash command.
  </Card>

  <Card title="Install and update" icon="download" href="/products/desktop-guide/install-and-update">
    Install paths, the first-launch install, updates, and version skew.
  </Card>

  <Card title="Troubleshooting" icon="life-ring" href="/products/desktop-guide/troubleshooting">
    Fixes for startup, connection, credits, voice, previews, and updates, plus how to send diagnostics.
  </Card>
</CardGroup>

## Safety in one place

* **Approvals.** Choose Manual, Smart, or Off. Manual asks before actions that need approval.
* **Sensitive input goes only to your agent.** A sudo password or a secret is sent only to your local agent, and is never stored in the transcript.
* **Checkpoints.** You can restore the conversation to an earlier prompt and rerun from there.
* **Deleted files go to the Trash**, not straight to oblivion.
* **Diagnostics are opt-in and redacted.** Sending a debug bundle shows exactly what it includes first.

Read the details in [Chat and projects](/products/desktop-guide/chat-and-projects#approvals-and-safety).

## The command line

The same agent works in the terminal. If you already have the Mibyan CLI, `mibyan desktop` builds and launches the app against your existing install, with the same config, keys, sessions, and skills.

| Command | What it does |
| - | - |
| `mibyan` | Start an interactive conversation in the terminal |
| `mibyan desktop` | Build and launch Mibyan Desktop |
| `mibyan model` | Choose your model provider and model |
| `mibyan tools` | Choose which tools are enabled |
| `mibyan gateway` | Start the messaging gateway to talk to the agent from chat apps |
| `mibyan setup` | Run the full setup wizard |
| `mibyan update` | Update to the latest version |
| `mibyan doctor` | Diagnose problems |
| `mibyan debug share` | Create a redacted debug report |

<Card title="Next: install and update" icon="download" horizontal href="/products/desktop-guide/install-and-update">
  Get Mibyan Desktop running, and keep the app and backend in step.
</Card>