Getting started
The Guide
Setup, providers, every day-one feature, pricing, and support, in reading order. The deep per-system docs live in the sidebar.
What is Mori
Mori is a desktop agent that does the work. She lives on your Mac or Windows machine, not in a browser tab. She sees your screen, drives your mouse and keyboard, browses in your real signed-in Chrome, writes and runs code, and talks to you out loud. She carries 154 native tools.
You give her a goal in plain language. She picks the right engine and carries it out. You keep your hand on anything that spends money.
Bring your own keys
Install
Mori ships for macOS 13 and later, and for Windows 10 and 11. The Mac build is code-signed and notarized by Apple, so it opens with a normal double-click. The Windows installer may raise a SmartScreen warning on first run; choose More info, then Run anyway.
macOS Download StudioMori.dmg, open it, drag Mori to Applications
Windows Download StudioMori-Setup.exe and run itTip
Terminal install
Prefer the command line? One line gets you the same app.
macOS
curl -fsSL https://studiomori.ai/install.sh | shWindows
irm https://studiomori.ai/install.ps1 | iexEach script fetches the latest build and installs it in one pass. When it finishes, open Mori and pick up at Quick start below.
Permissions
For Mori to see and control your computer, macOS needs two grants. She prompts you on first use.
Screen Recording
Lets Mori see your screen so she can act on what is there. System Settings, Privacy and Security, Screen Recording, enable Mori. Then relaunch.
Accessibility
Lets Mori move the mouse and type. System Settings, Privacy and Security, Accessibility, enable Mori.
Operating your real Chrome (optional)
To browse inside your signed-in Chrome, enable Allow JavaScript from Apple Events under Chrome's View, Developer menu, and approve the Automation prompt the first time.
If clicks do not land
The Setup page
Setup is where Mori proves her own wiring. Every check on the page is a real probe, not a saved preference. A provider row turns green only when a live call succeeds on your key. A local Ollama server is detected by talking to it. A failed check names its cause, so a bad key and a down server read differently.
Run it once after install, and again whenever something feels off. Green across the board means the machine is ready.
Quick start
Once she is open:
- Open Setup and paste an API key. One provider active is enough.
- Pick a model and let the connection check turn green.
- Go to Chat and ask for something real. Try a small build.
- Watch the right rail: the plan, the activity, the preview.
- Approve anything that costs money. She always stops to ask.
How API keys work
Mori does not resell AI. You bring a key from a provider you already trust, and Mori routes chat, the agent loop, tools, coding, and computer use through it. You pay your provider for what you use, and nobody else.
Keys live in Mori's local settings on your machine. They are never uploaded. You can keep keys for several providers and set one active.
Local and private
Providers
Nine cloud providers are built in, plus local models through Ollama. Add a key in Setup, set one active, and test the connection. Ollama needs no key at all.
| Provider | Best for | Example model |
|---|---|---|
| OpenRouter | One key, every model | anthropic/claude-sonnet-4.6 |
| Anthropic | Best for computer use | claude-opus-4-8 |
| OpenAI | GPT-class reasoning | gpt-4o |
| Groq | Fastest inference | llama-3.3-70b-versatile |
| DeepSeek | Cheap, strong coding | deepseek-chat |
| xAI (Grok) | Realtime and witty | grok-4 |
| Together | Open models at scale | meta-llama/Llama-3.3-70B |
| Mistral | Fast EU models | mistral-large-latest |
| Perplexity | Web-grounded answers | sonar-pro |
| Ollama | Local, private, no key | llama3.2 |
Not sure which to pick?
Models
Each provider exposes its own models. Hit fetch live in Setup to pull the current list straight from the provider, or type any model id. Mori defaults to the newest flagship.
Computer use wants a strong vision model. Quick chat can ride a faster, cheaper one. A fast-tier model is labeled in the composer when active, because it is weak for serious building. Switch any time without losing your work.
Local models (Ollama)
Run models entirely on your own machine. No key, no cloud. Mori talks to Ollama at localhost:11434, auto-detects the models you have pulled, and lists them like any cloud catalog. Pull one first:
ollama pull llama3.2The full catalog of models you can pull lives at ollama.com/library.
A keyless safety net
Computer use
Mori reads the buttons, fields, and menus of your real apps and clicks them by name. When the element path runs out, she falls back to vision and a real mouse. She streams what she sees into the chat so you can follow along.
Ask things like open Notes and write my list, or find the cheapest USB-C cable and add it to my cart. She works across native apps and websites. The deep dive lives in Computer use and browser.
Browser engine
For web tasks Mori uses a fast DOM engine instead of pixels. She reads the page's interactive elements and clicks by selector. She can run a private sandbox browser, or drive your real signed-in Chrome so your logins just work.
The Mori Chrome extension connects the desktop brain to your actual Chrome, with consent gates on anything risky.
Shopping
Mori compares real listings, adds the right item to your cart, and fills shipping details all the way to the final order screen. Then she stops and shows you a clean review.
She never pays on her own
Coding and preview
Mori scaffolds whole projects into real folders. Multi-file apps, not snippets. She runs them, reads the errors, and fixes until the build passes. The preview opens in the right rail beside the plan, so done is something you look at.
Deploys are real too. With your Vercel account connected, she ships through it, and the live URL lands in your dashboard under your control. The full system is in Coding and builds.
Terminal
A real shell, built in. Mori runs npm, git, build tools, and dev servers with live streaming output. Named terminal sessions stay alive across turns, and you can type into the same shell she is driving. Destructive commands are gated behind a confirmation. See Terminal sessions.
Voice and vision
Mori speaks, sentence by sentence, with her mouth synced to the audio. She also sees: screenshots of your screen and any image you hand her. Show her a photo and ask about it.
The living UI
You always know when Mori has the wheel. While she controls your computer, a soft glow frames the screen with a small banner. The moment she stops, it is gone.
The rest of the UI is honest the same way. Her thinking types into view word by word and holds until the last word lands. Plans show numbered phase boxes with real counts. The working indicator shows the actual step she is on, never a looping spinner.
No mystery state
The brain
The agent behind the face keeps getting sharper. In practice:
She remembers you
Memory persists across sessions as plain files you can read. Who you are, how you like things done, what you are working on. Everything she remembers is visible and removable. See Memory.
She learns from her own work
Tasks that go well become playbooks. Tasks that go wrong become lessons. She steers around the same mistake next time.
She researches on her own
Ask a real question and Mori runs deep research. The run shows up as an inline workflow card in the chat: waves, sources, and the trail that produced the answer. You get a briefing, not a snippet.
She reads your files for real
Hand her a PDF and she reads it. Hand her an image and she sees it. Hand her a CSV and she queries it with real SQL.
Real code powers, safely
Full git, Python, and a proper terminal. Risky work goes into an isolated workspace on its own branch. Every file is checkpointed before she changes it, so a bad edit is one rollback away.
Connections (MCP)
Mori speaks the Model Context Protocol. Connect her to MCP servers and every tool they expose becomes one of hers, on every provider you use.
Adding a server
Open Settings, Connections, and paste a config in the same shape as Claude Desktop's. If it works there, it works here:
{
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/folder"]
}Remote servers connect by URL instead:
{ "url": "https://your-server.example.com/mcp" }Secrets stay home
Business
Mori can help run a brand, starting with its socials. Ask her to push a launch and she writes posts into an approval queue. You review each draft and publish it with one click, or throw it out.
Nothing publishes without you
Live posting runs on your own platform keys, added in Settings. Stripe, Resend, and Shopify keys slot in there too.
Markets desk
A live board for crypto majors and prediction markets. Mori pulls live prices, researches what is moving, and preps an order ticket for you to review. Placing it is always your tap, never hers.
The safety line
This boundary is deliberate and does not move:
- Mori never enters a password or credentials.
- Mori never executes a trade or places a bet. You tap it yourself.
- Mori never clicks a final Pay without your explicit confirmation.
- Mori never publishes a social post without your one-click approval.
- Your keys and your money stay under your control.
The full model, including the autonomy ladder and the hardline floor, is in Autonomy ladder and Security and approvals.
Mori Link, Mori on your phone
Mori Link is the official iOS app, free on the App Store. It turns your phone into a remote for your desktop Mori: chat, build, run real tasks, and check results from anywhere. Same brain, same memory.
Pairing
Sign in with the same Studio Mori account as your desktop. Open Settings on the desktop, read the 6-digit pairing code, and type it on your phone. Both devices confirm over an encrypted channel. Your Mac only ever runs commands from that one confirmed phone.
What it can do
Run terminal commands, read and build files, drive your browser, send email, and execute multi-step jobs on your actual machine. Screenshots land right back in the chat.
Accounts and sync
Sign in with email or GitHub to sync conversations, tasks, and orders across devices. Stay signed out and Mori still works fully; everything just lives locally instead.
Building with Mori
Because Mori can see, click, type, code, and run a shell, the set of things you can ask is open-ended. A few starting points:
- Build me a landing page and preview it.
- Research these five products and make a comparison table.
- Fill out this form from the info in my Notes.
- Set up a new git repo and push my project.
- Deploy the site to my Vercel and send me the URL.
Tips for great tasks
Pricing
The free app is the complete product. Every tool, unlimited with your own API keys. Subscriptions add managed access: Mori runs on frontier models we provision, no keys required. The full comparison lives on the pricing page, and the honest fine print in Managed vs your own keys.
Hit a managed cap and Mori pauses managed usage until your session resets, or you switch to your own keys and keep going. The app never locks. Cancel anytime.
Updates
Mori updates herself. The app checks quietly, downloads in the background, and shows one small pill when an update is ready. Quitting also applies a downloaded update. macOS updates are signed and notarized end to end. A manual check lives in Settings.
What has shipped, release by release, lives in the changelog.
Support
Mori is built by a small team shipping every week. New models wired in, features landed, bugs fixed.
Getting help
- Community: the Discord is the fastest place to ask anything.
- Email: support@studiomori.ai. Paid tiers are prioritized.
- Studio and Max include help from real humans on setup and workflows.