# A native agent workspace that stays close to the GPU.

MAO is built as a desktop-native Rust application and renders its spatial workspace with GPUI, the GPU-accelerated UI framework behind Zed. That matters when your canvas contains real terminals, not just static boxes.

## GPU-rendered by GPUI

The canvas uses GPUI’s GPU-accelerated rendering model. Pan, zoom, arrange, and inspect the work from a native surface designed for spatial interaction.

## Native on every supported desktop

MAO is built for macOS, Windows, and Linux rather than asking a browser tab to imitate a development environment.

## Designed for dense work

A coding workflow can include many terminals, notes, files, drawings, portals, and connections. Native GPU rendering gives MAO the right foundation to keep that workspace usable.

## Local by default

Your workspace state is local JSON and Markdown, and each agent keeps its own provider login. The visual workspace is yours to keep and reopen.

## Frequently asked questions

### Is MAO an Electron app?

No. MAO is a desktop-native Rust application, not a browser wrapper, and its canvas is rendered on the GPU with GPUI, the framework behind Zed.

### Does MAO run on Linux?

Yes. MAO runs natively on Linux x86_64 under Wayland or X11, on macOS on Apple silicon and Intel, and on Windows x86_64.

### Does MAO stay responsive with many terminals open?

MAO skips work for what you cannot see: terminals that are off screen are not redrawn, and off-screen browser and device portals release their frames. When you zoom out, nodes collapse into compact status cards.

### Can I back up a MAO workspace?

Yes. In MAO's Settings, **Backups** writes a local **.mao-backup** archive with **Back up now**, or automatically once you turn on **Automatic backups**, and **Restore from file…** restores one as a new workspace. Worktrees, provider accounts and credentials are not part of a backup.

Source: https://trymao.dev/native-gpu-agent-workspace