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.

ZoneForStart here
TutorialsGetting up and runningInstallation & first launch
How-to guidesDoing a specific jobWorking fast · Analyzing documents
ReferenceLooking up an exact detailCapability catalog
ExplanationUnderstanding the designPrivacy & security

Finding your way around

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

DestinationWhat it holds
ChatHome. Also the workspace for Agents, Workflows, and Activity, which appear as tabs across the top.
ProjectsOne place per case, client, or job. Also holds Documents, the files OOMU has created.
ConnectionsApple apps, Google Workspace, cloud AI providers, tools on this Mac, and messaging channels.
ModsInstall and manage .oomu packages.
On this MacThe ledger. How much work ran locally, how much ran in the cloud, and what that saved.
SettingsModels, 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

How-to guides

Reference

Explanation


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 1Beta 2
In-app file sandbox, Sovereign Trust policies, resource budgetsmacOS 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 networkMods supply knowledge files and saved data. Nothing else runs.
A unified Task control plane over every runtimeActivity, a live view of chats and workflow runs
Remote control from a paired device or messaging appMessaging channels are delivery only: Telegram or Discord receive routine results
Three-way project data policyTwo states: Only this Mac or This Mac and the cloud
Signal, WhatsApp, Microsoft 365, SlackTelegram 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.