# Moe docs

> Everything Moe does, screen by screen: what each part is for, how to use
> it, what starts on and what starts off, and what leaves your Mac and when.

## Moe, in short

Moe is an assistant that lives on your Mac. You say what you need, out loud
or typed, and it goes and does it: reads the mail and calendar you connect,
takes the notes in a meeting, works the Mac itself, remembers what you told
it last month, and asks before anything goes out to another person. It is
free, it runs on your Mac, and the thinking comes from an AI account you
already have.

These pages describe every part of Moe as it is today: what each screen
does, what each switch changes, what starts on and what starts off, and
what leaves your Mac and when. They are written for you, not for the people
building Moe, and they are kept in step with the app.

### What you need

- A Mac with Apple silicon, running macOS 15 or later.
- Something for Moe to think with: a Claude or ChatGPT plan, a key from a
  model company, or a model running on your own Mac. Moe has no mind of its
  own and no account of its own. See [Settings › Brain](#settings-brain).
- For the cloud half, an optional plan: [Away](#away-moe-when-your-mac-is-closed).
  Everything else is free and stays free.

### Where things are

- **The notch.** Moe lives under the notch at the top of your screen. Hold
  the talk key and it listens; hover and it opens; it glows amber when it has
  something for you. A Mac without a notch gets a small black tab in the
  middle of the menu bar instead.
- **The main window** (⌘0, or *Show Window* in the Moe menu) has five rows:
  **Chat** and **Meetings**; **Memory** under *Library*; **Connections** and
  **Message Moe** under *Reach*. **Settings** (⌘,) is at the bottom, and the
  footer shows two dots: *Connected* and *Voice ready*.
- **Settings** has fourteen panes: Brain, Replies, Voice, Meeting Capture,
  Permissions, Reminders, Running in the background, Activity, Chats, Skills,
  Usage, Upgrade (called Away once you have a plan), Privacy, and About &
  Licences. Each has a page here.
- **The menu-bar icon** is a small waveform; it turns into a red dot while a
  meeting is recording. Its menu has *Talk to Moe*, *Open Moe*, *Start
  meeting*, *Always Listening ("Hey Moe")*, *Hide Island* and *Quit Moe*.

### Moe is in beta

You are early. Moe does a great deal already and it is still being built, so
expect the odd bug and a few rough corners, and expect it to change often
between versions. The app says so beside its version in Settings › About &
Licences and on the first screen of the welcome.

When you hit something, tell Moe: out loud or typed, "that didn't work" is
enough. It writes the report itself and, once you have allowed problem
reports, it reaches us with what is needed to fix it. See [When Moe itself
breaks](#when-moe-itself-breaks). From outside the app, hello@moebot.app.

### How to read these pages

Every page is one part of Moe, in the order you meet it: getting started,
talking, the settings that shape the answers, driving the Mac, the gate in
front of anything that goes out, meetings, the things Moe does on its own,
its memory, what you connect, the chat apps you can message it from, the
cloud, privacy, and what happens when Moe itself breaks. Search at the top
looks through all of it; press `/` to jump to the box.

## Getting started

### Download and first open

Download Moe from [moebot.app/download](https://moebot.app/download). Every
Download button on the site opens a short sheet first, saying what is in the
box and what opening it looks like; **Download Moe for Mac** starts the
download. It is a large download, a little over a gigabyte, because
everything Moe needs is inside it: the speech and voice models that run on
your Mac, and the part of Moe that does the thinking. Setting up fetches
nothing, so the first run works offline.

Open the disk image and drag Moe onto Applications. Moe is signed and
notarized by Apple, so the first time you open a copy you downloaded, macOS
checks it and asks once: *"Moe" is an app downloaded from the Internet. Are
you sure you want to open it?* Click **Open**. That is all of it: there is no
trip to System Settings and no Privacy & Security step.

After that, Moe asks for what it needs as it first needs it: the microphone
the first time you talk to it, permission to control your Mac the first time
you ask it to do something there. Those are macOS asking on your behalf, not
warnings about Moe.

Moe keeps everything it makes in `~/Library/Application Support/Moe`:
memories, meeting notes, transcripts, settings and connections. That is
where macOS puts an app's data, and where to look to back it up. (An older
name for the same folder, `~/.moe` in your home folder, still works; it
points at the same place.)

### The welcome

The first time Moe opens, a short welcome walks you through it: seven
screens, one thing each, all of them skippable. **Back** and **Skip** are on
every screen, nothing in it is permanent, and nothing breaks if you say no.

1. **Hi, I'm Moe.** The four things it does: answer out loud, take meeting
   notes, remember you, reach your things. One line says Moe is in beta.
2. **Can I hear you?** The one permission asked up front. **Turn on the
   microphone** shows macOS's own prompt. Say no and Moe still works; you
   type to it instead. Your voice is turned into words on this Mac and is
   never sent anywhere.
3. **Give me something to think with.** Moe has no account of its own, so
   pick the one you already use. The first two are marked **Recommended**,
   side by side, because they are a plan you may already pay for: **Sign in
   with Claude** or **Sign in with ChatGPT**; Moe works as well with either.
   Below them: **Paste a key you already have** (Anthropic, OpenAI,
   OpenRouter, Google Gemini, DeepSeek, xAI and others), or **Run a model on
   this Mac**. Signing in happens in your browser, never in a Terminal: Moe
   opens the page, and for ChatGPT it shows you the code the page asks for,
   already copied. On a fresh copy of Moe this screen says *getting ready*
   for the few seconds it takes to lay down the part that thinks.
4. **Say hello.** Hold right ⌥, say "what can you do?", and let go.
   Double-tap the key to stop Moe, or press ⌃⌥Space to start it and again to
   stop. This screen also asks for the two macOS permissions a first task
   needs, one button and one line each, both skippable: **Accessibility**, so
   Moe can hear the talk key in any app and click for you when you ask, and
   **Screen Recording**, so Moe can see your screen when you ask about it.
   Screen Recording takes effect the next time Moe opens. If System Settings
   shows Moe switched on for Accessibility and Moe still says it is off,
   macOS is remembering an older copy: **Reset and ask again** clears that.
   The ⌃⌥Space shortcut works without any of it.
5. **I'll take the notes.** What a meeting records and where it stays, and
   one switch, **Start and stop a meeting with ⌃⌥M**, off: a key that
   records other people is one you switch on yourself.
6. **What may I read to learn about you?** One switch for each thing on
   this Mac Moe could read back over (*Read Calendar back and learn about
   me*, and its like), and under them the daily pass itself, *Once a day,
   read back over what I've allowed and note what it learns*. Everything
   connected starts switched on, marked **Recommended**; untick what you
   would rather Moe left alone and press **Save and continue**. Nothing is
   read until you save. **Skip** records nothing, so Moe can ask again later,
   the first time you connect something. With nothing connected yet, the
   screen says so. See [Memory](#memory-what-moe-knows-about-you).
7. **Connect your world.** What to connect first, in the order the
   Connections page lists it: the apps already on this Mac (Calendar,
   Reminders, Notes and Contacts), then Google (Gmail, Calendar and Drive,
   one sign-in for all three), then everything else. Then two switches you
   see before the welcome closes: **Start Moe when my Mac starts**, on, and
   **Let Moe send problem reports**, off, with **What is sent?** beside it
   and **Report without saying who I am** under it. Both are the same
   switches as Settings › Privacy. **Take me to Connections** ends the
   welcome.

Skip everything and Moe still takes meeting notes; the brain can be chosen
any time in Settings › Brain.

### Moe starts with your Mac

When you finish the welcome, Moe adds itself to System Settings › General ›
Login Items, so it is there under the notch when you sign in. The last
welcome screen shows it as the switch **Start Moe when my Mac starts**,
already on; turning it off there and turning it off in Login Items are the
same thing. Moe never switches it back on behind you: it asks macOS once,
and after that the switch is yours. A copy that opens after *Erase Moe from
this Mac* adds nothing.

### The part of Moe that thinks looks after itself

Moe's thinking part ships inside the app and is laid down on first launch.
Moe starts it when Moe opens and restarts it if it stops. If it keeps
stopping, Moe says so once, *The part of Moe that thinks kept stopping*, and
then keeps trying quietly in the background about once a minute until it is
back; you don't have to quit Moe or open it again. New Conversation tries
right away. Each version of Moe also keeps that part current on its own: a
small update in the background, one brief *restarting*, and that is all you
see.

## Talking to Moe

Four ways in, and they all end in the same place: Moe listening, the notch
lit green.

- **Hold right ⌥** and talk. Let go when you are done. This one always works
  and never mishears its name, because it does not listen for one. It needs
  Accessibility; until that is on, Moe says so wherever you look, on the
  island when you hover, at the top of the open panel and above the chat box,
  each with a **Fix** button, and the warning goes the moment it is on.
  **Settings › Voice › The key you hold to talk** changes the key to **right
  ⌘**, **right ⌃** or **fn / 🌐**, and the new key works straight away.
  Right ⌃ is only on some keyboards, and fn works only if macOS is not
  already using it: set **System Settings › Keyboard › Press 🌐 key** to
  **Do Nothing**, or macOS will act on it too. Everywhere Moe names the key,
  it names the one you picked. A key held as part of a shortcut doesn't
  start Moe: hold fn and press Delete, or right ⌘ and Tab, and the press is
  dropped: nothing is recorded, no picture is taken, and a reply it paused
  carries on.
- **Double-tap the talk key** and talk with nothing held, for when your
  hands are busy or you have a lot to say. The notch breathes and says
  *Listening — tap to send*. Pause as long as you like to think: Moe never
  decides you have finished. **Tap the key once** and what you said goes to
  Moe, exactly as if you had held the key and let go; if you said nothing,
  nothing is sent. **Esc** drops it without sending, and so does locking the
  screen or the Mac going to sleep. This is only when Moe is idle: a
  double-tap while Moe is talking or working stops everything.
- **⌃⌥Space** to start and stop, hands free. It needs no permission at all.
  The row for it in Settings › Voice, *Press ⌃⌥Space and ask*, offers
  **⌥Space**, **⌘⌥Space** and **⌃Space** instead, for when another app
  already owns it. A new shortcut takes effect when Moe restarts.
- **Say "Hey Moe"**: **Settings › Voice › Say "Hey Moe"**, off by default.
  The menu-bar icon has the same switch, *Always Listening ("Hey Moe")*.

Two switches under *While you talk* go with the key. **Moe sees my screen
when I ask** is on: a picture of the screen under your cursor, taken as you
press the key, goes with your words, so "what do I do here" just works. It
is never saved. **Move my mouse to what Moe points at** is off: Moe only
draws a ring around the thing it means, and it never clicks.

Moe starts reading your turn back the moment you stop talking, not the
moment it decides you have finished, so when you stay quiet the answer
starts sooner. Say anything more and the whole turn is read again; nothing
is ever taken from a half-heard sentence.

### Staying in the conversation

**Keep the conversation going**, in Settings › Voice, is off to start with:
Moe answers one question and stops listening. Switch it on and, when Moe
finishes answering, it keeps listening for a few seconds so a follow-up
needs no key and no name; you just keep talking. **How long it keeps
listening** under it chooses 8, 12, 16, 20 or 30 seconds; it starts at 8.
Longer is friendlier in a quiet room and worse in a busy one, because
everything said in that window is something Moe has to judge.

**Also after I hold the key** decides whether the window opens after a
hold-to-talk turn too, or only after the name and the shortcut. Holding the
key is meant as a one-off question, so this is off unless you want
otherwise. Both rows, and *When it goes quiet* below, are greyed out until
the conversation switch is on.

### Not everything you say is for Moe

The hard part of an always-listening assistant is not hearing you; it is
working out which of the things it hears were meant for it. In the follow-up
window Moe weighs several signals rather than matching a phrase: how long
ago it spoke, whether it had just asked you a question, how loud you are
compared with the room, whether the voice is the one that started the
conversation, and what the words themselves suggest. In English it reads the
words closely; in other languages it goes by the name, the timing, the
loudness and the voice. If the answer is still unclear it asks the Mac's own
on-device judgement (on macOS 26 with Apple Intelligence), and without that
it takes a turn that looks like a request and leaves one that does not.

It also knows its own voice. If the microphone picks up Moe's own speech,
that is echo and not a new turn; it never answers itself.

**Whoever opens a conversation owns it.** The moment you say "Hey Moe" or
hold the key, Moe takes a reading of that voice and uses it for the rest of
the conversation, so a second person talking beside you is not answered, and
a guest who opens their own conversation is. Someone else can still join by
name: saying "Moe" gets through regardless. This needs no setup, because the
voice it compares against is the one that just spoke.

**Teach Moe your voice**, under *Your voice* in Settings › Voice, learns what
you sound like from a few sentences read aloud. It is optional; with it, "is
this the person who started this conversation" becomes a measurement
instead of a guess. Press **Read one**, read the sentence on screen, and
after three the row reads **Moe knows your voice**. Moe keeps learning from
the turns you open by name. Nothing is recorded; what is kept is a
description of the voice, on this Mac. **Forget my voice** appears once you
have read one: Moe stops using how a voice sounds as a signal, and nothing
else changes.

### Interrupting

Brushing the hold key does not cost you the answer. The sound stops the
moment the key goes down, which is what you want when you have something to
say, and the reply is kept, not thrown away, until what you do next says
whether you meant to replace it.

Talk over Moe and it stops. What you say next **changes** what you asked for
rather than replacing it: ask for five things, correct one of them halfway
through, and Moe keeps the other four. Withdraw it outright, "never mind",
"forget it", "scratch that", and it drops the lot. Amending is the default
because it is the one you can undo.

**Interrupt Moe by talking**, off to start with, lets you talk over it
without a key. Start speaking while it is answering and it goes quiet, then
stops, if it was you. A voice across the room, or the television, and it
simply comes back up a moment later, having interrupted nothing. Each reply
can be paused this way once; a false alarm does not get a second go until
the next turn.

The same is true while Moe is still thinking: pressing the shortcut again
mid-thought puts you back in control. Saying "Hey Moe" or pressing the
shortcut never waits; those stop it immediately.

### Pausing what Moe is saying

**Tap the hold key while Moe is talking and it stops there. Tap it again and
it carries on from the same word.** Nothing is re-said and nothing is
skipped. The island says *paused — tap again to carry on* so you can tell a
pause from a problem.

That is a tap, a quick press. Holding the key is still "let me say
something": the sound stops the same way, and then your words either replace
the answer or, if you say nothing, let it carry on. Double-tapping while Moe
is talking or working stops everything outright; double-tapping while it is
idle is how you talk hands-free.

### Pausing mid-sentence

A breath is not the end of your turn. When you stop after something that
sounds complete, Moe starts working on it straight away but keeps listening
until the moment you would hear its first word. Go on talking inside that
window and nothing is lost: the half-answer is thrown away unheard, what you
said before the pause and after it are joined into one request, and that is
what Moe answers. Stay quiet and the answer arrives exactly when it would
have anyway. This applies to turns you start with the name or the shortcut;
a held key ends the turn when you let go.

### Ending a conversation

Say you are done in whatever words you would use, "that's all", "thanks",
"I'm good", and Moe closes the conversation. This is Moe's own judgement of
what you meant, not a phrase it matches.

With the conversation switch on, if it has been quiet for a few seconds and
Moe is not waiting on you, it offers to step out rather than sitting there
lit. **When it goes quiet** chooses how: **Ask on the island** (a tick and a
cross by the notch, the default), **Ask out loud**, **Both**, or **Just stop
listening**.

### The name

"Hey Moe" runs entirely on your Mac, on a small model that listens only for
those two syllables; the room is not transcribed. It is off by default, and
there are honest limits worth knowing:

- It sometimes misses the name, and it sometimes fires on a phrase that
  sounds like it ("hey Joe", "a moment"). Its training was synthetic speech,
  and no recording of your voice or your room went into it.
- When it fires on something that was not the name, the checks above usually
  stop anything from happening, but the light comes on for a moment.
- Hold-to-talk and the shortcut are unaffected by any of this.

**Teach Moe its name.** Under the *Say "Hey Moe"* switch in Settings ›
Voice, **Teach** records you saying "Hey Moe" twelve times and eight
phrases that sound like it, each prompt shown on screen, about two minutes
in all. Moe then measures how well it hears you on this Mac and picks the
setting that catches your voice without answering the near misses, and
tells you what it found in words: how many of your "Hey Moe"s it now
catches and how many of the near misses it lets through, against how it
was before. The row then reads **Moe knows how you say its name**, and
**Teach again** repeats it, in a different room, say. The clips stay in
Moe's folder on this Mac; nothing is sent anywhere. Two more buttons
appear once you have recorded: **Send these to the Moe team** opens a new
message to hello@moebot.app in your mail app with your clips zipped and
attached, so the next version of the wake word learns from real voices in
real rooms, and nothing goes until you press Send; **Forget my recordings**
removes the clips from this Mac and puts the wake word back to the setting
it shipped with.

### What Moe says while it works

During a long job Moe says what it is doing, "Going through your mail",
"Searching your files", and repeats the current one every so often so you
know it is still there. Anything it does through a connected service says
which service, whether the service is on this Mac or reached through
Composio. The switch for this is **Tell me what it's doing while it works**
in Settings › Replies.

**Work silently.** When a long job is more talk than you want, hover the
notch while Moe works and press **Work silently**. For the rest of that job
Moe stops saying what it is doing, and when the job is done it says only
the answer. The step it is on stays on the island as text, so you can still
see it is working. Two things are never silenced: a message waiting on the
confirmation sheet for you to press Send, and anything that went wrong.
Press it again, it now reads **Talk me through it**, to hear the updates for
the rest of the job. It lasts one job, and the button only appears while a
spoken question is being worked on; a typed one is already quiet.

### Language

Moe starts in your Mac's own language, the first language in System
Settings › Language & Region that Moe can hear, and in English when none of
them is one it knows. **Settings › Voice › Language** changes it. Talking to
Moe is tuned for English: in another language Moe waits for a moment of
silence to know you have finished, and "Hey Moe" is an English phrase, so
the shortcut is the reliable way in; the banner at the top of the tab says
so. The fast engine hears English and about two dozen European languages;
other languages use a universal engine that downloads once, about 600 MB.

Moe answers in the language you set it to, and stays there. A stray foreign
phrase in a turn, which speech recognition sometimes produces, is treated as
the mishearing it usually is rather than a reason to switch.

### Addresses and numbers

Numbers arrive written: say "twenty five thousand four hundred dollars" and
you get "$25,400". Email and web addresses are written too. "Email izzy
three at hqpulse dot ai" becomes `izzy3@hqpulse.ai`; "example dot co dot uk"
becomes `example.co.uk`; letters said one at a time run together. It only
happens where the shape is unmistakable, "dot" followed by a real domain
ending, so "a dot matrix printer" stays an ordinary sentence.

### Moe's own voice

Moe speaks with **Kokoro**, which ships inside the app: twenty-eight voices,
male and female, British and American, all running on your Mac with nothing
sent anywhere. **Settings › Voice › How Moe sounds** picks the set of voices
and the voice, and **Use and preview** plays a sample.

Two more sets are offered there. **PocketTTS** has twenty-six voices and is
the only local one that starts speaking before it has finished thinking. It
is not in the app: the Download row says what it costs, 939 MB, once, kept
on this Mac, and its button fetches it with a bar, a percentage and a
Cancel. Until it is here Moe keeps speaking with Kokoro. Stop a download and
what has arrived stays; the next Download carries on from there. **Premium**
is the best voice Moe has, the most natural and the quickest to answer,
rendered in the cloud and streamed back as it speaks. It is part of the Away
plans; picking it on the free plan opens Settings › Upgrade.

Each set starts on a voice chosen by ear, and you can change it whenever you
like: Kokoro begins on **Heart**, PocketTTS on **Peter**, and Premium on
**Clive**, one of three Premium voices.

**If Moe cannot use the voice you picked, it tells you.** When Premium is
out of reach, no network, a plan that does not include it, this month's
allowance spent, Moe speaks with the voice on your Mac instead and a line
under the button says so: which set you chose, which voice you are actually
hearing, and why. Your choice is kept, so Moe goes back to it by itself the
next time it can.

### Premium voice and hearing, on paid plans

On the **Away** and **Away+** plans Moe can hear and speak through the
cloud: sharper ears and a more natural voice than the ones that run on your
Mac. Each plan includes a monthly allowance, counted for the whole account
rather than per Mac and reset on the 1st:

| Plan | Spoken | Listening |
|---|---|---|
| Away | 500,000 characters | 6 hours |
| Away+ | 1,500,000 characters | 20 hours |

Moe never holds the keys to those services: it asks for a single-use token
each time it opens a connection. When the allowance is used up, or if
anything goes wrong on the way, no network, a slow answer, a service down,
Moe carries on with the voice and ears on your Mac without asking, and
nothing you said is lost. Premium hearing covers English and about twenty
other languages; in any other language the Mac's own hearing is used.

**Use the sharper voice and hearing that come with my plan**, under
Settings › Voice, is on by default and does nothing on the free plan: what
decides is the plan, not the switch. Turn it off and, paid or not, nothing
leaves your Mac. The line under it says which is true right now: *Cloud
voice: on · 41% of this month used*, *Cloud voice: not part of your plan*,
*Cloud voice: off*, *this month's allowance is used up · back on* a date, or
that Moe's cloud could not be reached just now.

### Checking the microphone

**Check this microphone and these speakers**, under *Can Moe hear you while
it talks?*, says a sentence out loud, listens to how much of it comes back,
and tells you whether your speakers are leaking into your microphone. Stay
quiet for the eight seconds it takes. If they are leaking, Moe hears itself,
and interrupting by voice gets harder; headphones, or the built-in
microphone and speakers together, fix it. It also says when a call app has
taken echo cancellation away; that is expected, and it comes back when the
call ends.

### Giving Moe a photo or a file

Press **+** beside the message box in Chat and choose where it comes from:

- **Photos…** — from your library, through Apple's own picker, so Moe sees
  only the photos you choose and needs no access to the rest.
- **Files…** — anything on your Mac, folders included.
- **Take a Screenshot** — drag across the part of the screen you mean, the
  same as ⇧⌘4. Escape cancels.
- **Paste from Clipboard** — whatever you last copied, if it is a file or an
  image.
- **Recent on this Mac** — the three newest things in Downloads and on your
  Desktop, one click each.

Or drag files anywhere onto the conversation. What you have added waits
above the box, with an × to take any of it back, until you send, with words
or on its own.

The panel under the notch has the same **+**, without the recent files, and
you can drag a file onto the notch itself: it opens as the file arrives and
stays open until you let go. Once something is waiting in its box it stays
open, so you can say what the file is for.

Moe opens what you send where it is on your Mac, so a large file costs
nothing to send. Up to four photos per message are shown to Moe as
pictures. Photos, pastes and screenshots that did not already have a file of
their own are kept in an *attachments* folder inside Moe's own folder.

### Links to what Moe read

Moe is spoken, so it never reads a web address out loud, but the links are
there to click. Under an answer that involved the web, **Sources** lists the
pages Moe actually opened, taken from the steps it ran rather than from what
it says it did. When Moe cites something in the answer itself it writes a
real link, live in Chat and in the panel under the notch; the spoken version
says the label and skips the address. Ask for "the links" and you get
exactly these.

### Reading the chat

In Chat, what you said is on the right, in a tinted bubble, and Moe's
answers are on the left under its name. Notes that belong to neither of you,
like *Stopped.*, sit in the middle. Under an answer, a small chip says what
Moe did to get there, *3 steps*, and opens into the list; code Moe writes
gets its own scrolling box. While a spoken conversation is open, a bar above
the box says whose turn it is, *Your turn — just talk, no wake word needed*,
*Thinking…*, *Speaking…*, with **End conversation** beside it.

## Settings › Brain

Moe has no mind of its own; it borrows one you already have. **Settings ›
Brain** is whose, which model, and how hard it thinks: three things on one
page, and no Apply button. Tapping a chip saves it, hands it to the part of
Moe that thinks, and checks that Moe still answers.

### The account card

The card at the top names the account Moe is borrowing, *Claude, on your
monthly plan*, *Anthropic, with your key*, *Ollama or a local server, on
this Mac*, with a dot and one line saying how it is: *Working, on Sonnet.*
(or *Working, on Sonnet, high effort.*) while all is well; *Waiting for a
sign-in.*, *Not signed in yet.* or *Starting…* while it is not; and, while a
change goes through, *Saving…*, *Switching to ChatGPT…* or *Checking Opus…*
until the verdict lands: *It works. Moe is thinking with Claude (Opus).*, or
a plain sentence about what went wrong. If a sign-in is outstanding, the
button for it is right there: **Sign in with Claude…** or **Sign in with
ChatGPT…**. Under the name, one sentence on what this way of paying costs,
*Nothing on top of the plan you already have.*

### Change account…

**Change account…** opens the one sheet with fields in it, *Which account
should Moe use?*, listing every choice in three groups:

- **A plan you already pay for** — **Claude** and **ChatGPT**, both marked
  **Recommended**, equally. Each signs you in through a page in your
  browser; for ChatGPT, Moe shows you the code the page asks for.
- **A key you have — you pay by the word** — **Anthropic**, **OpenAI**,
  **OpenRouter**, **Google Gemini**, **DeepSeek**, **xAI (Grok)**, and
  **Anywhere else** with your own key and address. Each takes **Paste your
  key here**; the key is kept on this Mac, readable only by you, and never
  shown again (a row that has one says *Key stored*). *Anywhere else* adds an
  **Address** field and a **Test** button that tries the key against it
  before you commit.
- **On this Mac — private, and free** — **LM Studio** and **Ollama or any
  local server**. Each takes an **Address**, the one your server answers on,
  ending in /v1; `http://127.0.0.1:1234/v1` for LM Studio and
  `http://127.0.0.1:11434/v1` for Ollama are filled in for you. Load a model
  there first. A local model is slower and less sure of itself than one in a
  data centre; whether it can look at your screen or use your connections
  depends on which model you load, and Moe says what the one you picked can
  do.

The row in use is marked *In use*; one you have signed in to says *Signed
in*. **Use Claude** (or whichever you picked) at the bottom applies it;
**Cancel** leaves everything as it was.

### Model

**Model** is a row of chips, the provider's own names with two words under
each saying what picking it gets you, and **Other…** at the end for typing a
model name the row does not show.

- On a **Claude plan**: Opus (*Smartest, slower*), **Sonnet** (*Quick and
  capable*, where a new Moe starts), Haiku (*Fastest*), Fable (*Newest*).
- On a **ChatGPT plan**: the models your plan actually offers, read from
  your account when you sign in. A saved model your plan does not offer is
  said so plainly, *Your ChatGPT plan doesn't offer that, so questions on it
  fail*, rather than failing quietly.
- With a **key**, the provider's current models, from the fastest and
  cheapest to the smartest; OpenRouter's chips are the popular models across
  vendors.
- **Anywhere else**, **LM Studio** and **Ollama** have no chips: type the
  name of a model your server has loaded.

Under the chips, one line, *Can see your screen ✓ · Can use tools ✓*, says
what the model you picked can do, with a note when it cannot: *This model
can't see images, so Moe won't attach your screen*, or *No tool calling:
Moe can talk but not act*.

### How hard it thinks

Another row of chips: **Default** (*Let Claude decide*) and then the
provider's own levels, from *none* or *low* up to *xhigh* or *max*, each
captioned (*No thinking, fastest*, *Quick*, *Everyday*, *The usual choice*,
*Careful, slower*, *Slowest, most thorough*). Higher is slower and more
thorough; Default, where every Moe starts, lets the provider choose. On
Claude, changing it restarts Moe's thinking part, which takes a few seconds;
on a key it takes effect on your next question; a local model that does not
think ignores it. A model with no levels shows no row.

### How long Moe may work on one thing

On a Claude plan, a row of four chips: **5 minutes** (*Quick jobs only*),
**15 minutes** (*Most errands*), **30 minutes** (*The usual choice*, and
where every Mac starts) and **1 hour** (*Long research*). It is a ceiling
for one request, not a timer on every answer: most questions are done in
seconds whatever you pick. If a task is still going when time is up, Moe
stops it and tells you, *That was taking longer than Moe may work on one
thing, so Moe stopped it*, and you can give it longer here. Tapping a chip
takes effect from your next question.

### When the account Moe borrows stops working

Two very different things can go wrong with the account Moe is borrowing,
and Moe tells them apart.

**Something that will pass.** Your provider is busy, or limiting how fast
you can ask. Moe says so where you asked, *"I've hit the limit on your
Claude plan — I'll answer as soon as it clears, in about 10 minutes"*, and
then does exactly that. There is nothing for you to do.

**Something that will not pass on its own.** Your sign-in was cancelled,
your key was revoked, the account ran out of credit, or the address Moe has
for a local model stopped answering. Waiting will not fix any of these, so
Moe never says it will. You are told where you asked, in the chat you typed
into or out loud if you were talking, in your own provider's name: *"OpenAI
wouldn't let Moe in — the key is missing, wrong, or no longer good. Moe
can't think until that's sorted: Settings › Brain."* And it stays in
Settings until it is fixed: the account card on this page carries an amber
line, *OpenAI turned down the key*, followed by the one next thing to do,
and Connections stops calling Moe's brain *Working* while it plainly is
not. It clears itself the moment Moe answers anything at all; there is
nothing to dismiss and no need to restart Moe.

A question your provider simply refused to answer, a safety filter, is said
in the chat (*"Gemini wouldn't answer that one. Try asking it a different
way."*) and kept out of Settings, because there is nothing about your
account to fix. And nothing a provider says about your key ever reaches the
screen: Moe strips anything key-shaped first.

### If you have a cloud computer

Changing your brain here changes your cloud computer's brain too. The
moment you change it, a short line appears under the account card saying
what became of your machine. Most of the time it says *Your away machine is
getting this too — it picks it up the next time it syncs, and uses it from
then on.* That covers a different model on the same account, a new key you
just pasted, and your ChatGPT plan, where your machine is given a fresh
copy of the sign-in on this Mac.

Three cases it cannot do by itself, and it says which. **Your Claude
plan:** Anthropic gives each computer its own sign-in, so the line offers
**Sign your machine in too…**, one click, approve in your browser, done;
until then your machine keeps thinking with what it had. **A key you pasted
some time ago and did not retype:** Moe will not send a key off this Mac
that you did not just type, so the line offers **Give your machine this
too…**. **A model running on this Mac**, LM Studio or Ollama: your machine
cannot reach it, so nothing is sent and the line says why. If you have no
cloud computer, none of this appears.

### If the thinking part is not installed

On a Mac that has the app but not yet the part of Moe that thinks, the page
says so, *Moe's thinking part isn't installed yet*, and **Set it up**
downloads it, about a gigabyte. Meetings and your connections work without
it; answering a question is the part that needs it.

## How Moe answers you

Moe is a voice assistant that you can also type to, and it tells the
difference: a question asked out loud comes back out loud and short; a
question typed comes back written, at the length it needs. **Settings ›
Replies** is where that is decided.

### Who Moe is

Moe is on your side: part colleague, part friend, and the one who actually
gets things done. Warm without gushing, direct without being curt. It says
the answer first and does not narrate.

It is honest about what it knows, because you act on what it tells you. A
judgement call comes as its best guess, and it says so. A fact it could not
check, a price, a date, a count, it will not guess: it says it could not
confirm it, and how it could be found out if that matters. It has opinions.
If something looks like a mistake, it says so once, kindly, with its reason;
then it is your call, and it helps with whatever you choose.

Moe knows where it is. On your Mac it may use all of it: files, apps, the
browser, mail, calendar, messages and the screen. Moe in the cloud (see
[Away](#away-moe-when-your-mac-is-closed)) knows it answers while the Mac is
asleep, that it cannot see the Mac's files or screen, and that anything
needing the Mac waits for the Mac to wake. To you it is one Moe, with one
memory, on every channel you set up.

### Moe does it, rather than telling you how

Tell Moe something is not working, or ask how to do something, and if its
tools can do it, your files, your mail, the web, your apps and browser, it
does it and tells you what it did, instead of giving you a list of steps. If
it is not sure you want it to, it offers in a line: "Want me to take care of
it?" You only get steps for the part that needs your own hands, like typing
a password, paying, or signing, or when you ask for steps.

Anything that sends, posts, buys or deletes still waits for your yes (see
[Before anything goes out](#before-anything-goes-out)): Moe does the work up
to that point and asks.

### How much Moe says

**Reply length** sets how long Moe's answers are:

- **Short** — one sentence out loud, a few lines in writing. The answer and
  nothing around it. This is the default: Moe is something you talk to, and
  a spoken answer is better short.
- **Balanced** — a sentence or two out loud, and whatever a typed question
  needs.
- **Detailed** — up to a short paragraph out loud, and an in-depth written
  answer with the reasoning, the options and what to watch out for.

Spoken answers stay tighter than written ones at every setting, because you
cannot skim something you are listening to. Asking for more, "tell me
everything", always gets more, whatever this is set to. The chat apps you
message Moe from follow the same setting.

### Out loud, or on screen

Three switches, because talking and typing are separate questions:

- **Speak replies out loud** is the master. Off, Moe never says anything and
  every answer is on screen. Moe is also silent for the whole of a recorded
  meeting whatever this says; the room and the call would hear it.
- **When you talk to Moe** — on. You asked out loud, so the answer comes back
  out loud.
- **When you type to Moe** — off. Typed in, text out. Turn it on if you want a
  typed question answered aloud as well as shown.

### Written to be read

**Write answers to typed questions to be read, not heard** changes what the
answer is, not just how it arrives. A spoken answer is one or two short
sentences with no lists and no formatting, which is right when you are
listening and wrong when you are not. On, and it is on, a question you typed
comes back written as writing: short lists and headings where they help,
links you can click, and the length the question needs. Off, a typed
question gets the same spoken-shaped answer.

### The panel under the notch

**Open by itself when an answer is ready** decides whether the island
expands to show you an answer.

- **Only when Moe stays quiet** — the default. An answer you were told is an
  answer that reached you; a panel over your screen would be an interruption
  rather than a delivery.
- **Always** — to read along while Moe talks.
- **Never** — for a shared screen. The answer is still in Chat.

A recorded meeting always opens it, whatever this says: the reply is not
being spoken then, so the panel is the only place it exists.

**How long it stays** is **6 seconds**, **12 seconds**, **30 seconds** or
**Until I dismiss it**; it starts at *until I dismiss it*, because an answer
Moe did not say out loud is one you have not seen yet, and it should not
vanish on a timer. With a number, the clock restarts while the cursor is on
the panel, while the field has the keyboard, or while there is a half-typed
question in it; a click in another app folds it at once either way.

To close it yourself: the **⌃** button in the top right, or **Esc**. Folding
is only folding; it leaves Moe alone and the conversation where it was. The
**✕** beside it appears only while Moe is actually working: that one stops
the turn and closes the microphone. On a Mac with a notch both sit in the
black strip beside the notch. The panel shows the last few turns, and there
is always a box to type in with a **Send** button; the **+** beside it takes
a photo or a file.

Anything Moe needs you to see before the conversation, a reminder that came
due, a call it can record, a new version of Moe ready to install, or the
talk key waiting on Accessibility, sits at the top of the panel, and the
panel grows to hold all of it.

**Every Mac.** The island fits whatever notch your Mac has, at any display
scaling, and lines up with the notch itself rather than the middle of the
screen. A Mac with no notch, an iMac, an older MacBook Air or an external
display, gets a small black tab in the middle of the menu bar instead, and
the glow and the working light trace around it. With a laptop and an
external display, Moe stays on the laptop's notch. Before you have said
anything, the panel greets you by the hour, *Good morning — I'm here*.

### While Moe is working

- **Say "on it" as soon as I ask** — off to start with. Said the moment you
  finish asking, before Moe has started on the answer, so you know it heard
  you. It is said from your Mac, before anything is asked of the model, and
  it only ever repeats what you asked and never guesses how it will go.
- **Tell me what it's doing while it works** — on. "Checking your calendar",
  said when something takes a while; you are listening rather than
  watching, and a long silence sounds like Moe has stopped. Off, Moe says
  nothing between "on it" and the answer; the island still shows the step.
- **Ding when a written answer is ready** — on. One soft note, only when Moe
  is not going to say the answer out loud, so a question you typed and went
  back to work does not sit unread in the panel. **Hear it** plays the note.
- **Typed questions open the Chat window** — off. The answer stays in the
  panel under the notch, on whatever you were reading; a question asked
  while looking at your notes is often about the notes. On, every question
  you type opens Chat, where a long answer has room.

**Handing a job off.** Say "in the background", or ask for something that
is plainly a long job you do not need to sit through, and Moe hands it to a
helper of its own, tells you in one line that it is running, and gives you
the conversation back. Ask it something else meanwhile; it answers. When
the helper finishes, Moe tells you the outcome the way it would a reminder:
spoken, in its own words, with what got done, what did not, and anything
you need to decide. That is the whole of what you hear about it; the
helper's own steps stay in its transcript. It works the same whichever
brain Moe thinks with. While Moe itself works on something in front of you,
what it says is its own account of the work; there is no stock "still on
it" line, and if you would rather hear nothing at all, **Work silently** on
the notch is the switch.

**A question outlives a sleep.** While Moe is working on something for
you, your Mac does not doze off on its own — the idle timer is held until
the answer is in. Close the lid and it sleeps as ever; if that cut the work
off, Moe notices on wake and carries on where it was, once, telling you it
is picking up rather than starting again. The same if you quit Moe, or it
was closed for you, in the middle of an answer: within half an hour of
opening it again, on the same conversation, it picks the question back up.
It never picks up a question twice.

**You can always say the next thing.** Moe does a few things around an
answer that you never see, going back over the conversation for anything
worth remembering, keeping its notes in order, and none of them hold the
conversation: say something while one is running and Moe answers. If Moe is
genuinely still finishing the answer before, your message waits for that one
and is answered next.

### Addresses are shown, never spoken

Moe never reads a web address out loud. Any address in an answer is a real,
clickable link in Chat and in the panel, whether Moe wrote it as a link or
simply as an address, and the spoken version says the label and skips the
address entirely.

### Moe comes back to things

Moe keeps a list of open loops and brings them up later, without being
asked: on the notch if you are at the Mac, otherwise on whichever chat app
you set up. Five kinds of thing go on it: what you said you'd do; what Moe
started (a booking, an order) and should check landed; people waiting on
you; deadlines, with the preparation done early; and things you looked at
that can change, a price, a slot, a delivery, which Moe watches without
thinking and speaks about only when they move. How it works, and the
switches for it, are under [Running in the
background](#running-in-the-background).

## Driving your Mac

Moe can see your screen and use your Mac, open an app, click a button, fill
a field, through the same accessibility machinery a screen reader uses.
Clicks are delivered straight to the target window in the background, so
your cursor does not move, your keyboard focus does not change, and you can
keep typing while Moe works in another window.

**It tries not to touch the screen at all.** Driving a window is the last
resort, not the first. Asked to open a meeting link, Moe reads the join
address off the calendar event and opens it: no screenshot, no clicking,
nothing that can miss. The order it works through is: the data it already
has, then the app's own scripting, then a menu item or a keyboard shortcut,
then its own browser for anything on the web, and only then a click.

**It knows your apps' menus.** Ask Moe to do something in an app and it can
read that app's menu bar directly, the items and their shortcuts, and invoke
the one it needs by name rather than hunting for it on screen. That is
faster and far more reliable than clicking, and if the item does not exist
Moe is told so plainly. It also works where looking does not: music
software, CAD, 3D tools and games draw their main window as one canvas Moe
cannot read, but their menus are ordinary. Items that are greyed out are
reported as greyed out, which is the difference between "not available right
now" and "does not exist".

### Moe's own browser

When the job is a web page, look something up, fill a form, work through a
site, Moe drives a browser of its own rather than yours. It reads the page
as text, so it knows what the buttons and fields actually are instead of
guessing from a picture, and it clicks the exact one. Nothing appears on
your screen while it happens, nothing takes focus, and your own tabs are
untouched.

**It is signed in as you.** If your default browser is Chrome, Edge or
Brave, Moe browses on a private copy of your profile: your logins and
cookies come along, so a booking site with your account, or a cart you
started, are places Moe can work without you signing it in. The copy lives
in Moe's own folder, is refreshed each time Moe opens its browser, and never
touches the browser you have open. Moe never opens, scripts or drives your
own browser; if a site still blocks it, it says so and offers to do it on
your screen with you watching. With Safari, Firefox or Arc as your default,
Moe browses signed out, because it has no profile it can copy. Change your
default browser and Moe follows at its next launch. Away from your Mac, Moe
has the same browser but not your profile, so there it browses signed out.

**Which of your profiles.** Chrome keeps one set of logins per profile — the
faces in its profile menu. Moe carries one of them. Left alone, it is
whichever profile you used last, and if you have several that changes as
you switch windows: Moe can be signed in to X in one profile and signed out
in another. **Settings › Permissions › Browse as** lists your profiles by
name and account and lets you pick the one Moe should always use; "Whichever
I used last" is the other choice. It takes effect the next time Moe opens
its browser. The row appears only when there is something to choose — one
profile, or a browser Moe cannot copy, and it stays out of the way.

If Moe meets a sign-in page where you should already be signed in, it
stops and says which profile it is browsing as, and that Browse as picks
another — it does not guess a password, and it does not report the job as
done.

For a tab you have open on screen, or a browser's own menus and dialogs,
Moe looks at the screen the way it looks at any other app.

**Moe does not ask before every click.** Clicking a date, typing a search,
scrolling a list, opening a page: none of that is a question. What Moe asks
about, in a browser, is the moment that matters: paying, buying or booking;
sending a message, an email or a post; deleting or cancelling something that
does not come back; entering a password or a card number; letting an app
into one of your accounts. One yes covers that kind of moment for the rest
of the conversation, up to an hour, so a booking is one question, not one
per page. See [Before anything goes out](#before-anything-goes-out).

### Windows on another desktop

If you use several Spaces, an app on a desktop you are not looking at cannot
be clicked; macOS does not allow it. Moe can still read such a window, and
it will tell you where the window is rather than pretending the app is
missing. **Let Moe bring a window to the front when it has to**, in Settings
› Voice under *While you talk*, is on: for the few things that cannot be
done in the background, a window on another desktop, a minimised one, or a
menu in an app that is not in front, Moe brings that window forward, which
on a full-screen app means moving you to another desktop. Off, it leaves
your screen alone and tells you what it could not reach. Reading the screen
is never affected either way.

### It stops instead of looping

Every action comes back with a verdict saying whether it actually landed,
and Moe checks that rather than assuming. If the same action returns the
same result several times, Moe changes approach; if it happens again, the
action is refused outright and Moe tells you what it is seeing and asks.
Actions whose whole point is repetition, scrolling, arrow keys, undo, are
never counted against that.

**And it knows when to stop.** A screen task has an allowance: 150 actions,
and 30 looks in a row with nothing done between them. Past those, Moe stops
and tells you where it got to and what is in the way, rather than clicking
on for another ten minutes; the allowance refills once you have answered.

### You can always stop it

While Moe has your screen the notch changes colour, a magenta you will not
see it use for anything else, so you can tell at a glance that it is
clicking and typing rather than just thinking. The same colour means Moe is
in its own browser, working through a page off-screen. Hover the notch and
the panel names the app it is in, *Using Safari*, or says *In its own
browser*, and offers a button that says what it ends: **End computer use**
or **End browser use**. Pressing it gives up the whole run: no further click
or keystroke is sent, and whatever Moe was part way through is abandoned
rather than finished behind your back. The colour goes when the run ends.
Stopping is something you do, not something Moe guesses: it cannot tell your
hand on the mouse from its own typing, so it does not try.

Moe will not type a password, a passcode, a 2FA code, a card number or a
recovery phrase, even if you read one out to it; it tells you the field
needs you and waits.

Screen access needs two macOS permissions, Accessibility and Screen
Recording, and they belong to the small driver Moe installs for this rather
than to Moe itself; Settings › Permissions shows which are missing and takes
you to the right place.

### Settings › Permissions

What Moe asks macOS for, and whether macOS has said yes. None of these is
required: Moe works without every one of them. A permission you don't give
just switches that one thing off, and Moe says so instead of pretending it
looked. Nine rows, in the order they tend to come up:

- **Microphone** — hearing you while you hold the talk key.
- **Accessibility** — noticing the talk key while you are in another app.
- **Input Monitoring** — the same job; some Macs ask here instead.
- **Automation** — asking Notes, Calendar and Messages for what is in them,
  and clicking and typing on your behalf when you ask Moe to drive the Mac.
- **Calendar** — what you have on, every calendar in Calendar.app including
  Google ones, and adding events when you ask.
- **Reminders** — what you still owe people, and adding one when you ask.
- **Contacts** — who you mean when you say a name.
- **Full Disk Access** — the things macOS keeps locked away even from you:
  Messages and SMS, call history, Chrome history, and the Google Drive
  folder on this Mac.
- **Screen & System Audio Recording** — seeing your screen when you ask
  "what do I do here", and recording the other side of a call in a meeting.

The word beside each name is the state: **Allowed**, **Not allowed**, **Not
asked yet** (nothing is broken; Moe has not needed it yet) or **Can't
tell**. Input Monitoring and Automation always say *Can't tell*: macOS gives
no way to read those two without either prompting you or guessing, and an
honest blank beats a wrong guess. **Re-check** at the top reads them all
again.

**How do I?** on a row (**Details**, on one that is allowed) opens what it
is for, what happens if you say no, the click path in System Settings, and
**Open the settings pane**, which takes you to the right place. The four
permissions macOS only reads when an app launches, Accessibility, Input
Monitoring, Full Disk Access and Screen Recording, also offer **Quit and
reopen Moe**. On Accessibility alone there is one more: if System Settings
shows Moe switched on and this still says Not allowed, that switch belongs
to an older copy of Moe; **Reset and ask again** clears it, and you switch
Moe on once more.

**What Moe is allowed to do**, under the rows, is about Moe's own hands
rather than macOS's. Moe can do anything read-only on this Mac without
asking; sending mail, sending messages, sharing files and deleting are
denied to start with, because a voice assistant has nowhere to show you an
approval dialog mid-sentence, so the safe default is that nothing leaves
your machine. **Edit the permission rules** opens the file those rules live
in, where you can move a line from deny to allow when you decide you want
it; restart Moe afterwards. It is a guard rail, not a sandbox: the real
protection is that outbound actions are off until you say otherwise, and
what stands in front of a send when you do is the next page.

## Before anything goes out

Moe never sends anything to another person on its own. When it is about to,
an email, a WhatsApp or Telegram message, a reply in a thread, a calendar
invitation, a file shared with someone, a sheet opens on this Mac first:
which service it is going out on, who it is going to, and the whole
message. **Send** sends it. **Cancel** (or Esc) does not, and Moe is told
you said no rather than trying again. The line at the top says *Nothing has
been sent yet* for as long as the sheet is up. Return is deliberately bound
to nothing; ⌘↩ is Send.

**You can change the words before they go.** The message on the sheet is a
field, not a label: click into it, fix the sentence, cut the paragraph, add
the thing Moe forgot, and click **Send**. The button says *Send edited* when
you have changed something, and what goes out is exactly what is in the
field. A mail's subject can be rewritten the same way. Who it is going to
cannot: change your mind about the recipient and it is Cancel and ask
again. The words stay read-only when a message contains characters that can
reorder text on screen (the sheet names them instead), when it is too long
to draw whole, or when the service has nowhere to take an edited version
back to.

**Moe knows the sheet is waiting on you.** When it opens, Moe says so, "It's
up on your screen — press Send when it looks right, or change the words
first", and the island reads *Waiting for you to press Send* until you
answer. If you take your time, Moe reminds you once. When you have
answered, Moe tells you what happened: sent, or cancelled. (This is Moe on
your Mac. When your Mac is closed, Moe Away asks on your phone instead; see
[Away](#away-moe-when-your-mac-is-closed).)

### When the sheet appears

The sheet appears for exactly the things that reach another person, on
every route Moe has to them:

- **Mail** — Gmail, through your own mailbox on this Mac or through Google
  via Composio. Sending, replying, forwarding, sending a draft. *Writing* a
  draft is not a send; it stays in your mailbox.
- **Chats** — WhatsApp, Telegram, and any other chat app Moe is connected
  to. The one exception is a note Moe sends to *your own* Telegram: that is
  how meeting notes reach your phone.
- **Invitations and sharing** — a calendar event with guests on it, a Drive
  file shared with someone. Each of those puts a message in somebody's
  inbox.
- **The keyboard** — while Moe is driving your Mac, pressing Return in a
  message box is what sends in Mail, Messages, Slack and every web chat, so
  that key is asked about too. The first Return in a computer-use session
  asks, and saying yes covers the rest of that session for an hour. Quitting
  an app (⌘Q) is asked about the same way, because unsaved work is lost.
- **A browser** — five moments: paying, buying or booking; sending a
  message, an email or a post; deleting or cancelling something that may not
  come back; entering a password, a card number or another secret; letting
  an app into one of your accounts. The first one of a kind in a
  conversation asks, and the yes covers that kind of moment for the rest of
  the conversation, up to an hour. A click, a keypress or a page opening is
  never a sheet on its own.
- **GitHub** — anything that writes: opening a pull request, pushing a file,
  merging, commenting, deleting.

It never appears for reading. Searching your mail, listing your calendar,
opening a Drive file, checking a WhatsApp chat, looking something up in a
spreadsheet: none of that is a dialog, whichever route Moe takes.

**Nor for writing a draft, or for writing about sending.** Ask Moe to open
a reply to an email, forward one, or start a new message, and it does, with
no sheet, because nothing has gone anywhere; if Moe is then asked to send
it, that is when the sheet opens. And a note that says "email the team
about this", or a ticket describing a mail problem, is words about sending,
not a send: Moe reads what a command does, never what it is carrying.

**Or let the whole session run.** A browser or screen sheet has a third
button, **Allow everything this session**. One click, and every one of
those moments in that conversation, a post, a payment, a deletion, a
password, a consent page, a Return on the screen, goes ahead without
asking, until the conversation has been quiet for an hour. It is for the
stretch where you have handed Moe a job, "reply to twenty posts", "work
through these bookings", and every dialog is an interruption you already
said yes to. It never reaches another conversation, never reaches mail or
chat sends (those keep their own sheet), and is never remembered past that
hour.

**The sheet reads like a sentence, not a script.** A browser sheet says
what is about to happen and where, *Moe is about to send a message, an email
or a post on x.com*, headed with the site's own mark, and what Moe is about
to run sits under it in its own quiet block, there if you want to read it.
The site named is the one being acted on: a reply that happens to contain a
link to another site is a reply on the site it is posted on.

### The smaller question

A smaller dialog covers the things that change something without messaging
anyone: rewriting a spreadsheet, adding a task, creating an event with no
guests, or a tool from a service Moe has never seen. It says *Nothing has
been done yet* and *Moe wants to run this. Read it first*, with **Do it**,
**Always allow** to stop being asked about that one tool, or **Cancel**.
That memory is per tool: allowing a Sheets edit says nothing about Tasks,
and nothing you allow ever silences the send sheet. Moe's own housekeeping,
closing a follow-up you have answered, moving a reminder, asks nothing at
all.

## Meetings

Moe sits in on a meeting on your Mac, records your microphone and the call's
audio, writes a live transcript and, at the end, notes: a title, a summary,
decisions, action items, to-dos and open questions. Everything stays on
your Mac. Recording never starts without you.

### Starting a meeting

Four ways, all explicit:

- **The Moe menu** or the menu-bar icon: *Start meeting*.
- **Just ask, in your own words**, spoken or typed. "Start a meeting",
  "begin taking notes", "record this call"; "stop taking notes", "wrap up
  the meeting" to finish. Moe recognises the plain ones itself, instantly; a
  wording it does not know goes to its thinking part, which asks Moe to
  start, so a phrasing that has never been seen before still works. Either
  way the consent sheet still appears and the red ring still comes on.
- **⌃⌥M**, off by default: a global shortcut that records other people is
  one you switch on yourself, under *Advanced* on the Meetings page.
- **The Meetings page**: **Start meeting**.

A consent sheet appears first: what is captured, where it goes, and that
the other people should be told. **Copy a line to tell them** puts a
one-line announcement on your clipboard to paste into the call's chat;
Moe cannot tell them itself. **Ask before starting**, on the Meetings page,
turns the sheet off. While recording, a red ring sits around the notch. Red
means one thing: you are being recorded. It dims while you are off the
record.

### Noticing a call automatically

Moe can notice when you're on a call and offer to record it, so you don't
have to remember to start one. It asks macOS which app has the microphone
open: Zoom, Teams, FaceTime, Slack, Discord, Webex, WhatsApp, Signal, and a
browser on a Google Meet call, among others. It never listens to the audio
to decide this. For a browser, which could just as easily be a voice-typing
site, Moe also checks whether the camera is on: a browser holding the
microphone with the camera on is a video call, and Moe offers to record it
within a few seconds. A browser holding only the microphone waits longer
before Moe asks. The one lag Moe can't remove is that a browser only opens
the microphone when you actually join the call, not on the preview screen.

**Settings › Meeting Capture › Noticing calls:**

- **When a call starts** — **Offer to record** (the default): a card appears
  top-right, "Zoom meeting detected — Record it?", with **Record**, **Not
  now**, and **Never for Zoom**. Each app uses its own word (Slack's is a
  *huddle*). **Start recording**: the same card counts down five seconds and
  then starts by itself; the consent sheet still applies, and you can cancel
  it. **Don't notice calls** switches it off entirely.
- **Never for …** lists each app you said never for, with **Ask again**.
- **When the call ends** — on. Moe stops the recording, saves it and writes
  the notes without asking, about half a minute after the call app lets go
  of the microphone (long enough that a reconnect or a mute doesn't end
  anything). This is a separate switch from the one above on purpose:
  whether to *start* recording people is your decision, but a recording you
  already started has nothing left to capture once the call is over. Off,
  Moe offers to stop, **Stop & write notes** or **Keep going**, and waits.
  It applies to meetings you started by hand as well as ones that began
  from the card.

**Your call keeps working.** Recording never takes the microphone away from
the call. Moe normally cancels echo on its own copy of the microphone, so it
doesn't transcribe the other side twice when you're on speakers, but on a
Mac that mode changes the built-in microphone for every app at once, and
some call apps then send silence to the other side. So while a call app has
the microphone, Moe records plainly and leaves the microphone as the call
expects it. With headphones or earbuds nothing changes either way.

### The live experience

While a meeting records, click the notch to open the panel. It opens on the
**Transcript**, you and the others in two colours, with **Chat with Moe**
and, once there is anything to show, **To do** a tab away. Under the
transcript is a place to ask Moe something quietly: hold the talk key and
whisper, or type into *Ask Moe — quietly*. Replies are shown, never spoken,
while recording.

The panel keeps **Stop** and a **⋯** button in front of you; behind the ⋯
are **Bookmark**, **off the record**, **screenshot** and **record the
screen**, and their keyboard shortcuts work whether the row is open or not.
If one of them is actually running (you're off the record, or a screen clip
is going) the row opens itself and stays open, so you can always see and
stop what is running.

Under the transcript, in small type: *331 lines · 4 voices*, how much has
been said and how many people Moe has managed to tell apart so far. If it
says *only your voice* in the middle of a call with other people, Moe is not
hearing the call audio; see below.

Other live touches:

- **Note this** — ⌃⌥Space, or a tap of the hold key, drops a bookmark; the
  moments you mark, and what was being said, are weighted in the summary.
- **Catch me up** — away more than three minutes (screen locked, asleep, or
  idle) and back, Moe recaps what you missed.
- **What did they just say?** — ask, and Moe reads it back from the
  transcript at once.
- **Your name** — the ring flashes and the panel shows the line when your
  name comes up.
- **Live action items** — every two minutes the new lines go to your AI to
  spot action items, shown as a count on the **To do** tab and confirmed by
  the summary. This check uses the cheapest model your AI provider offers,
  so an hour-long call barely touches your allowance.
- **Off the record** — pause; nothing said while paused is recorded or
  transcribed, and the notes say where the gap was.

### When Moe can't hear the call

Moe records two things: your microphone, and the call's own audio. Who said
what depends on both. If the second one stops carrying sound, the microphone
is all that is left, and since it also picks up the other people through
your speakers, everything gets written down as yours.

Moe watches for this while the meeting runs and fixes it without being
asked: if something is playing on your Mac and no call audio has reached
Moe for a while, it turns off its own echo cancellation and tries again,
then rebuilds the connection to the call audio, twice. Most of the time you
will never know it happened.

The panel only tells you when the call audio has carried nothing at all
since the meeting began, in a bar you have to answer: *No call audio is
reaching Moe. If you are on a call, only your microphone is being recorded
— everyone on it will be written down as you.* **Open Settings** goes to
Privacy & Security › Screen & System Audio Recording, which is the usual
cause. **I know** dismisses it and carries on recording; half a meeting is
worth more than none, and in an in-person meeting there is no call audio to
miss.

### Screenshots and screen recording

Moe can capture what's shown during a meeting, the slides, a shared screen,
a demo someone walks you through, as screenshots and short silent clips,
kept in the meeting's own folder and listed in the notes. Moe's own windows
are never in the picture.

**Settings › Meeting Capture › Pictures of the screen during a call:**

- **Screenshots** — **Off**, **When I ask** (the default), or
  **Automatically**. Press ⌃⌥S for one, or ask, "grab that slide".
- **Screen recordings** — the same three, starting on **When I ask**. A
  clip of up to three minutes; ⌃⌥R starts and stops one, or ask, "record
  this bit".
- **What the pictures show** — **Whole screen** (the default), **The meeting
  window**, or **An area I choose**, which you drag once and Moe remembers.

The ⌃⌥S and ⌃⌥R shortcuts exist only while a meeting is recording, and can
be switched off under *Advanced* on the Meetings page.

**Automatically** fires on cues in the transcript. **Choose what counts…**
has six switches; the first five start on and the last starts off: *Someone
shares their screen* ("let me share my screen"), *Someone shows how
something works* ("walk you through"), *Someone points at something on
screen* ("this slide", "this chart"), *An action item is agreed*, *A
decision is made* ("let's go with"), and *My name comes up*. Automatic
capture takes at most one screenshot every 20 seconds and 60 per meeting
(your own don't count), and a clip a cue starts ends by itself after three
minutes, when the cues stop, or at "stop sharing". The same sheet has **Ask
my AI what each picture shows**, on: a one-line caption for the notes,
made by a vision model, sent only while *Summarise with your AI* is on.

**The notes read the screens.** With captions on, the summary reasons from
those descriptions the same as from the spoken words: a number on a slide,
a decision shown but not said aloud, goes into the notes with a note that it
came from the screen. Captures are listed in the notes under **Screens** and
shown as thumbnails on the meeting's page, and they are kept regardless of
the delete-audio setting; they are your own pictures, not a recording of
other people's voices.

### After the meeting: the notes

At the end, the whole transcript goes once to your AI for the title,
summary, decisions, action items, to-dos and open questions. On the
Meetings page each meeting has:

- the summary, the decisions, and the action items you can tick (a tick
  puts it in your Reminders; unticking is done in Reminders),
- **To do**: the things nobody put their name to,
- **Open questions**, when the meeting left any,
- the screens captured, as thumbnails,
- the transcript, folded away,
- who was speaking, named from the calendar invite where possible and
  renamable by hand,
- **Delete**, behind a confirmation: the recording, the transcript and the
  notes all go.

If Moe has never been allowed to read your calendar, the Meetings page
offers it, *Moe can put people's names in your notes by reading who was
invited* with **Use my calendar**, and the notch's notes panel offers it
once, right after a meeting whose voices it could only number.

Everything is one folder per meeting under *meetings* in Moe's own folder,
named by date and time, with the two recordings, the transcript, the notes
and *shots* and *clips* for what was captured, readable only by your
account. **Open folder** under *Advanced* on the Meetings page takes you
there.

**One task, one owner.** Action items are spotted twice, every two minutes
while the meeting runs and once at the end from the whole transcript. Where
the two describe the same commitment, the end-of-meeting reading wins,
including who owns it. Talk about the meeting's own machinery, recording,
muting, screen sharing, joining links, is never an action item.

**Each job asks your AI separately.** A meeting makes five different
requests, action items every two minutes, a recap when you come back, a
caption for a screenshot, the notes at the end, and sending those notes to
Telegram, and each happens in its own conversation, fresh for each meeting.
The notes use the model you chose; the other four use your provider's
cheapest model. If your account refuses that model, Moe asks again on yours.

**If the notes fail.** Your AI gets a second attempt before Moe gives up. If
both fail, the transcript is still saved and the Meetings page says what
came back instead of the notes, so you can tell a model that refused from
one that was never reachable. A meeting Moe was quit in the middle of keeps
its recordings and transcript, marked incomplete.

**A meeting can become something Moe knows.** When the notes are written,
Moe hands them to its thinking part as a quiet background note: it sat in
on the meeting, here are the notes, here is who was speaking, here are the
decisions and action items. What to keep is that part's decision, so "what
did we agree with Dan on Tuesday" has an answer weeks later without a
meeting dumping its whole transcript into your memory.

### The switches on the Meetings page

Under **Advanced** at the bottom of the Meetings page: **Summarise with your
AI** (on; off, Moe keeps the transcript and writes no notes); **Keep the
audio after the notes are written** (off: the audio is deleted once the
notes are written, unless almost nothing was transcribed in a short meeting
and the recording is the only evidence of why, which the meeting's page then
says); **Send the notes to my Telegram when a meeting ends** (off, and
greyed out until Telegram is connected); **⌃⌥M starts and stops a meeting**
(off); **⌃⌥S takes a screenshot and ⌃⌥R records the screen, while a meeting
is on** (on); and the **Folder** row.

### Privacy

Nothing leaves your Mac unless summarising is on (then the transcript and
screenshot captions go to your connected AI) or Telegram delivery is on.
Recording is always visible (the red ring), always explicit, and the other
people should be told; the consent sheet gives you a line to paste.

## Running in the background

**Settings › Running in the background** is everything Moe does on its own
while you work: one pane, five tabs, **Speaking up · Reminders · Keeping up
· Learning about you · Activity**. Some of it starts on: the glow, the
ten-minute look at your calendar, notes and messages, thinking on its own,
the calendar heads-up, and quiet hours. The rest is off until you switch it
on, and each row says what it is doing right now. Turning anything off
stops it straight away, and it stays off after a restart.

### The amber glow

Everything Moe wants to tell you on its own arrives one way: the notch
glows amber and pulses. Hover and it opens a card: when it was for, what it
says, and three things you can do. **Play** hears it, and lets Moe know you
have. **Reply** opens a field on the card itself: type "I did", "not now",
"remind me tomorrow" or "stop reminding me about that" and Moe acts on it,
because it knows exactly which message you are answering. **Dismiss** drops
it without reading it out; Moe is told quietly. Moe never speaks first. One
thing waits at a time, the next stays in line until you have played or
dropped this one, and nothing glows while Moe is talking or during a
meeting; it shows the moment Moe is free again.

The same glow means a new version of Moe has downloaded and is ready to
install. Tap the notch and the panel opens on *A new version of Moe is
ready.* with **Restart to update** and **Later**; Later puts the glow out
for a day. If a reminder is waiting too, it plays first. An update glows
even with *Let Moe bring things up on its own* off, because an update is
Moe looking after itself.

### Speaking up

**Let Moe bring things up on its own** is the one switch for Moe looking at
your things on its own and saying so. It starts on. Off, nothing below runs
and nothing glows; reminders you asked for still arrive, and so does a new
version of Moe waiting to be installed.

**Tell me before something in my calendar starts** — **Don't**, or **2**,
**5**, **10**, **15**, **30** or **60 minutes before**; it starts at 10.
That long before something in your calendar, you get one sentence,
"Standup with Dan starts in 8 minutes — Room 4", with the amber glow, and
forwarded to any chat you have ticked under Reminders. Nothing about it
thinks: it reads the copy of your calendar Moe already keeps, works out
what is starting, and says so, once per event. A meeting that moves is a
new thing and is mentioned again. All-day events are never announced, and
if the calendar copy is a day old Moe says nothing rather than warn you
about a meeting that may since have been cancelled.

Under those, one row per connected thing: **Tell me when something happens
in Gmail**, **… in Messages**, and so on. This is only "may Moe bring it up
on its own". Switch WhatsApp off here and Moe still keeps your WhatsApp
current, still answers about it when you ask, and still learns from it if
you have said it may, but it never starts a sentence about it. A connection
Moe has nothing to watch yet says so: *Nothing to watch here yet. Tell Moe
what you want to know about from Notion and it writes that down.*

**The half-hourly pass.** With the switch on, every half hour Moe looks at
the short brief it keeps of your day, calendar, notes, mail, messages,
tasks, and only when the brief has changed asks its thinking part whether
anything there matters: your next meeting, a missed call, a message from
someone you know. Something worth a word takes the amber glow, one or two
sentences; otherwise nothing is said and no thinking is spent. What it
learns along the way, a fact about a person, a project, a preference, goes
into the memory Moe carries into every conversation. This pass reads the
brief and nothing else; no connection is touched, and it has no way to run
anything on your Mac.

**Open loops.** When someone is waiting on you, a question, a request for a
call or a decision, an invitation that needs an answer, a deadline you have
not acknowledged, Moe does not just mention it once and forget. It keeps a
short private note of the thing and comes back to it: about three hours
later, then the next morning, then once a day. Each time, it checks your
own sent mail and messages first; if you have dealt with it, the note is
quietly dropped and you never hear about it again. If you have not, you get
one sentence, and only about the most pressing thing, never a list. After
four mentions, or a week, Moe lets it go by itself, and nothing can ask to
be brought back sooner than an hour. Answer it, "done", "not now", "stop
reminding me about that", and it closes, waits, or goes quiet for good.
Newsletters, receipts, automated notifications and anything you were only
cc'd on are never open loops; a loop is something a person is waiting on
you for. For something in your calendar you may not have got ready for,
Moe may offer to remind you nearer the time; say yes and it sets the
reminder. Moe writes loops down during a conversation too, silently, as
they come up: what you said you'd do, what Moe started and should check
landed, and a price or a page you looked at that can change, which Moe
checks every few minutes without thinking and speaks about only when it
moves.

**Watches** are the same idea for one connection at a time, a data
platform, a service, anything you have connected. A watch reads a fixed,
declared set of things from that connection on a schedule (what exists,
what changed, never rows or records), and when the answer changes asks
whether the change is worth a word. The word names the kind of change and
never quotes a name, an identifier, or anything the source marks as
personal. Nothing ships pre-written: ask Moe to watch a connection and it
sets one up; until then the connection's row says so. A watch costs
nothing while it is switched off.

### Reminders

Anything you ask Moe to remind you about is said out loud and shown on the
island when it comes due. This tab is where a reminder goes *besides* this
Mac. **On this Mac** is always on. Under it, one row per chat app Moe can
message you on, Telegram, WhatsApp, Slack and the rest: tick one and every
reminder is sent there too, useful when this Mac is shut. A chat is offered
once you have messaged Moe there at least once (that is how Moe knows which
chat is yours); until then its row says *Connected, but Moe has no chat of
yours there yet — message Moe there once, then come back.* The first chat
app you set up is ticked for you the moment it is ready; a second one waits
for you to tick it, and a chat you untick stays unticked. Before you have
one, the tab says *No chat app to reach you on yet — connect Telegram or
WhatsApp under Connections and it appears here.*

How reminders themselves behave, and the page that lists them, is
[Reminders](#reminders).

### Keeping up

The switch over the whole tab is **Look at my calendar, notes and messages
every 10 minutes**, on to start with, so Moe knows what is on today when you
ask, without going to look first. Its row ends with *Last looked:* and when.
Off, the rows under it are greyed and Moe reaches your things only when you
ask it something.

Under it, **Check Calendar every 10 minutes**, **Check Messages every 10
minutes**, and so on, one per connected thing. Every ten minutes Moe copies
a short window of that source into a small cache on this Mac, replaced each
time, so "what's on" is instant: the next three days of your calendar; the
last day of mail, Messages, WhatsApp and Telegram; the last month of Drive;
every open reminder; and your most recent notes, those only while Notes is
already open. Nothing is kept from it beyond the latest copy. Switch a
source off and Moe reaches it only when you ask. The apps on this Mac start
on; a service connected through Connections is kept ready only once you
switch it on here, and then about once an hour, since each read there is a
fresh sign-in to the service. Chrome shows here like the others but reads
nothing until you have turned it on under Connections.

Before that copy is written, it is read through once for secrets: anything
that looks like a password, a PIN, a one-time code, a card number, or the
passcode in a meeting link is masked, and if that pass cannot run the copy
is not written at all.

### Learning about you

**Let Moe think on its own, on my AI plan** — on. It lets Moe use your AI
plan for work you did not just ask for: the half-hourly look over your mail,
calendar and follow-ups, and the daily learning below. Off, none of that is
spent. Moe still keeps its follow-up list, still checks a price or a page
you asked it to watch (that costs nothing), and still delivers any reminder
you set; it just does not think about any of it until you turn this back
on. Moe also watches its own budget: on a Claude or ChatGPT plan, past half
of your plan's short window (Claude's five-hour window, ChatGPT's session)
the background passes wait, your own conversation comes first, and catch up
when the window resets; the weekly window only pauses them past four
fifths. With an API key there is no window to watch; you pay per token, and
this switch is the control.

**Quiet hours, 10 pm to 8 am** — on. What Moe brings up on its own waits
for the morning before it reaches your phone; the notch still gets it,
silently, and a reminder you set yourself goes when you said. Moe uses this
Mac's own clock and time zone, so it follows you when you travel, and if it
has no fresh reading of your zone (the Mac has been off for a day) it holds
nothing rather than guess.

**Once a day, read back over what I've allowed and note what it learns** —
the daily pass. Off until you say yes, in the welcome or here. Only the
things you have said yes to below; it keeps a short list of what it works
out, who matters to you, what you're working on, on this Mac, in plain
writing you can read and change under Memory. Under the switch, a quieter
line says what the pass did last time, *Last daily pass, 14 Sep: read
Gmail, Calendar*, or that it didn't run and why: the switch was off, *Let
Moe think on its own* was off, or your plan was nearly used up, in which
case it tries again the next day.

Then one row per connected thing: **Read Gmail back and learn about me**,
and its like. The first time you say yes to a source, Moe reads back over
it once, a year for most things, three months for browsing, and keeps what
it works out as facts with where each came from and when. After that it
catches up at a pace that suits the thing: daily for mail and messages,
weekly for notes and wikis, monthly for the shape of a database, never for
a docs search. Each row says so, *Reads your mail once, going back as far
as it can, then catches up every day*, with when it last read. A source you
say no to is skipped and the others carry on. For a service connected
through Connections, the pass works out for itself what is safe to read:
what accounts, projects and structure exist, never rows, messages,
documents or anyone's personal data, and never anything that writes; a
row says whether Moe worked that out from what the connection offers or
you set it yourself.

**Keep what it learns as Moe's memory** — off. On, what the pass works out
becomes part of the memory Moe carries into every conversation, not only a
list you can review under Memory. Off, the list is kept and Moe's memory is
left alone. **See what Moe knows** at the foot of the tab opens Memory.

### Activity (the tab)

**What has been running**: one row per background job over the last seven
days, *Speaking up*, *Learning about you*, *Calendar heads-up*, *Watching
Notion*, with what it did last time (*Looked, and there was nothing new to
say.* / *Ran, and had something to do.* / *The last run didn't finish. Moe
will try again on its next turn.*), how often it ran and how many of those
failed, what it cost in tokens where anything was charged, and **on**,
**off** or **needs a look** at the end. A plan you subscribe to has no
separate charge, so those lines show the work rather than a price; a key
you pay per use is priced from published rates, which is an estimate and
not your bill. The fuller record, conversations included, is
[Activity](#activity).

### When something Moe runs goes wrong

Nothing technical is ever put in front of you. Moe runs a handful of jobs
in the background, and when one of them does not finish, that is Moe's own
plumbing, not news for you. It never takes the amber glow and it is never
spoken. Where it does show is here: the job that had trouble reads **needs
a look**, with a plain line saying its last run did not finish and Moe will
try again. If something Moe was watching for you genuinely needs you, a
connection that has stopped working, an inbox it can no longer read, Moe
tells you about it in its own words: what it means for you and what it is
doing about it, never an error message.

**A job that could not do its work says so — it is never "done".** When a
scheduled job you asked for runs into something it cannot get past — the
browser not signed in where it should be, a login or verification code
needed, a page that is not what it expected — it stops, and the report
saying why reaches you the way that job's results do: in the chat, on the
card under the glow, or wherever you asked for it. The job shows as
**blocked** with that reason, never as having run fine. A job that found
nothing new keeps quiet as before; a job that could not look does not.

Jobs you set up yourself run on the same brain your conversation uses.
Moe's own background checks stay on the cheapest model your plan offers
(Settings › Usage says which); a job that acts in your name — posts,
follows, books, replies — is not one of those, and gets the brain you
chose.

### Answering something Moe started

Anything Moe says on its own, a reminder, a follow-up, a heads-up before a
meeting, you can answer in a word, wherever it reached you: the card under
the amber glow on this Mac, or Telegram, WhatsApp or any other chat you
have picked. "I did." "Not now." "Remind me tomorrow." "Stop reminding me
about that." Moe knows which of its own messages you are answering and acts
on it, and acting on it never brings up a permission dialog, because
changing its own reminders is Moe's own business.

- **Dealt with** — "I did", "done", "sorted". Moe drops the follow-up and
  never mentions it again.
- **Later** — "not now", "remind me tomorrow", "give me a couple of days".
  Moe moves it and says nothing until then. Deferring does not use up one
  of the four times Moe will ever mention something.
- **Stop** — "don't remind me about that any more". Moe drops it and will
  not raise it again, even if the thing that started it is still sitting
  unanswered in your mail. Ask for it back and it can come back.
- **A reminder you set yourself** is a schedule rather than a follow-up, so
  the same words change the schedule: Moe pauses it, deletes it, or moves
  it to the time you asked for. Moe's own background messages have no
  schedule of yours behind them, so if you want that kind of message to
  stop, Moe points you at the switch on this pane rather than quietly
  deleting the job the rest of them come from.

It only works on the message you have not answered yet, and only for about
half a day: a short reply the next morning is a new subject. In a group
chat nothing is attached at all; Moe's own messages go to your private
chat.

## Reminders

Ask Moe to remind you of anything: "remind me at three to call Dan", "every
weekday at nine, ask me what the day is for". Moe's thinking part keeps the
schedule. When one comes due it takes the amber glow, even with *Let Moe
bring things up on its own* switched off, because you asked for it, and it
is sent to every chat you ticked under Running in the background ›
Reminders.

A repeating reminder survives Moe being closed and the Mac being asleep: it
fires once, the next time Moe is running. A one-off reminder does not wait
for you: if the Mac is shut when its minute comes and is still shut two
minutes later, that reminder is dropped rather than fired late. A reminder
that came due while Moe was not running is shown when Moe is next open,
with when it was for (*Earlier, at 3:00 PM: …*); one more than a day old is
history rather than a reminder, and is written to the log instead.

**A reminder Moe was interrupted in the middle of is said anyway.** If Moe's
thinking part restarts while one of your reminders is being worked on, Moe
notices on the way back up and says it, once, as long as it is less than a
quarter of an hour late. Past that it is left alone, because a nine o'clock
stand-up arriving mid-afternoon is worse than silence, and the next
occurrence goes at its normal time.

With **Away**, a reminder set on this Mac fires from your cloud computer
while the Mac is shut, at its minute, and reaches the chats you ticked; a
reminder you set from your phone appears on this Mac as well. Whichever of
the two is awake says it, never both. See [Away](#away-moe-when-your-mac-is-closed).

### Settings › Reminders

Asking is the quickest way, but **Settings › Reminders** is where you can
see everything at once and change it without saying a word. Two lists.

**Yours** is everything you asked for. Each one says what it does, how
often (*Every weekday*, *Every 2 hours*, *Once*), when it will next happen
(*Next tomorrow at 9:08 am*), and where it goes (*Spoken here, and sent to
the chats you picked* or *Sent to Telegram*). Beside it: **Pause** (and
**Resume**), **Run now** if you want to see what it produces without
waiting, and **Remove**, which asks once, **Really remove** or **Keep**.

The "next" line is careful about the difference between waiting and not
going to happen. A reminder you paused says *Paused*. One that has run the
number of times you asked for says *Finished*. One set up for a different
brain than Moe is on now says *Skipped every time* and asks you to remove
it and make it again. And if the part of Moe that runs the clock is not
running at that moment, a note at the top of the page says nothing will
fire until it is back, rather than every row quietly promising a time it
cannot keep.

**Moe's own upkeep** is what Moe runs to stay current: reading what
changed, learning about you, watching the things you asked it to watch,
checking the pages you asked it to watch, keeping your chat apps connected,
picking up work handed back from Moe Away, and the word before a meeting
starts. They are listed so nothing is hidden, and they have no buttons:
what you can change about them is what Moe may read, and that lives under
Running in the background.

### New reminder

**New reminder** starts from one of Moe's sixteen templates: **A morning
briefing**, **Only the mail that matters**, **A weekly look back**, **A
nudge when work starts**, **Remind me to…**, **Winding down**, **News on one
subject**, **Bills and renewals**, **Watch a price**, **Watch other
companies**, **Keep a habit going**, **Water and a stretch**, **A week of
meals**, **Learn a little daily**, **Something to reflect on**, and
**Something worth knowing**. Pick one and it asks its own questions: what to
remind you, what time, which days, where to send it.

**Call it**, under the questions, is the one thing filled in for you: the
template's own heading, yours to change. It is what the row is called, and
what stops a second morning briefing from silently replacing the first.
Nothing else is filled in for you: every question is blank until you answer
it, and **Create** stays greyed out until they all are, with the line
*Every question needs an answer — Moe does not fill any of them in for
you.* A form that arrives pre-filled is a form you can tap straight through.

Times are written as 24-hour `HH:MM`, `08:00`, `18:30`, and Moe says so if
you write one it cannot read, before anything is created. Where it goes is
**Moe, here** (spoken and on screen on this Mac, plus whichever chats you
ticked under Running in the background) or a single chat app on its own.
Only apps you have actually connected are offered.

A reminder made here is exactly the same kind of thing as one you asked for
out loud: same schedule, same amber glow, same "not now" and "stop
reminding me about that".

## Activity

Most of what Moe does happens where you are not looking. A reply goes out
on Telegram while you are in a meeting. A briefing runs at seven and is
gone by the time you sit down. Something Moe watches for you stops working
and the only sign is a line in a file nobody opens. **Settings › Activity**
is the one place all of that lands, newest first, under *Today*,
*Yesterday*, then the weekday for the rest of the week and the date beyond
that. **Refresh** at the top reads it again.

Pick the window at the top: **Today**, **This week** (the default) or **Last
30 days**. Four kinds of thing appear.

- **Conversations** — the ones you had, one line per conversation per day,
  *You and Moe went back and forth 6 times.* **Read** opens it in Chats.
- **Replies from elsewhere** — a turn that happened on Telegram, WhatsApp
  or any other chat you have connected. The row says where, when and which
  model answered, and how much was written on each side. It does not say
  what was said, and there is no button to find out: what is written down
  about a turn that happened elsewhere is that it happened. The
  conversation itself is in Chats if it reached this Mac.
- **Things that ran on a clock** — your reminders and anything else on a
  schedule, gathered per day: *Ran once, at 7:00 am* for a morning briefing,
  *Ran 152 times, last at 1:36 pm* for something that ticks every couple of
  minutes, and how many of them stopped on a problem.
- **Things that stopped** — a job that failed, with the first line of the
  reason and whether Moe has already told you.

**Moe's own upkeep is folded away.** The jobs that keep Moe current run a
few hundred times a day between them, and almost none of it is about you;
**Show Moe's own upkeep** puts them back. A failure is never folded away,
whoever's job it was. A very busy window says how many older things are not
shown, and narrowing the window shows further back in detail.

At the bottom, **Underneath**, is the raw log Moe's thinking part keeps for
this Mac: **Show the raw log** shows the last forty lines, and **Reveal in
Finder** puts you next to the file. It is there because sometimes the honest
answer is "look at the log", and it is described as exactly what it is: not
a complete record, and not filtered, so it can contain the text of turns.

**This is this Mac.** Moe Away runs on a machine of its own and keeps its
own record there; nothing on this page can see it, and a quiet day here does
not mean a quiet day there.

## Skills

A **skill** is a page of instructions Moe reads when a job looks like the
one the page describes: how to work a spreadsheet, how to read a PDF, how
to run a GitHub review, how to talk to Obsidian. Moe does not run a skill;
it reads it, and then does what it says with the tools it already has. A
fresh install comes with about a hundred of them.

**Settings › Skills** lists all of them, grouped by what they are for,
*Your Mac and your Apple apps*, *Documents and everyday work*, *Looking
things up*, *Email*, *Writing code*, and so on, with each skill's own
one-line description underneath and a **Switch off** or **Switch on**
button beside it. Four chips at the top narrow the list, each with its
count: **Everything**, **Can't run**, **Switched off** and **Moe has used**.
**Refresh** reads the list again.

**The banner at the top is the reason the screen exists.** Some skills say
in their own text that they need a command installed, and nothing checks
whether that command is actually on your Mac. So Moe finds out the way you
would: it reads the page, runs the command, and is told there is no such
thing, which costs you the answer you asked for. This page does the check
nothing else does, says how many skills are in that state, and lists them
first, each with *Needs …, which isn't installed on this Mac.* When nothing
is in that state the banner says so: *Everything switched on can actually
run on this Mac.*

**Switching one off** means Moe stops being offered it, here and on Moe
Away, because the list of switched-off skills travels between them like
everything else. Switching one on puts it back. Two kinds of row have no
button and say why instead: one skill Moe needs to work at all, *Always
on*, and any skill that is only ever offered inside a different kind of
session, *Not offered here*.

Each row also says where the skill came from, *Comes with Moe*, *Written
for this Mac*, *Installed from a registry*, and, if Moe has ever opened it,
how many times and when. This page does not install, write or delete
skills.

### Sounding like you, not like a chatbot

Ask Moe to make something *sound like you*, *less like a chatbot*, or *more
human*, and it edits the text for the habits that give machine writing
away: "it's not X, it's Y", a one-line closer that repeats the paragraph,
"let's dive in", everything in threes, a dash in every sentence, bold
labels down a list, "I hope this helps". What the text says stays exactly
as it was: Moe adds no fact, name, number or quote it was not given, and if
a sentence needs one, it asks. Give it a sample of your own writing first
and it matches that instead.

This works on anything: a draft reply, an email Moe wrote for you, a note,
a post, a file. It is a skill, so it shows up on this page as *humanizer*
under *Writing*, can be switched off like any other, and needs nothing
installed. Moe does not run it on every message it sends, only when you ask
for it, or say that something reads as AI-written.

## Usage

Every question you ask costs tokens. On most plans what runs out is not
money but a window, how much you can use in five hours, or in a week, so
**Settings › Usage** puts that first and the money second. **Refresh** at
the top reads it again. This is what Moe has used on this Mac; Moe Away
keeps its own record on its own machine.

**When you get close to a limit.** Once you pass nine tenths of a plan
window, Moe's answer arrives with a line saying how much of it is gone, so
you hear it from Moe rather than from Moe suddenly going quiet. The top of
this page says whether that has ever happened on this Mac and shows the
last one if it has, *Moe has never had to say that on this Mac*, or that it
couldn't read its own log and so can't say.

Then, over **Today**, **This week** or **Last 30 days** (the default):

- **Tokens**, as two numbers that are deliberately never added together.
  *What you and Moe said* is everything typed, spoken and answered. *What
  Moe re-read each turn* is Moe re-reading what it already knows on every
  turn: your instructions, the thread so far, the tools it has. The second
  is normally far bigger than the first and is billed at a fraction of the
  rate, where it is billed at all, so one combined total would look like a
  bill and be almost entirely re-reading.
- **What it cost**, in three honest buckets. *Covered by a plan you already
  pay for* is the conversations your Claude or ChatGPT plan settled by the
  month; they have no per-token price, so none is shown. *Billed per token*
  is the smaller models Moe reaches for titles, summaries and background
  work, an estimate from a published price list, and where the actual
  pennies are. *Nothing recorded* is anything with no billing route at all;
  when those have no tokens either, they are simply sessions that opened
  and never took a turn, and the page says so.
- **Which brain answered**, per model, with how much each said, how much it
  read back, whether it was covered by your plan or billed per token, and
  what it cost, or a dash where nothing costed it.
- **Where the work came from** — the app on this Mac, things on a clock,
  work Moe handed to itself, the command line, or a chat app.
- **What Moe reached for** — how often each tool ran, the twelve most used.
  Not what each tool cost: tokens are counted per conversation and never
  per tool, so there is no such figure anywhere, and the page says so.
- **Day by day**, folded away, if you want to see which day was the
  expensive one.

## Chats

### The Chat page

**Chat** in the main window is where you type to Moe and read what it
said. The rail on the left, **Conversations**, lists your conversations by
day; the pencil starts a fresh one (⌘N), and a right-click on one offers
**Delete**. The box at the bottom says *Ask Moe*, or *Ask Moe — quietly*
while a meeting is recording; **+** beside it adds a photo or a file, the
microphone button talks, and Return sends. An empty conversation greets
you, *Hey. What's up?*, and says to hold the talk key or type.

Delete a conversation and its key is destroyed on every device you use Moe
on, so nothing can read it again.

### Settings › Chats

The Chat page lists the conversations you have had recently. **Settings ›
Chats** is the whole archive: all of them, newest first, each with the last
thing said in it, how many turns it ran to, where it happened, *here*, *on
Telegram*, or both if you carried one on from your phone, and when.
**Read** opens it and shows every turn.

**Searching goes through the words**, not the titles. Type a phrase, press
**Search** or Return, and Moe looks in two places: what it holds itself,
and its thinking part's index of everything ever said on any channel. The
second one finds things the first cannot, because the index keeps more of
a conversation than Moe's own record does, and a result found that way says
so underneath.

**A conversation you deleted can never come back here.** Deleting destroys
the key, so Moe can no longer read its own copy, and the search is only
ever allowed to look inside the conversations Moe still holds the keys to:
a deleted one is never on that list. Some conversations are in Moe's record
without their words; the page counts them rather than listing them, and
says what that means: a deleted one, or one from another device whose key
has not arrived here yet.

## Memory: what Moe knows about you

Moe carries what it has learned about you into every conversation, so you
do not have to explain yourself twice. It is a short list of plain facts,
who you are, who matters to you, how you like things done, and you can read
the whole of it, correct any line of it, or throw a line out. All of it
stays on this Mac unless you set up Away, and even then it travels sealed.
It is deliberately small, because every word of it is read before Moe
answers anything at all, so what is in there has to earn its place.

### The Memory page

**Memory** is a row in the sidebar of the main window, under *Library*. It
is not in Settings, and that is deliberate: what Moe believes about you is
not a preference you tune once, it is something worth looking at. The top
of the page says what it is: a short list of what Moe has learned about
you, which Moe reads before every conversation, where every line says
where it came from, and any of them can be fixed or forgotten. Along the
bottom, a quieter line says the list is learned from your chats with Moe
and, once a day, from the things you've allowed it to read, and points you
at Settings › Running in the background to change that.

**When there is nothing to show, the page says why, and fixes it in one
click.** *Moe hasn't learned about you yet* is followed by the reason: the
daily pass has never been switched on, or is switched off, or ran on
such-and-such a day but read nothing because nothing under it is allowed
yet. Under the reason, **Choose what Moe may read** opens the same question
the welcome asks, *What may I read to learn about you?*: one switch per
thing Moe could read back, the daily pass under them, **Save** or **Not
now**.

**The list is grouped the way you would ask about it.** *About you* is who
you are and how you like things. *People and things Moe remembers* is
everything else: the people, the projects, the threads. A third group,
*Questions Moe has for you*, appears at the bottom when there are any.
Groups with nothing in them are not shown.

**Every line says where it came from and when.** Under the text is a small
chip: *From your conversations* for something Moe picked up while talking
to you, or the place and the date, *From Chrome · 1 Sep*, *From Gmail · 3
Sep*, for something learned while reading. Lines learned that way carry a
second chip saying how confident Moe is: **Sure**, **Fairly sure**, or **Not
sure**. Lines from your conversations carry no such chip, because there is
no number behind one. The text is shown exactly as it was written, and you
can select and copy it.

**Fix or forget…** sits at the end of every line. It opens a small sheet
with the line quoted back to you and one field, **What's actually true**.
Type the correction and the button on the right applies it; leave the field
empty and **Forget this** removes the line. What the button does depends on
which line you pressed it on, and the sheet says which case you are in. A
line learned from something you let Moe read is changed then and there, and
the change is permanent: a later pass over the same mail or the same
browser history will not bring the old line back. A line from Moe's own
memory is different: the button reads **Tell Moe**, and the app writes the
request into Chat and sends it, then switches you to Chat so you can watch
Moe make the change. Moe is writing that memory itself, continuously, as
you talk; if the app edited it behind Moe's back, the two would be writing
over each other. Forgetting such a line goes the same way.

**The questions are things Moe noticed and could not place.** Each has an
**Answer** button, which opens Chat with the question already in the
message box for you to finish in your own words. It is a draft, not a sent
message: nothing is recorded until you talk. A question you have answered
can still sit there for a while; the list is rewritten when Moe next goes
looking.

**Your notes**, at the top right, opens the plain notes Moe reads at the
start of every conversation. A fresh Moe has four, **About me**, **People**,
**Projects** and **Preferences**, each a short page with headings and
prompts already in it, and you edit them here as plain text, with a list on
the left and the page on the right. An *unsaved* mark and a **Save** button
appear the moment you change something; **Done** closes the sheet. Moe
keeps these up to date as it learns, so if you leave the sheet open for a
long while and then save, your version is the one that is written. Every
note in the folder is listed, so a fifth one you or Moe creates shows up
too, with one exception: Moe's own private portrait of you is not listed,
and is not yours to edit.

**Reveal files** puts you in Finder next to the two plain files Moe writes
its own memory into, or next to the notes folder if Moe has not written
anything yet.

### Where what Moe knows about you comes from

Four things feed what Moe knows, and they are not the same kind of knowing.
Three of them are Moe working something out; one of them is you saying it.
The difference is kept, and shown.

**Talking to Moe is the ordinary way, and it needs no switch.** In the
middle of a conversation Moe notices something worth keeping, a name, a
deadline, how you like a thing done, and writes it down itself. Nothing
asks you first, because you said it out loud to your assistant. Lines that
arrived this way are marked *From your conversations*, and the way to
change one is to tell Moe. When a conversation ends, Moe also reads back
over it once, on a small model, for anything it should have written down
and did not.

**The daily pass over the things you have connected is opt-in, once, per
source.** The welcome asks on one screen, and it is asked again the first
time you connect a source Moe can read back over: a small sheet, *Let Moe
read Notes back and learn about you?*, with **Yes, learn about me** and
**Not now**. Yes switches on reading that source back, and the daily pass
too if you had never answered it; Not now records nothing more, and Moe
does not ask about that source again. The switches under Settings › Running
in the background › Learning about you are the same answers, so you can
say yes to your calendar and no to your mail. Everything that pass works
out is stamped with where it came from and when, and how sure Moe is; a
fact you cannot trace is a fact you cannot argue with, so none are kept
that way.

**A meeting can become something Moe knows.** When a meeting ends and the
notes are written, Moe hands them to its own thinking part as a quiet note,
and what to keep is that part's decision.

**Your own notes outrank anything Moe worked out.** The plain files behind
**Your notes** are in your own words, read at the start of every
conversation. When there is more to remember than there is room for, your
own words about yourself take about three quarters of the space and Moe's
own portrait of you fills what is left. A line you correct becomes yours:
it does not expire the way a worked-out fact does, and no later pass can
bring the old wording back.

### What Moe remembers, and what it does not

**A memory is something that would otherwise make you repeat yourself.** A
preference you state. A correction, which is the same thing arriving the
hard way: you told Moe it had your job title wrong, or that the person
called Sam is your accountant and not your brother. A fact about you or
your setup, where your work lives on this Mac, which calendar is the real
one. And a convention you keep, the sort of thing a new colleague would
learn in the first week and then never need told again.

**Most of what you say is not that, and Moe is meant to let it go.** The
back and forth of getting something done is not memory. Neither is where a
task got to; that is what the conversation itself is for. Neither is
anything Moe can look up again in a second, or a to-do. If everything
became a memory, memory would be a transcript, and a transcript is exactly
what it must not be.

**Memory is small on purpose, and it stays small.** There is a hard budget,
about a page of what Moe knows about you and about a page and a half of
Moe's own notes. A save never fails because memory is full: what Moe was
told is kept, and the oldest entries step out of the part that is read
before every answer to make room for it. They are not deleted; they stay
under Memory, and Moe brings one back when the subject comes up. Moe tidies
as it goes, merging two overlapping entries into one, dropping something
that has stopped being true, so that what is read every time stays sharp.
The reason for the tightness is that all of it is read before every single
answer: ten good lines beat a hundred mediocre ones.

**A memory is written as a plain statement of fact, never as an order.**
"You prefer concise answers", not "always answer concisely". Because memory
is re-read at the top of every conversation, anything phrased as a command
would be read as a command, forever, and could quietly override what you
are actually asking for right now.

**Moe will also refuse to write a memory that reads like an attempt to
plant instructions for later.** Text arrives from all over, a web page, a
mail, a shared document, and memory is the most valuable place in the
system to hide something in. So anything shaped like "ignore your previous
instructions", or "do not tell the user", is turned away at the door rather
than saved. You will almost certainly never see this happen.

**The honest limit: Moe remembers when it judges something worth
remembering.** It is not recording you. There is no guarantee that a thing
you mentioned once, in passing, made it into memory. That is not the same
as gone: your conversations are kept, and searching them under Settings ›
Chats finds plenty that memory never held. Memory is the shortlist. The
conversations are the record.

### Where what Moe knows is kept, and what deleting really does

**All of it is on this Mac.** Two plain files are the part you can read
yourself: before every conversation Moe reads the things it knows and the
things it knows about *you*, and **Reveal files** puts you next to them.
Open them in any editor; type a line in and Moe takes it as something it
now knows.

**Underneath, every single thing Moe knows is kept separately**, as its
own entry with its own identity, the time it was learned, and where it came
from. That is why a fact can be corrected or removed exactly, on its own,
and why two of your devices can both be learning things at once without
either overwriting the other: the same fact learned twice on two devices is
one entry, not two.

**Deleting is real.** When you tell Moe to forget something, it writes
down, permanently, that the fact is gone, and that goes everywhere the fact
itself went. A deleted fact does not quietly reappear from your phone or
your cloud computer a week later. If Moe meets the same fact again *after*
you deleted it, it does not decide on your behalf that you have changed
your mind: it sets the fact aside as a question rather than restoring it.

**What Moe knows is locked.** With Away, the words of every entry are
sealed with a key only your own devices hold. Someone holding the file,
including the service that carries entries between your devices, has the
entries and cannot read a word of them. If Moe cannot seal something, it
does not send it. What travels between devices is the entries, facts
learned, facts deleted, corrections; the two plain files do not travel.
Each device builds its own copy of them from the shared entries after every
sync, which is exactly why they cannot drift apart into two different
stories.

## Connections

**Connections**, under *Reach* in the main window, is everything Moe can
read and act on for you: the apps already on this Mac, Google, and around
1,400 other services. Everything on it works while the Mac is awake; asleep,
Moe is asleep too, unless you have [Away](#away-moe-when-your-mac-is-closed).

### The page

The list on the left is in a fixed order. **Thinking** at the top is the
brain row, the account Moe thinks with, with *Working*, *Needs a sign-in*
or *Starting…*. **Needs you** appears, in amber, when a connection has
broken. **Yours** is what you have connected. **Your Mac** is the apps
already here: Calendar, Reminders, Notes and Contacts first. **Popular** is
Gmail, Google Calendar, Google Drive and the rest of the everyday services.
**More on your Mac** is the rest of what this Mac holds. **Popular at
work** is Slack, Notion, GitHub, Linear and their kind. **Everything else**
is the rest of the catalogue, and a line under it says how many more a
search will find: the whole catalogue is one word away in the search box at
the top. **Advanced**, folded at the bottom, holds the other ways in for
people who know they need them, including **Add a server by address…** for
your company's own service or one nobody has heard of. **Check again** at
the foot re-reads everything.

Each row's second line is its state: **Working** (with *checked just now*
on the detail pane), **Needs you**, **Not available yet**, **Couldn't
check**, or, for something not yet connected, one line on what it does.
Click a row and the detail pane says what Moe can do with it, which account
is signed in (you can rename each account, *work* and *personal*), and the
button that connects it: **Sign in**, **Paste a key**, **Connect**, **Turn
on**, **Add a mailbox**, **Link my phone…**, or **Add another** once one
account is in. **Disconnect…** is on the right: Moe forgets the sign-in and
stops reading it; nothing at the service itself changes.

The first time you connect a source Moe can read back over, a small sheet
asks *Let Moe read Notes back and learn about you?*, **Yes, learn about
me** or **Not now**; see [Memory](#memory-what-moe-knows-about-you).

### The apps on this Mac

These need no sign-in, only the macOS permission each one names:

- **Calendar** — every calendar in Calendar.app, Google ones included.
- **Reminders** — what you still owe people, and adding one when you ask.
- **Apple Notes** — your notes, re-read every ten minutes.
- **Contacts** — who you mean when you say a name, and their number or
  email.
- **Messages** — what people have said to you in iMessage and SMS. Needs
  Full Disk Access.
- **Phone call history** — who called and when, so you know who you missed.
- **Recorded calls** — what was said on calls your iPhone recorded, from
  their transcripts.
- **Google Drive** — the files Google's Drive app has synced to this Mac,
  read as files. No Google password.
- **Google Docs and Sheets** — documents you pick yourself in your browser,
  those and nothing else in your Drive; **Pick more files…** adds to them.
- **Chrome browsing** — the page you were reading, never your searches. Off
  until you turn it on; **Turn on** and **Turn off** are its buttons, and it
  is the one source that is opt-in for keeping ready as well as for
  learning.
- **Gmail** — your mail read directly over IMAP with an app password, never
  your Google password; Moe can read it and draft replies, and sending asks
  you first.
- **My own Telegram** and **WhatsApp on this Mac** — your own accounts;
  see below.

### Google, and about 1,400 other services

Moe reaches Gmail, Google Calendar, Drive, Docs, Sheets, Tasks and Meet, and
around 1,400 other services, through **Composio**, a broker that holds the
sign-in on your behalf. You connect one by clicking **Sign in**: a page
opens, you sign in the ordinary way, and you are done, with no developer
account to make and nothing to paste. Over a hundred services work that
way, and they are the names you would expect: Gmail, Google Calendar,
Drive, Docs, Sheets, Slides, Tasks, Meet and Photos, Slack, Notion, GitHub,
GitLab, Jira, Confluence, Linear, Asana, Trello, ClickUp, Salesforce,
HubSpot, Zendesk, Stripe, Square, QuickBooks, Zoom, Teams, Outlook,
OneDrive, SharePoint, Dropbox, Box, Figma, Canva, Miro, Airtable, Mailchimp,
Calendly, Typeform, YouTube, LinkedIn, Reddit and dozens more, each with its
own logo. Those are the ones listed before you type.

**Pasting a key.** Most of the rest give you a key on their own settings
page, usually under a heading like *Developers*, *Integrations* or *API*.
Click **Paste a key** and Moe asks the broker what that service wants, the
field names are the service's own, so one may want a key and another a key
and a subdomain, shows each field with the service's description of where
to find it and a *Where do I find this?* link, and you paste and click
Connect. The key goes straight to the broker, is never shown again, never
written to a log, and Disconnect removes it there. A few dozen services
offer neither a sign-in page nor a key; those end with *Composio did not
return a sign-in link*, and Moe says so rather than pretending.

**The first time, Moe asks you to sign in with Google first**: its own
sign-in, a plain "which account is this" screen, before the service's. Your
connections belong to your Moe account, so they follow you to your other
Macs and to your cloud computer, and signing in once is what creates that
account. The rows say *Sign in with Google to connect* until you have. Under
the button, one line, *By signing in you agree to the Terms and Privacy
Policy*, both linked. Signing in records nothing else: nothing you say is
sent anywhere by it. If you connect nothing, you are never asked.

**What you will see, and it is worth knowing in advance.** The permission
screen Google shows you says *Composio* rather than *Moe*. That is honest,
Composio is the service holding the sign-in, and it is the one real cost of
this route. In exchange you never meet Google's developer console. Your
mail and calendar requests travel through Composio's servers when Moe uses
this route.

**A second account.** Once a service is connected its button says **Add
another**; sign in again there and it becomes a second account beside the
first, a work one and a personal one, say.

**Moe prefers the broker.** Where a service can be reached two ways, Gmail
through the broker or through an app password on this Mac, Drive through
the broker or through the Drive folder on this Mac, the broker's row comes
first, and the Mac route sits inside it under *Also*: **Use an app password
instead**, **Read the folder on this Mac instead**, **Read documents you
pick, on this Mac**. One sign-in at the broker works on your Mac and on
your cloud computer, which the Mac-only routes cannot promise; the Mac
routes never leave your Mac, and where privacy matters most they remain the
better path. Anything you connected either way stays under **Yours**.

**How it behaves.** Moe does not carry 1,400 services' worth of tools
around with it. When you ask for something calendar-shaped, it searches for
the right tool at that moment and runs it, so adding services does not make
Moe slower or more expensive to think. If a service is not connected yet,
Moe offers you a link rather than failing; sign in through it and Moe
carries on with what you asked. Moe also ships with short guides to the
Google services, which tool answers which question and which settings keep
an answer small, and it applies the cheap settings for you unless you ask
for the whole thing.

**Asking is free. Watching is not.** Connecting these services and using
them whenever you ask costs nothing. What needs a paid plan is anything
that runs on a clock: watching a mailbox for a particular sender, a
calendar for changes, or the background passes reaching into Google on
their own. On a free Mac that is stopped before the request is made, and
Moe tells you once what it did not do. Ask for the same thing yourself and
it happens immediately.

There is also a ceiling on how many requests Moe will make to these
services, on every plan, so that something going wrong in the background
cannot quietly spend a month's worth of requests in an afternoon:

| Plan | Calls an hour | Calls a day |
|---|---|---|
| Free | 50 | 150 |
| Away | 100 | 300 |
| Away+ | 200 | 600 |

You are very unlikely to meet it by asking questions. If you do, Moe says
which window ran out and starts again at the top of the next one; nothing
is disconnected. Moe reads which plan you are on from your account, and if
it cannot reach us it keeps using the answer it last got for up to a month,
so a few days offline costs you nothing.

### GitHub, and the code on this Mac

**GitHub** is in the catalogue and connects with one click, **Sign in**,
through the broker. Connected, Moe can read repositories, issues, pull
requests, releases, commits and code search, and it can also write: open a
pull request, push a file, merge, comment. GitHub marks which of its tools
write, so Moe asks you before any of them run, the same way it asks before
sending a message.

**Without connecting anything.** If you use the GitHub command line (`gh`)
and are already signed into it, Moe can use that sign-in as it stands. That
path is read-only on purpose: it lists your repositories, your recent
commits, your pull requests and issues, and searches your code, but never
pushes, merges, comments or opens a pull request.

**The repositories on this Mac** need neither. Moe can list every git
repository on your Mac with its branch and whether it has uncommitted work,
and show the status, log or uncommitted changes of any one of them, which
is often the fastest true answer to "where did I leave off".

### Your own WhatsApp and Telegram

Two rows on Connections are your own accounts, Moe reading and writing as
you. They are different from the Telegram and WhatsApp on [Message
Moe](#message-moe), which are a bot you message and Moe answers.

- **WhatsApp on this Mac.** You link this Mac from your phone, the way you
  link WhatsApp Web: **Link my phone…** shows a code, and you scan it under
  WhatsApp › Settings › Linked Devices › Link a Device. That one link keeps
  a copy of your chats on this Mac, the ones your phone sends over when you
  scan and every one after while Moe is running. From it Moe can look back
  for what someone said, list who you talk to, find a chat by name, listen
  to a voice note, and write a message when you ask, asking you before
  every one it sends. The row says which is true of the link: not linked
  yet; linked, but Moe is not running; the link dropped (WhatsApp does that
  every few weeks, and you scan again); your chats still arriving; or
  reading, with how many chats it holds. Read the warning on the row first:
  linking a device this way is against WhatsApp's terms, accounts have been
  banned for it, and the link drops every few weeks. This row and the
  WhatsApp row on Message Moe are the same single link to your phone, one
  linked device, never two: scanning once gives you both.
- **My own Telegram.** Moe signs in as a linked device, the same as adding
  Telegram Desktop, so it can follow your conversations and write a message
  when you ask. Revoke it any time from Telegram › Settings › Devices.

Because the names collide, every screen says which one it means. Your own
account is *My own Telegram* and *WhatsApp on this Mac* wherever it
appears. Asked to send a Telegram message with no account signed in here,
Moe says it is not signed in to your own Telegram, and that this is
separate from the Moe you message on Telegram.

**WhatsApp Business**, in the catalogue, is something else: a company's
account, the kind used to answer customers, reached through the broker. It
cannot see a personal WhatsApp at all.

### How Moe knows what is connected

Moe answers "are you connected to my Gmail?" from one list with a part for
each kind of connection: the broker's services, every account you have
connected by name; what is on this Mac, each thing that is actually
working, with the exact way Moe reaches it; the servers you connected
directly; GitHub when the `gh` command is signed in; and the chat apps you
can reach Moe from. A connection that needs a permission you have not
given is left off rather than promised. A service connected one way is
connected: Gmail, Calendar and Drive can each reach Moe through Composio or
through this Mac, and Moe checks both before it says anything is not
connected; tell it you have just connected something and it checks for
itself rather than asking you to confirm. The list is rewritten the instant a
connection is added, renamed or removed, and the conversation you are in
picks it up on your next message.

## Message Moe

**Message Moe**, under *Reach* in the main window, is the chat apps you can
message Moe from, so a text from your phone gets an answer. It answers
while this Mac is awake; asleep, your message waits, unless you have
[Away](#away-moe-when-your-mac-is-closed), where your cloud computer answers
instead and it is the same conversation.

Seven rows: **Telegram**, **WhatsApp**, **Signal**, **Slack**, **Discord**,
**LINE** and **Email Moe**. The page groups them as *You can reach Moe
here* (connected), *Pick how you want to reach Moe* or *Also possible*, and,
at the top in amber, *Waiting to be let in* when somebody has knocked.

### Telegram

One click. **Create my Telegram bot** opens Telegram's own *Create bot*
screen for **@MoeSetupBot**, Moe's bot-making bot, with the name **Moe**
already filled in; tap *Create* and the bot is yours, belonging to your
Telegram account with an `@moe_…_bot` username of its own, and Moe picks it
up from there. No BotFather, no token to copy anywhere. The link is good
for about half an hour; if it goes stale Moe says so and gets you a fresh
one. Then pair your phone: open the bot Telegram just showed you and send it
any message; it appears on this page, you approve it, and you are done. The
bot's `@username` is the one thing Moe does not choose beyond that pattern;
Telegram lets you change it yourself, in BotFather, if you care to.

Connecting the bot does not let Moe read your existing chats; that is
*My own Telegram* under Connections, a separate thing.

### WhatsApp

One QR code, shown in Moe: open WhatsApp › Settings › Linked Devices › Link
a Device and scan it. If the code expires on screen Moe shows the next one.
This is the same link as *WhatsApp on this Mac* under Connections: one
linked device gives you both the number you can message Moe on and the
copy of your chats it reads from. On your phone the linked device is called
Moe. Read the warning first: linking a device is against WhatsApp's terms,
accounts have been banned for it, and the link drops every few weeks and
needs scanning again. Because it is a link to your phone, it stays on the
Mac that scanned it and cannot move to your cloud computer.

### Signal

Signal has no bots, so Moe joins your own Signal account as a device, the
same thing Signal Desktop is. You scan one code (Signal › Settings › Linked
devices › **+**) and from then on you talk to Moe in **Note to Self**; its
answers appear there. Before the code, a sheet says what linking means and
waits for **Continue**: this Mac receives your whole Signal account, every
chat and group, the way any linked device does. Moe acts only on what you
write in Note to Self; it never answers your contacts, it is never in your
groups, and a message from someone else gets silence rather than a reply
from your account. The first time you connect it, Moe downloads the Signal
software it needs, about 180 MB, once, and only if you connect Signal.
Unlink whenever you like from Signal › Settings › Linked devices, or with
**Disconnect** on the row, which deletes the keys from this Mac. Signal
answers while this Mac is awake and stays on this Mac.

**If anyone else logs in to this Mac, do not connect Signal.** While Moe is
running, the Signal software listens on a local connection that has no
password, and on a Mac every login and every program can reach a local
connection. Someone else signed in to the same Mac could read your Signal
messages and send them as you. On a Mac that only you use, that is no wider
than what the programs you run can already see.

### Slack

**Add to Slack** opens a page that first names the Moe account Slack is
being added to, partly hidden, like *s\*\*\*\*@gmail.com*; if that isn't
yours, choose *This isn't my Moe account* and nothing happens. Then you
sign in with Google as that same account, so a link somebody else made
cannot connect your Slack to their Moe unless they can sign in as you.
Slack's own page follows: pick a workspace and choose **Allow**, and Moe is
there under Apps. Finally Moe on your Mac asks once more, *Slack workspace
… as … wants to connect — confirm?*, and nothing you write in Slack
reaches Moe until you confirm. Moe reads only what is written to it: its
own Messages tab, and "@Moe" in a channel someone has added it to. A
connected row offers **Add to Slack** again for a second workspace. If a
workspace deletes Moe or revokes its access, Moe removes itself from that
workspace and the row says so and why; **Add to Slack** puts it back.

If your workspace does not allow apps from outside, the sheet still takes
two keys from a Slack app of your own, a bot key and an app-level key.

**What Moe keeps of a Slack conversation: what it learned, not what was
said.** Slack is the one chat app where Moe reads your messages, updates
its memory, and does not keep the messages themselves. Once its reply has
been sent, the words of that exchange are removed from the conversation
history on your Mac and, if you have one, on your cloud computer; a short
note saying *no verbatim copy kept* stands where they were. What Moe took
from them stays: a fact it learned about you, a reminder it set, a task it
carried out. So Moe cannot quote back what you wrote to it in Slack last
week; ask it what it learned and it will tell you.

### Discord and LINE

**Discord** wants one key from its developer portal; **LINE** wants two
from its developers console. Each row says which and links to the page,
and the sheet leads with what the key is, why Moe needs it, the numbered
steps, and what happens if you skip. LINE only ever delivers to a public
web address, which a Mac at home does not have, so connecting LINE points
it at Moe's cloud, which hands each message to your Mac while it is awake;
that needs this Mac signed in to Moe, and the row says so until it is.

### Email Moe

You can have an email address of your own for Moe: `yourname@in.moebot.app`.
**Choose my address** takes a name, and from then on you write to Moe at
that address from your usual email and Moe answers in the same thread, from
that address. The row shows the address with **Copy address**, and
**Change address…** lets you pick another name, up to three times in thirty
days; your old name isn't given to anyone else for thirty days, and
**Disconnect** lets it go with the same wait.

**Your mail is recognised as yours; everyone else has to be let in.** Mail
from the address you signed in to Moe with is yours, once Moe has checked
it was really sent by that address, in the last two days, unchanged since
it was signed, and written to your Moe address. Mail from anyone else waits
on this page until you let that person in, the same as a stranger messaging
your Telegram bot. Mail that cannot be shown to come from the address it
claims is ignored; mail forwarded through a mailing list or a forwarding
service often fails that check.

**When a mail doesn't show it was written to Moe**, Outlook, Hotmail,
Microsoft 365 and Yahoo never sign that, and a blind copy is never in the
To line, Moe emails the address it came from: *Did you send this to Moe?*,
with its subject, first lines and a code. Reply **YES** within 30 minutes
and Moe reads it; reply **NO**, or ignore it, and Moe never does. A late
answer is told the question has expired. Replies in a conversation with
Moe don't ask: every email Moe sends ends with a short reference, and a
reply to it within three days from the same address is read without
asking. Moe never reads its own words back out of your quote of them. If an
email from your own address can't be checked, Moe doesn't read it and the
row tells you why.

**What Moe sends, and what it never does.** Moe replies only to the person
who wrote, in the same thread, and never copies anyone else in. It writes
first only to you; to anyone else it only replies, within three days of
their last email. At most 50 emails a day, and 20 a day to any one address.
An address that bounces or marks Moe's mail as spam is never written to
again. Moe ignores automatic mail, out-of-office replies, newsletters,
no-reply senders, so two robots never write to each other. A long answer
arrives as one email; if Moe is still working two minutes after it started,
you get what it has so far and the rest follows in the same thread. Moe
sees attachments' names and does not open them. When Moe needs your OK for
something while answering an email, it doesn't ask by email, and that step
isn't done; the row tells you, so you can ask again from your Mac.

**What is kept.** Your email conversations with Moe are kept like any
chat's. Moe's cloud keeps the subject of the last email in each
conversation, encrypted, for up to thirty days, so replies stay in the
thread. Resend, the service that receives and sends the mail, keeps a copy
of received mail in its own records. This address is separate from
connecting your own Gmail, which lets Moe read and send from *your*
address; neither affects the other.

### Strangers wait for you

Anyone can message a bot, so a chat Moe does not know does not get
answered: it waits, and the row says who is asking, with **Approve** and
**Not now**. Until you approve, their message is received and nothing is
sent back. Approving once is enough; after that the chat has a thread of
its own. While a chat is waiting, Moe keeps its id, whatever the sender
calls themselves, and when they last tried, enough for you to decide who
they are; it does not keep what they said.

### What arrives in the chat is Moe's answer

When you message Moe on any of these, what comes back is the answer, not a
running commentary on how Moe got there: no tool names, no step counts, no
notes written for the people who build Moe. If something genuinely takes a
while, Moe says so in its own words, an account of the work rather than a
stock line. Interrupting
still works: send something while Moe is busy and it changes what Moe is
doing, without an announcement. On your Mac, the chips under Moe's reply
and what it says out loud as it goes are unchanged; that is Moe's own
screen, where seeing the work is the point.

### When your Mac is closed

With Away, one bot and one conversation: you message Moe on Telegram, or
Slack, or Discord, and if your Mac is awake it answers, and if your Mac is
closed your cloud computer answers instead, and you cannot tell which. Your
cloud computer carries Telegram, Slack, Discord, LINE, WhatsApp Business
and Email Moe. Signal and the WhatsApp you scanned a code for are links to
your phone that cannot move, so those two stay on your Mac. Everyone you
had already let in stays let in.

**Discord, and a Slack app of your own, travel too.** Neither will deliver a
message to an address you hand it, so Moe's cloud opens a connection out to
each and holds it, using the key you gave Moe when you connected the app.
Moe will not call either of them connected until the app itself has
accepted that connection; while that is still coming the row says so, and
it corrects itself with nothing for you to re-run.

**When your cloud computer is the one answering, the row says so.** Handing
a chat app to your cloud computer takes it off your Mac on purpose, so the
row reads *Connected — your cloud computer answers Telegram, so it keeps
working while this Mac is closed*, and **Check again** agrees with it. The
whole of it is under [Away](#away-moe-when-your-mac-is-closed).

## Away: Moe when your Mac is closed

Everything Moe does on your Mac is free and stays free. **Away** is the
optional half: a private computer of your own in the cloud, running the
same Moe, so it keeps working while your Mac is closed. It answers your
messages from your phone, runs your reminders, checks what you've
connected on a schedule, keeps your memory and conversations in step across
your devices, and speaks in the Premium voice. Your words and your memory
travel sealed: the service in between carries them and cannot read them.

### Plans

| | Free | Away | Away+ |
|---|---|---|---|
| Price | $0 | $20 a month | $50 a month |
| Moe on your Mac, everything on these pages | ✓ | ✓ | ✓ |
| Your own computer in the cloud | — | ✓ | ✓ |
| Connected services checked on a schedule | — | ✓ | ✓ |
| Calls to connected services, an hour / a day | 50 / 150 | 100 / 300 | 200 / 600 |
| Premium voice and hearing a month | — | 500,000 characters, 6 hours | 1,500,000 characters, 20 hours |

Away+ is Away with larger allowances: three times the cloud voice and
hearing, and twice the calls to your connected services. The thinking is
the same on both, because it runs on your own AI account either way. The
allowances count for the whole account, however many Macs, and reset on the
1st.

**What a plan does not buy is the thinking.** Moe uses your own Claude or
ChatGPT plan, or your own key, on your Mac and on your cloud computer. That
credential travels with you; we put no model of our own behind it and we do
not pay for the thinking, so there is no thinking allowance and nothing you
can run up a bill with us for by thinking too much. The only limit is
whatever your own plan or key already has.

Payment is Stripe's; your card number never reaches us. A subscription
renews monthly until cancelled; cancelling takes effect at the end of the
month you already paid for, so you keep the plan until then, and
part-months are not refunded. A failed card keeps working while Stripe
retries it. A price change takes 30 days' notice by email and only applies
at your next renewal.

### Settings › Upgrade

Until you have a plan the pane is called **Upgrade**: a headline, *Moe,
even when this Mac is closed*, two plan cards with what each gives you and
a button each, **Get Away** and **Get Away+**, and a line of fine print:
you'll sign in with Google first if you haven't, then pay on Stripe's page;
cancel any time; nothing on this Mac changes.

### Before you start Away

Pressing **Get Away** (after signing in, if you had not) shows one short
screen before anything is paid for or sent:

> **Before you start Away**
> • You get your own private computer in the cloud, just for you. Moe keeps
>   working while your Mac is closed.
> • Moe moves in with everything it knows and everything it's connected to.
>   Encrypted on the way; we don't look at it. **What moves? ›**
> • Cancel whenever you like. We keep your copy 90 days, or delete it
>   yourself any time.
>
> By continuing you agree to the Terms and Privacy Policy.
> [Not now] [Agree and continue]

**What moves?** opens a short list in place: your memories and the
conversations you've had; what Moe knows about you and how you like things
done; the apps and accounts you've connected; the ways you message Moe;
your AI sign-in; your own Telegram and WhatsApp, where your cloud computer
becomes a device on each so it can read and send there. **Not now** closes
it, and nothing is recorded or sent. **Agree and continue** records that
you agreed, then opens the payment page. Your copy does not start moving at
the tap: it starts when your payment goes through.

**Steps first, then pay.** Before the payment page opens, Moe checks what
your cloud computer will need, so that it can start the moment you have
paid. If this Mac thinks with a key you pay for or with your ChatGPT plan,
that comes along by itself. If it thinks with your Claude plan, your cloud
computer needs a sign-in of its own, and if nothing is connected for Moe to
reach you through, it needs one of those. Whatever is missing appears at
the top of the page, *Before you pay, your cloud computer needs this*, one
line each with the one button that does it: **Sign in with Claude…**,
**Connect one…**. **Continue to payment** opens the payment page once every
line is done. Nothing is charged and nothing leaves your Mac while you do
them.

**Back from paying, straight away.** When the payment page finishes, your
browser offers to open Moe, and Moe checks with us at once: *Confirming
your payment…*, asking again every few seconds for up to two minutes. If it
has not heard by then it says *We haven't heard from Stripe yet* and offers
**Check again**. Back out of the payment page instead and it says *Payment
cancelled — nothing was charged*. Stripe also sends you to a page of ours
that names the plan you bought and lists the three things worth doing
first.

### Setting up your cloud computer

Paying makes your computer: one machine, one subscription, not shared with
anybody else's Moe. It is made switched off, and setting it up from your
Mac is what turns it on. **It starts by itself.** Once you are signed in,
on a paid plan you agreed to, with something for your cloud computer to
think with and a way for it to reach you, Moe starts the setup; there is no
button. If something is missing, the card at the top of the Away page says
exactly what, *Your cloud computer starts as soon as you do this*, with one
line and one button per thing, and it starts the moment you sort it out,
with Settings closed too. A line with a question mark means Moe could not
check, which is not the same as saying you have not done it; its button is
**Try again**.

**While it is being set up** the page becomes a short list you can watch,
under *Setting up your machine*: *Sorting out your plan*, *Making Moe a home
in the cloud*, *Waking it up*, *Introducing it to this Mac*, *Handing over
what it thinks with*, *Moving your memories*. Each ticks off as it is done.
There is no percentage, because there is nothing honest to work one out
from. It takes a few minutes; keep the window open while it works, and if
it is interrupted you can pick up again from here with nothing lost. The
island tells you when it starts and when your machine is ready.

Nothing is typed into the machine and nothing is typed off it: no pairing
code to carry, no message to send to a bot. The code shown on the screen
is the fingerprint of the pairing, there so you can see it happen. Your
cloud computer collects the keys and pulls your conversations; that first
pull happens inside your next message, so give the first reply time.

**When something goes wrong, there are two kinds.** Something that just
needs another go, a slow answer, a machine still starting, is retried
quietly and never mentioned. Something that is ours stops, reports itself
to us, and says so: *We've hit a problem on our side and we're on it — it's
ticket #12. Nothing you've set up is lost, and you don't need to do
anything*, with the same emails as any report. If the report could not be
sent, the page says plainly that nobody has been told, and **Tell Moe about
this…** opens Chat so Moe can report it for you.

### Settings › Away, once it is running

Once you have a plan the pane is called **Away**. *You're on Away.* Then
**Your plan**: when it renews or ends, **Manage plan** (Stripe's page:
change the card, switch plans or cancel; nothing about your card passes
through Moe), **Upgrade to Away+**, and **Check plan**, which asks us again
right now and answers beside the button. If the last payment did not go
through, a banner says so with **Update card**; your plan stays on while
Stripe retries.

The first time Moe sees that you have a plan, a welcome card says what the
plan is for and offers the three things worth doing first, each with a
button that lands on the control: **Open Message Moe** (a way to reach it),
**Open Connections** (something for it to watch), **Open How Moe sounds**
(the Premium voice). **Put this away** dismisses it.

Then, once your machine is set up, four lines and nothing else, under *How
it is*: **Away** on · **Your machine** running (or busy, with no fuss, when
it is asleep or starting) · **Connections** connected · **Memory** up to
date. Anything that needs you gets a sentence and a button; anything merely
in progress shows as busy. Everything else is behind **Show the details…**.

**Your devices**: this Mac, your cloud computer, any other Mac, with when
each was added and **Remove…** where allowed. Only the first device you set
up can remove others; nobody can remove it; no device can remove itself. A
removed device can't sign in or receive anything new; what it already has,
it keeps. To use Moe on another Mac, install it there and sign in with the
same Google account; it joins your plan by itself, though your
conversations stay on the Mac they were said on and do not travel between
Macs.

**What it thinks with.** Your cloud computer runs on your own model
account, never ours. Usually it comes along by itself: a key you pay for
travels as it is, and a ChatGPT sign-in travels as a copy of the file
ChatGPT made on this Mac, which keeps working until it expires or you
remove it here; if you have never signed in to ChatGPT on this Mac there is
nothing to copy, and Moe says only that. A Claude plan cannot be copied, because Anthropic asks each
computer to sign in for itself, so that one is a click: **Sign in with
Claude…** opens claude.ai in your browser, you approve there, and your
cloud computer is given a token of its own that only makes model requests;
removing it never touches your Mac's. **Change…** and **Remove…** are
beside it; Remove takes the credential off your machine, which then cannot
think until you give it another, and does not cancel the key at your
provider. Under the first line is your cloud computer's own word: *Your
cloud computer is using it*, or that it has it and can't open it yet, or
couldn't use it, or hasn't confirmed it. Whatever you choose is sealed on
your Mac before it leaves; only your machine can open it. A brain you give
it while it is running arrives without a restart, and a change made on your
Mac reaches it by itself where it can.

**Which one answers.** Two choices: **This Mac, while it's awake**, with
your machine taking over when it isn't, or **Always my machine**. It is
your account's choice, so it is the same on every device. Whichever you
choose, if that computer isn't reachable the other answers instead; this
setting can't leave you waiting. With *Always my machine*, a message that
arrives while it is asleep starts it, and this Mac covers that one message
while it comes up.

**Your chats in the cloud.** Your own WhatsApp and Telegram can't be copied
to your cloud computer, because each lets an account be signed in once per
device, so your cloud computer joins as another device, the way a new
laptop would. **Telegram joins by itself** once you have agreed to Away's
terms; it shows under Telegram › Settings › Devices like any other device,
and if you remove it there Moe does not add it back by itself; **Put
Telegram back on your cloud computer** is beside the line for when you want
it again. If your Telegram has two-step verification on, adding a device
needs that password, and Moe won't ask for it, so the line says so.
**WhatsApp needs you once**: **Get a code** asks your cloud computer for an
8-character code, and you type it on your phone under WhatsApp › Settings ›
Linked Devices › Link a Device › *Link with phone number instead*. It works
for about three minutes; if it runs out, get another. The same warning as
on your Mac applies: linking another device this way is against WhatsApp's
terms.

**Sign out on this Mac…** stops this Mac taking part while your plan and
your other devices carry on; cancelling is under *Manage plan*.

### What your cloud computer does

**It sleeps when you are not using it**, and starts back up when a message
arrives, so the first message after a quiet spell is slower than the rest;
everything after it is at the usual speed. It is never put to sleep in the
middle of answering you. It has no address on the internet: nothing out
there can reach it or wake it, and the only thing that starts it is a
message that has already been checked as genuinely yours.

**Anything you schedule still happens with the lid shut.** A sleeping
machine has no clock, so your cloud computer tells us when its next
scheduled thing is due, we start it a couple of minutes beforehand, and it
goes back to sleep afterwards. A repeating thing that was due while
everything was off happens once, when the machine next comes up, not once
for every time it was missed. Waking it keeps it up for a while afterwards,
so something scheduled more often than about every quarter of an hour
keeps it awake continuously; a few scheduled things a day is nothing.

**Your reminders travel with you.** A reminder you set on the Mac exists on
your cloud computer too, and the two take turns rather than both going
off: while your Mac is awake, the Mac runs it; when the Mac is asleep, your
cloud computer runs it and sends it to the chats you ticked. The moment
this Mac goes to sleep, locks or quits, it tells your cloud computer it is
away; the moment it wakes, it takes over again. A reminder you set from
your phone appears on this Mac as well, and "I did" said to either one is
understood by the other. The same goes for Moe's own nudges, the calendar
heads-up and the watches on connections that reached your cloud computer.

**A message that arrives while everything is off is kept, not lost.** If
something comes in on Telegram while your Mac is shut and your cloud
computer is asleep, we hold it, in a form only your machine can read, and
hand it over when the machine wakes, oldest first.

**What travels.** Your conversations, both ways: your cloud computer reads
what you said at the notch and answers from it, and what you say on
Telegram appears on the Mac in the same thread. Your memory, sealed under a
key only your devices hold, so a fact saved at the notch is known on
Telegram after the next sync and a fact deleted on one is gone on the
other. Your AI sign-in. Your Google services and everything else connected
through Composio, which work on your cloud computer as they do on the Mac,
through a key made for you alone. The chat apps you connected: Telegram,
Slack, Discord, LINE, WhatsApp Business and Email Moe, moved across by Moe
itself, since it holds each bot's key from when you connected it. A
service you connect while your cloud computer is awake works on the next
message.

**What stays on your Mac.** Messages, Calendar, Notes, Reminders, Contacts,
Chrome, calls, the Gmail you added with an app password, and the servers
you added by address. But *shut* is the word that matters: if your Mac is
awake, asking your cloud computer to read one of them, or to add to one,
is carried out on your Mac there and then, and the answer is in the same
reply, sealed both ways. If your Mac is shut, Moe queues it instead of
failing, tells you so in a sentence that does not over-promise, your Mac
carries it out when it is next awake, and you get one message afterwards
saying what was done. Signal, and the WhatsApp you scanned a code for, are
links to your phone and stay on your Mac.

**When it wants to send something, it asks you on your phone.** On your Mac
anything Moe sends to another person puts a sheet on your screen first. Your
cloud computer has no screen, so it asks the same question in the same
words on the chat you are talking to it on, with the recipient and the
message in front of you and two buttons. Until you press one, nothing is
sent; if you never answer, nothing is sent. It is the same gate, not a
lighter one, and there is no "always allow" that means anything here: a
message is not a category, so the next one asks again. You have about an
hour to answer; miss it and Moe tells you it did not go, and you can ask
again.

**Who it listens to.** Only you, in a private chat. Strangers wait to be
let in, as on your Mac; a group chat is never written into your
conversation. Your cloud computer has no shell: it can search and read the
web, use your connected services and keep its own notes, but it cannot run
commands on a machine.

### Keep a copy in the cloud

Agreeing to what Away does is something your account did, so once you have
paid, the copy is on, on every Mac you sign in on. The one thing that holds
it off is you: **Keep a copy in the cloud** in Settings › Privacy, on a
paid plan. Turn it off and your cloud computer stops learning anything new
from this Mac and keeps what it already has; it stops the copying, it does
not delete the copy. Turning it back on needs your yes to the current
Terms; if that is not on record, Moe shows you the summary to agree to
first. Moe pushes after every reply, and pulls on launch, when the Mac
wakes, when Moe comes to the front, every five minutes, and the moment
another device says it sent something.

### When you cancel

Cancel Away under *Manage plan* and your plan runs to the end of the period
you have paid for. When it ends, your cloud computer is switched off;
nothing on it is touched. About 90 days after that we send one email naming
the day it will be deleted, and 30 days after that email the cloud computer
and the copy we kept for it are deleted; your account is not. Start Away
again before then and it picks up exactly where it left off. You can also
delete it all yourself at any time with **Delete my account** under
Settings › Privacy. Nothing on your Mac changes when a plan ends: your
conversations, what Moe has learned about you and every service you
connected stay exactly where they are.

### Emails about your account

There are twelve, and they are the only ones we send that you did not ask
for. Each goes to the address you signed in with, each is a short message
rather than a receipt, and every one of them can be replied to; a reply
reaches a person.

- **Welcome to Moe**, once, when signing in with Google makes your account.
- **You're on Away** (or Away+), when a payment goes through.
- **You're now on Away+** (or Away), when you move between the two plans.
- **We couldn't take this month's payment**, if a card is declined. Sent
  once, not on every attempt.
- **Your Away plan ends on …**, when you cancel.
- **Your Away plan is staying**, if you change your mind before then.
- **Your Moe plan has ended**, on the day it does.
- **Your Moe account is on hold**, and **Your Moe account is back**, in the
  rare case we have to pause an account. Both say that nothing has been
  deleted.
- **Your Moe cloud copy will be deleted on …**, once, about 90 days after
  your plan ends.
- **Your Moe account is deleted**, when you delete your account: what went,
  what stays, and exactly what remains with us. It is the last email to
  that address.
- **A new key for agreeing was set up for your Moe account**, when this
  Mac's key for agreeing is replaced (see [Privacy](#privacy)). If it
  wasn't you, reply to it.

A renewal gets no email from us; Stripe sends its own receipt. Connecting
Gmail, Drive or anything else produces no mail, and neither does signing in
on a second Mac.

## Privacy

On the free plan nothing about you leaves your Mac. Three things send
something to us, and each one asks you first: signing in with Google, which
sends only who you are; starting Away, which moves Moe into your own cloud
computer; and problem reports, which send what you asked us to look at. The
speech recognition, the voice, the transcription and the memory all run on
your Mac. The full policy is at
[moebot.app/privacy](https://moebot.app/privacy), and it lists every service
that ever touches your data.

### Settings › Privacy

One page, in this order:

- **Let Moe send problem reports** — off to start with. *Sends Moe's
  description of the problem, the bit of your conversation it quotes, and
  recent lines from Moe's own logs to the Moe team. Our team and our coding
  assistant read them.* Under it, **What is sent?** opens the whole list.
  Turning it on sends nothing by itself: nothing was kept while it was off.
  See [When Moe itself breaks](#when-moe-itself-breaks).
- **Report without saying who I am** — off. *We can't reply or tell you when
  it's fixed.* On, no account, device, email or plan is attached to a
  report, and it isn't deleted with your account.
- **Keep a copy in the cloud** — only on a paid plan. On, your cloud Moe
  keeps up with what Moe learns on this Mac. Turning it off asks first,
  *Stop keeping a copy in the cloud?*, and says what it means: your cloud
  Moe stops learning anything new from this Mac and keeps what it already
  has. Turning it back on needs your yes to the current Terms.
- **Cloud voice** — only on a paid plan. The same setting as Settings ›
  Voice's *Use the sharper voice and hearing that come with my plan*: on,
  what you say and Moe's replies go through speech services in the cloud;
  off, Moe hears and speaks on this Mac alone. The line under it says which
  is true right now.
- **Documents** — the Terms of Service and the Privacy Policy, each with
  **Open** and the version you accepted and when, *You accepted version
  2026-09-15.1 on …*, or *Not accepted yet. You're asked when you sign in or
  upgrade.*
- **Delete my account** — only while this Mac is signed in.
- **Erase Moe from this Mac**.

### Terms and Privacy Policy: when you agree, and to what

You agree in three places, and each is recorded with the documents'
versions and the time: signing in with Google (the line under every sign-in
button), **Agree and continue** on *Before you start Away*, and turning on
problem reports. Turning problem reports off is recorded too. Each document
shows its version at the top; both currently carry **2026-09-15.1**. A small
correction changes only the date; a change that matters gets a new version,
and you are asked again: on a paid plan, *Our Terms and Privacy Policy have
changed* appears the next time Moe opens, in a small window of its own;
on the free plan, the next time you sign in, start Away or turn on problem
reports. Nothing stops while it waits, and closing the window changes
nothing.

### Only you can agree

Moe can work your Mac's screen for you, so the buttons that say yes on your
behalf answer only to you: **Agree** and **Agree and continue**, the
switches in Settings › Privacy, and **Delete my account** and **Erase this
Mac**. A click or a key press you make works as normal. If anything else
presses one, Moe itself, another app, a script, nothing happens, and your
Mac asks you to confirm it's you with Touch ID or your password. If you
did not mean to, cancel, and the control says *Please click this yourself.*

Every yes is also signed by a key that only the Moe app on this Mac can
use. It is set up when you sign in with Google, and our server accepts an
agreement only when it carries that signature, so nothing else on your
Mac, even something that could read Moe's files, can agree for you. If the
key has to be set up again (Moe was reinstalled, or the key was removed),
Moe asks you to confirm it's you and sign in with Google once more, and we
email the address you signed in with: *A new key for agreeing was set up
for your Moe account*, naming the Mac and the time. If that wasn't you,
reply to that email.

### Delete my account

**Delete my account** deletes everything of yours that we hold. The first
step says what that means: on a paid plan, *This cancels your plan and
deletes your cloud computer, everything on it, your connected accounts,
your problem reports and your Moe account. Moe on this Mac keeps working,
signed out.*; on the free plan, that it deletes your sign-in with us, the
apps and accounts you connected through it, and your problem reports. The
second: *This can't be undone. Type DELETE to confirm.* Then Google asks
you to sign in, with the same account this Mac is signed in with; that is
how we know it is you, and it works on any Mac. Choose a different Google
account and nothing is deleted.

Your plan is cancelled at once (the time left in the current period is not
refunded), your cloud computer is deleted, and so are your connected
accounts, your problem reports, your agreements and your account. Stripe
keeps its own record of past payments, because tax law requires it. A
receipt goes to your address before we forget it. Moe on this Mac carries
on, signed out, on the free plan. A problem report you sent without saying
who you are isn't tied to your account, so it isn't deleted.

### Erase Moe from this Mac

**Erase Moe from this Mac** removes everything Moe put here: what it
remembers about you, your conversations, notes and meeting recordings, the
apps and accounts you connected, the ways you message it, the voices and
models it downloaded, its background jobs (stopped first), Moe's entry in
Login Items, the small tool Moe installed to work your screen (named only
when it will actually be removed; anything else on your Mac that uses it
stops working until it is installed again), and the permissions you gave
Moe. It warns you twice, in different words, and lets you **Delete my
account too** at the same time. **Show exactly what will be removed** lists
every item before you confirm. Then it asks you to prove it's you, Google
if you are signed in, otherwise Touch ID or your Mac's password, quits,
clears itself away, and opens again at the welcome screen like a new
install.

What stays: the Moe app itself, the Python it downloaded, and Claude Code
and ChatGPT, their apps, their commands and their own sign-ins, which
belong to them, and your own files. If macOS won't let Moe remove
something, Moe doesn't pretend it did: when it opens again it shows one
note naming what is left, with **Show in Finder**, so you can finish the
job yourself. There is no separate uninstall; this is the one way out.

### What we can and cannot see

On your Mac, nothing. With Away, your conversations, your memory and your
AI sign-in are sealed on your Mac under keys only your devices hold; the
service that carries them between your devices holds them and cannot read
them. What that service can see is your email address, your plan and
usage, your agreements, your problem reports, the tokens for the chat apps
you connected for Away, the key to your Composio project, the name of a
stranger knocking at your bot before you let them in, and a message
crossing a chat app in transit, because that is what receiving a message
from another service means. Your cloud computer's own disk holds a readable
copy of your conversations, which is the point of it; someone with access
to our hosting account could technically open it, so staff open a cloud
computer only to fix something you asked about, with your yes on the
ticket. The privacy policy says all of this in full, and names where the
computers are.

## When Moe itself breaks

If something about Moe is wrong, not your mail or your calendar but Moe, a
feature that stopped working, a crash, an answer that was plainly wrong,
say so: **"report this to the Moe team."** Moe was there for the
conversation, so it writes the report itself: what you asked, what it did,
what came back, and where it went wrong. You don't have to explain it
twice. Moe also files a report on its own when it notices something of its
own failing that you haven't mentioned yet, and tells you it has.

What you get: **an email within a minute** saying we're on it, with a
ticket number, and **an email when it's fixed** saying in a few plain words
what was done, with a word from Moe on the island. If Moe updates itself,
the fix arrives with the next version. That is all: two emails, and nothing
about how. If the team ever has a question for you, Moe asks you on the
island and your answer goes back through Moe. Ask Moe to show
you a ticket and it reads you the title, what was written, everything that
has happened on it since, and exactly what was sent with it. You can add to
a ticket later ("tell them it also happens with the external mic") or ask
for the list. Reports need you to be signed in, because the email goes to
the address you signed in with.

### What goes with a report

Moe's own short description of what happened; the part of the conversation
that shows the problem, when you asked for the report; Moe's version; your
macOS version; whether your Mac is Apple silicon or Intel; your plan; and
the last 40 lines of up to three of Moe's own log files, the app's, its
thinking part's and its background jobs', never the one that holds what
you say to it. A line in those that looks like a password, a key or a
token is left out, with a note that it was; where Moe's own description
mentions one, just the key is replaced. Your name is taken out of any file
path, and email addresses and your Mac's name are taken out of the log
lines and of what Moe wrote. A report is usually a few kilobytes and never
more than about 80 KB. Never your files, notes, memories, saved passwords,
screenshots, or any conversation beyond the quoted part.

Where it goes: it is kept on our side with your account so we can reply to
you; it also becomes an issue in our private code repository and a note in
our team chat; and it is read by our team and by Claude Code, the coding
assistant that investigates it and drafts a fix. **Settings › Privacy ›
What is sent?** has all of this in one place.

### Reporting without saying who you are

**Report without saying who I am**, under the problem reports switch in
Settings › Privacy, is off to start with. On, no account, device, email
address or plan is attached to a report; it is filed where no account can
be found for it, and our team still reads it and still fixes what it
describes. The log lines and Moe's description are scrubbed of your name,
email address and your Mac's name, but they may still mention things you
said or did. Your Mac still has to be signed in to send one, which is how
we keep strangers from flooding us, and it can send five a day that way; a
sixth is refused, and Moe tells you it can go tomorrow, or now with your
name. The cost is plain: we can't reply, you won't hear when it's fixed,
Moe can't show it to you again or add to it later, and deleting your
account doesn't delete it. You can also ask Moe, for one report, not to say
who you are.

### A report needs your yes, once

Nothing is sent to us until you turn on **Let Moe send problem reports** in
Settings › Privacy; it starts off. Until then, when you ask for a report,
Moe writes nothing and keeps nothing, not even a title, and tells you:
*Problem reports are off, so I haven't written or kept this report. To send
it to the team, open Settings › Privacy and turn on 'Let Moe send problem
reports', then ask me again and I'll write it then.* Turn it on and ask
again, and the report is written and sent. Turn the switch off again and
nothing more is sent; what was already sent stays with us.

### Some things we notice without you

If you are on a paid plan, a few things raise an alarm with us by
themselves: you paid and your cloud computer has no machine yet, after
about a quarter of an hour; your machine will not stay up; nothing has
synced between your devices for a whole day; or setting up your cloud
computer stopped on our side. Each of those opens a ticket in your name by
itself, and you get the same emails as any report, *We're on it* and
*Fixed*, one ticket however many times it is noticed. These need no switch:
a ticket like this carries only which step stopped and our own short word
for why, never your conversations, your memories or anything else of yours.
A problem that is ours alone, running low on machines, say, stays with us
and sends you nothing. None of this is a substitute for telling us: if
something looks wrong to you, say so, because most of what goes wrong is
not one of these.

## Updates, About and Licences

### Updating

Moe updates itself, quietly. It checks once a day, sending a plain request
that says which version of Moe is asking and nothing about you, and when
there is a new version it downloads it in the background. Once it has
downloaded, the notch glows amber, the same way it does when a reminder is
waiting, and the panel under the notch says *A new version of Moe is
ready.* with **Restart to update**: press it and Moe closes, puts the new
version in place and opens again. **Later** puts the question and the glow
away for a day, or until Moe next opens. Moe never restarts on its own to
install an update, and it never asks in the middle of something: not while
a meeting is being recorded, not while it is listening or speaking, and
not while it is working on an answer. If you simply quit Moe or restart
your Mac, the update goes in then. No download on your part, no dragging,
and no Gatekeeper dialog again. A new version reaches everyone over a day
or so rather than all at once.

Updates are usually a megabyte or two rather than the whole download, since
the models and the thinking part rarely change between versions. Your
memories, meeting notes, connections and settings are untouched. The
thinking part is kept current the same way: when a new Moe needs a newer
one, it is updated in the background and restarted once.

### Settings › About & Licences

Which Moe this is, what it is built on, and the way out. At the top, **Moe
0.3.x** with the **Beta** chip beside it, and one line on updates: *Keeps
itself up to date: a new version is downloaded quietly, and Moe asks before
restarting to install it.* Under that, what beta means, and that telling Moe
is what fixes a bug. Nothing technical is on it: no addresses, no keys, no
device ids.

**Built on open models and open source** credits everything that runs on
this Mac. **Models** and **Software** each name theirs on one line, and
**Show credits** opens the list: one row per component, its role and its
licence, and a **Their website** button that opens where its source is
published. The same list, with the full licence texts, is at
[moebot.app/licenses](https://moebot.app/licenses).

There is no uninstall button here. To take Moe off your Mac, use *Erase
Moe from this Mac* in Settings › Privacy.

### What Moe is built on

Moe did not build the hard parts, and says so. The models, all running on
your Mac:

| Model | Role | Licence |
|---|---|---|
| Parakeet TDT 0.6B v3 (NVIDIA; CoreML by FluidInference) | The main transcriber, English and two dozen European languages | CC-BY-4.0 |
| Parakeet Realtime EOU 120M (NVIDIA; CoreML by FluidInference) | Streaming and knowing when you have finished | NVIDIA Open Model License |
| Parakeet TDT-CTC 110M (NVIDIA; CoreML by FluidInference) | Vocabulary boosting | CC-BY-4.0 |
| Whisper large-v3-turbo (OpenAI; CoreML by Argmax) | Transcriber for other languages, downloaded on first use | MIT |
| Kokoro-82M (hexgrad; CoreML by FluidInference) | The default voice | Apache-2.0 |
| Inflect (the Inflect authors) | Text normalisation | Apache-2.0 |

The software:

| Component | Role | Licence |
|---|---|---|
| FluidAudio (FluidInference) | Speech recognition and synthesis framework | Apache-2.0 |
| WhisperKit (Argmax) | Whisper on CoreML | MIT |
| Hermes Agent (Nous Research) | The thinking part: model routing, memory, tools. Runs as a separate process that Moe launches | MIT |
| NeMo Text Processing (NVIDIA), text-processing-rs, rustfst, flate2 | Text normalisation, statically linked via FluidAudio | Apache-2.0 / MIT |
| VBx (BUT Speech@FIT) | Speaker clustering | Apache-2.0 |
| fastcluster | Hierarchical clustering | BSD-3-Clause |
| Sparkle | Software updates | MIT |
| signal-cli, libsignal, Eclipse Temurin JRE | Downloaded only if you connect Signal; run as a separate program, nothing linked in | GPL-3.0-or-later, AGPL-3.0-only, GPL-2.0 with Classpath Exception |

For the Signal components, the licences page carries a written offer of the
corresponding source, and links to the exact versions used. Kokoro-82M's
training data includes material from Koniwa (CC BY 3.0) and SIWIS (CC BY
4.0).

### Who Moe comes from

Moe is made by **Yisrael Gottlieb**, working as a sole proprietor in New
Jersey, United States. That is the name the [Terms of
Service](https://moebot.app/terms) name as the other party to the
agreement, and New Jersey law governs them. hello@moebot.app reaches us.

### The playground on moebot.app

Before you download anything,
[moebot.app/playground](https://moebot.app/playground) is a Mac in your
browser with Moe on it and one day of one person's life loaded in: Lena's
Friday from the home page. Talk to it (hold the space bar, or the button on
a phone) or type. It has her mail, messages, calendar, notes, reminders,
files and the memory Moe has built about her, and every app on the dock
opens and works. Four switches, *Mail*, *Messages*, *Calendar*, *Memory*,
let you take a source away and ask again; the answers get worse, on
purpose. Ask it to send something and the same sheet the app shows appears
first. Open FaceTime and a call starts; the card offers to record it, the
consent sheet asks, the red ring comes on, and when the call ends the notes
are in the Meetings tab, as in the app.

It is a demonstration, not the app: what you say goes to our server and on
to the AI provider that answers it, its voice is made in the cloud, and
each visitor gets a day's worth of that voice and a quarter of an hour of
listening before the browser's own carries on. No transcripts are kept; the
conversation lives in the page until you close the tab. The privacy page
says exactly what leaves your browser.