Documentation
Documentation
Everything you need to install OOMU, work with it, and understand how it works, organized into four clear zones.
OOMU is a private AI workspace that runs on your Mac. A small model trained by us reads every request and decides whether it can be answered on this Mac or genuinely needs the cloud. Most of the time the answer is your Mac, and nothing leaves it.
This documentation covers OOMU Beta 2: a ground-up rebuild. If you used Beta 1, read What changed in Beta 2 below before anything else.
| Zone | For | Start here |
|---|---|---|
| Tutorials | Getting up and running | Installation & first launch |
| How-to guides | Doing a specific job | Working fast · Analyzing documents |
| Reference | Looking up an exact detail | Capability catalog |
| Explanation | Understanding the design | Privacy & security |
Finding your way around
The sidebar has four destinations, with On this Mac and Settings below them:
| Destination | What it holds |
|---|---|
| Chat | Home. Also the workspace for Agents, Workflows, and Activity, which appear as tabs across the top. |
| Projects | One place per case, client, or job. Also holds Documents, the files OOMU has created. |
| Connections | Apple apps, Google Workspace, cloud AI providers, tools on this Mac, and messaging channels. |
| Mods | Install and manage .oomu packages. |
| On this Mac | The ledger. How much work ran locally, how much ran in the cloud, and what that saved. |
| Settings | Models, security, Mac access, storage and privacy, GDPR & EU AI Act disclosures, background work, appearance, language, and your profile. |
Two things live outside the window: 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
.oomupackage and understand what its trust badge means.
How-to guides
- Working fast: The Quick Launcher, quick actions, and the quick switcher.
- Connecting services: Apple apps, Google Workspace, cloud models, local tools, and messaging channels.
- 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, 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 after OOMU closes.
- 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 router behind them.
- Enterprise security: Air-Gap Mode and the hardware-signed audit ledger.
- Building a Mod: A developer's guide to packaging an
.oomufile.
Reference
- Capability catalog: Every native action OOMU can take, by identifier.
- Mod package specification: The
.oomuarchive,manifest.json, and the Beta 2 ABI. - 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 in Beta 2
Beta 2 is not an update to Beta 1. It is a new application with a new bundle identifier (ai.eldris.oomu.gpd.beta2), its own database, and its own Keychain namespace. It does not read Beta 1 data, though it can import a Beta 1 agent from a file.
The largest change 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 removes all of it and defers 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.
| Beta 1 | Beta 2 |
|---|---|
| In-app file sandbox, Sovereign Trust policies, resource budgets | macOS TCC and Gatekeeper, with a live Mac access panel in Settings |
| Signed capability bundles and a curated registry | .oomu Mods with a three-state trust badge and a narrow static ABI |
| Mods executing WebAssembly, injecting prompts, calling the network | Mods supply knowledge files and saved data. Nothing else runs. |
| A unified Task control plane over every runtime | Activity, a live view of chats and workflow runs |
| Remote control from a paired device or messaging app | Messaging channels are delivery only: Telegram or Discord receive routine results |
| Three-way project data policy | Two states: Only this Mac or This Mac and the cloud |
| Signal, WhatsApp, Microsoft 365, Slack | Telegram and Discord ship. Slack and Microsoft 365 are build-gated. |
New in Beta 2: the Quick Launcher on ⌘⇧Space, quick actions that turn pasted text into finished documents, twenty-seven Apple app actions and a menu bar item, Ask Documents and document comparison, Air-Gap Mode and a Secure Enclave-signed audit ledger, a PowerPoint engine, and full parity across twelve languages.
Status. Written against OOMU 0.2.0, the Beta 2 (Apocalyptic Captain) 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.