Documentation

OOMU is a private AI workspace that runs on your Mac. A small on-device model reads every request and decides what kind of work it is: an answer to write, a file to read, a reminder to add, a search to run. Everyday work runs on this Mac, and nothing leaves it unless you have allowed a cloud model and the request calls for one.

This documentation covers OOMU Beta 4 (Breezy Wizard). Beta 3 is retired. If you used it, read What changed since Beta 3 below first. Your Beta 3 work comes across automatically.

---

Finding your way around

The sidebar has four destinations, with On this Mac and Settings below them:

Your Profile opens from the button at the top right of Chat. Three things live outside the window: Mochi on your desktop (⌘⇧M shows or hides it), the Quick Launcher (⌘⌃⇧Space from anywhere), and the quick switcher (⌘K inside OOMU).

---

Tutorials

• Installation & first launch: From the download to a working workspace, including the guided model setup.
• Setting up a project: Keep a case or client together, with its own files, notes, instructions, and cloud policy.
• Creating an agent: Give OOMU a named role with its own instructions, personality, and model.
• Installing a Mod: Add an .oomu package, understand its trust badge, and use its tags.

How-to guides

• Working with Mochi: The desktop companion, what it can watch for you, and the files that wait for your approval.
• Approving from Slack or Discord: Check what is waiting and approve, deny, or snooze it from your phone.
• Working fast: The Quick Launcher, @ tags, quick actions, and the quick switcher.
• Connecting services: Apple apps, Google Workspace, cloud models, the Browser Bridge, local tools, and messaging apps.
• Analyzing documents: Ask questions across a pile of files and compare contracts, all on this Mac.
• Generating documents: Produce Word, Excel, PowerPoint, and PDF files that OOMU reopens to check.
• Automating your Mac: Apple apps, shell commands, application control, the built-in browser, and screen actions.
• Building workflows: Save a sequence of steps and run it on demand.
• Scheduling routines: Run a saved workflow on a schedule, including alerts when a value changes.
• Choosing a local model: Add your own models and read what your Mac can actually do.
• How OOMU picks a model: Automatic, On this Mac, and Cloud, and the System 1 router behind them.
• Enterprise security: Air-Gap Mode, the hardware-signed audit ledger, and managed Macs under OOMU Control.
• Building a Mod: A developer's guide to packaging an .oomu file.

Reference

• Capability catalog: Every native action OOMU can take, by identifier.
• Mod package specification: The .oomu archive, manifest.json, and the declarative manifest.
• Application Bridge API: The command layer between the interface and the native engine.
• Local database schema: The encrypted SQLite tables on your disk.

Explanation

• System design overview: How a request travels from your keyboard to a verified result.
• Evidence & receipts: Why OOMU distinguishes what a model said from what actually happened.
• Privacy & security: Where your data lives and who governs access to it.
• Hybrid AI economics: Why local and cloud together beats either one alone.

---

What changed since Beta 3

Beta 3 is retired and no longer updated. Beta 4 continues its codebase, installed as its own application with its own bundle identifier (ai.eldris.oomu.gpd.beta4), database, Keychain namespace, and model folder, so the two never share anything while both are on your Mac.

Your Beta 3 work comes with you. The first time Beta 4 opens, it looks for a Beta 3 installation and copies everything in it: agents, chats, projects, workflows, memories, settings, and the files OOMU created. It copies your saved provider keys into Beta 4's own Keychain entry, so you do not enter them again. Model files you already have are linked rather than copied, so they take no extra disk space and do not download again. On a Mac with more than 8 GB of memory, setup then downloads the larger Gemma 4 E4B once. The import is one way: the Beta 3 database and Keychain are only ever read, never changed. Beta 4 also keeps its own copy of the Beta 3 database it imported from. The import only runs into an empty Beta 4, so it can never overwrite work you have already done there. Once your work has come across, you can move the Beta 3 app to the Trash.

Beta 4 imports from Beta 3 only. It does not read a Beta 2 installation.

If you had a Discord channel set up in Beta 3, it comes across, but it does not listen until you finish setup under Connections › Messaging channels and choose the one account allowed to control OOMU. Telegram destinations are removed.

If you are coming from Beta 1

No release since Beta 1 has been an update to it. None of them reads Beta 1 data, though each can import a Beta 1 agent from its folder.

The largest change from Beta 1 is philosophical. Beta 1 built its own permission system on top of macOS: a file sandbox, a permission broker, trust policies with budgets, and a capability gatekeeper. Beta 2 removed all of it and deferred to the operating system for access to your machine, where every native macOS permission is enforced. When OOMU needs your Calendar, macOS asks, once, in its own voice, and you manage it in System Settings like every other app. What leaves your machine is still OOMU's decision, gated in the engine.

---

Status. Written against OOMU 0.4.0, the Beta 4 (Breezy Wizard) public release for macOS 14 and later on Apple Silicon. Where something is gated by how your copy was built, or is not finished, the page says so rather than implying otherwise.