> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mantle.chat/llms.txt
> Use this file to discover all available pages before exploring further.
# Web and desktop apps
> Use Mantle in a browser or install the macOS app for native notifications and local coding agents.
Mantle runs fully in a web browser on desktop and mobile devices. A native app is also available for macOS.
Windows, Linux, iOS, and Android native apps are planned. Until they are released, use the web app on those platforms.
## Install the macOS app
Go to [mantle.chat/downloads](https://mantle.chat/downloads). Mantle supports Apple Silicon and Intel Macs running
macOS 12 or later.
Most recent Macs use Apple Silicon. Choose the Intel build only if your Mac has an Intel processor.
Follow the macOS install prompt, then sign in with the same Mantle account.
Allow notifications if you want mentions, replies, and direct messages in Notification Center.
The app checks for updates and lets you restart when you are ready to install one. Mantle's macOS builds are signed and
notarized by Apple.
## Use a supported local coding agent
The macOS app can use supported coding tools installed on your Mac, including Codex, Claude Code, Cursor, OpenCode, and
Grok CLI. You sign in through the coding tool's official provider flow, and that provider's terms and usage rules
continue to apply.
Follow that tool's own setup and official sign-in instructions on your Mac.
In the macOS app, go to **Settings → Models → Local providers**.
Mantle checks whether the tool is installed and signed in. Follow the on-screen setup if it needs a path or login.
Once ready, turn the provider on. In Mantle's model picker, switch to **Local models** (the laptop button above
image generation) to see its models.
### Follow what the agent does
A local agent's reply shows its work as it happens, the same way for every agent:
* **Commands** show what ran and their output. Long output keeps its end, where results and errors usually are.
* **File changes** list each file with how many lines were added and removed, and open to the diff.
* **To-do lists** the agent keeps show each step as pending, in progress, or done.
* **Reasoning** the agent shares appears in its own collapsible step, apart from the answer.
* **Plans** from Plan mode appear as a plan, so it's clear nothing has changed yet.
### Sign in and keep an eye on limits
In the model picker's **Local models** list, an agent that can't run yet shows why, with what to do next: **Sign in**,
**Install**, or **Settings**. Codex signs in with ChatGPT in your browser and comes back to Mantle by itself. Claude
Code, Cursor, Grok, and OpenCode sign in through their own command, which Mantle opens in Terminal; when you come back
to Mantle it checks again. An agent with a newer version available shows **Update**.
Below the message box, a local chat shows the same status when its agent can't run, and otherwise how much of your Codex
or Claude subscription's 5-hour and weekly limits is left. It turns amber when a limit runs low.
### Choose the folder a chat works in
Below the message box, a local chat shows the folder its coding agent works in and that folder's git branch. Click it to
move the chat to a recent folder or choose another one, or to open the folder in Finder, an installed editor, or a
terminal. Each chat keeps its own folder, and a new chat starts in the folder you chose last. Moving a chat to another
folder starts the agent fresh there with the conversation so far. Channel and thread mentions keep using the default
folder from local provider settings.
In the sidebar, Mantle files each local chat in a workspace folder named after its project folder, and reuses a folder
that already has that name. A chat you move yourself, or take out of its folder, stays where you put it. Like the chats
in them, these folders are visible to everyone in the workspace.
### See what changed
To see what changed in a chat's folder since its last commit, open the folder menu below the message box and choose
**Show changes**. The Changes pane lists each changed, new, deleted, or renamed file with how many lines were added and
removed; pick a file to see its diff. It catches every change, however the agent made it, and reads again when a reply
finishes. Mantle reads the changes on your Mac with Git and never uploads them; Git must be installed, and the folder
must be a Git repository.
Each reply from a local agent that changed files ends with a line like **3 files changed +12 −4**; click it to see just
that reply's changes. The menu at the top of the pane switches between **Uncommitted**, the **Latest reply**, any of the
**Earlier replies**, and **This chat**, every reply's changes together. To tell a reply's changes apart from yours,
Mantle keeps a snapshot of the folder just before and just after each reply, in the folder's own repository under hidden
`refs/mantle` names that branches, history, and pushes leave alone. Snapshots stay on the Mac they were made on, so
replies show their changes only there. Mantle skips them when a reply would copy too much, like thousands of new files
or a large dataset, and a repository keeps those of its newest 1,000 replies.
To undo a reply, open its changes and choose **Undo these changes**. Mantle takes back only what that reply changed, so
your edits and later replies stay, and it changes nothing when a file the reply touched has changed since; it names the
file instead. **Redo** puts the changes back. Before either, Mantle keeps a snapshot of the folder as it was, and it
never touches your Git index, branches, or history.
### Choose what the agent may do
The access control beside **+** in the message box shows what the chat's agent may do, and changes it:
* **Read only**: the agent reads and answers, and changes nothing.
* **Ask first** (the default): it asks before it changes files or runs commands.
* **Edit automatically**: it edits files inside the folder without asking. Commands still ask.
* **Full access**: it runs anything without asking.
Edit automatically and Full access ask for your confirmation once per folder. If you decline, the chat stays at the
level that folder already allows. A new chat starts at the level you chose last, and Full access shows in amber.
To have the agent propose a plan before it changes anything, open **+** and turn on **Plan mode**. The plan arrives as
the reply; turn Plan mode off and ask it to go ahead when you're happy with it. Plan mode works with Claude Code, Codex,
and OpenCode.
### Answer requests and stop the agent
When the agent asks before it does something, the request appears above the message box of the chat it's working in,
with the exact command or the file changes as a diff, and the agent's reason when it gives one:
* **Approve** allows it this once.
* **Always allow** allows it and stops the agent asking again for the same kind of request.
* **Decline** says no, and the agent carries on without it.
* **Stop** ends the reply.
A request from another chat shows only a note saying where the agent is waiting, so you answer it with its chat in front
of you. Unanswered requests are declined after two minutes.
**Stop** ends the reply but keeps the agent's session, so your next message continues where it left off. If an agent
doesn't stop within a few seconds, Mantle restarts it, and your next message picks up the conversation.
Local providers run on your Mac and are available only while the desktop environment can run them. They may have their
own usage limits and permissions. Mantle-hosted AI uses Mantle credits; a local coding agent follows its provider's
rules instead.
Local-provider availability and model names depend on the installed tool and your account with that provider. Check
the status shown in Mantle settings when a model is missing.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.