Coming soonOOMU is launching soon. Downloads will open at launch.
OOMU
← All documentation

How-to guides

Working Remotely

Ask OOMU to start, steer, approve, and stop work while you're away from your Mac; without ever putting your credentials or files on the other end.

There are two ways to reach OOMU when you're not at the keyboard:

  1. Messaging channels (available now); Signal, Telegram, WhatsApp, or Discord.
  2. A paired companion device (backend built; pairing currently turned off; see below).

Both reuse the same local Task authority. Remote access never turns your Mac into an open gateway: a remote request can only do what you've explicitly allowed, and it can never see a password or browse your files directly.

Controlling OOMU from a messaging channel

Once you've linked a channel under Connections → Messaging (see Connecting Services), the authorized owner of that channel can:

  • Start a task or run a Routine now.
  • Check status of running work.
  • Pause, resume, or cancel a task.
  • Approve or decline an action OOMU has paused on.

Every channel-issued decision is bound to the exact task, action, arguments, expiry, and channel identity, so an approval means "approve *this* action," not "approve anything." Only the owner you configured can drive OOMU; messages from anyone else are ignored.

When work finishes, OOMU delivers an artifact reference or a bounded summary to the channel; never a raw local file path or private payload. Consequential actions still require valid, task-scoped authority; a channel can approve within its scope, but it can't grant OOMU new powers.

This is what makes a scheduled Routine genuinely useful on the move: it can finish a weekly brief, message you the result on Signal, and wait for your "go ahead" before it sends anything out.

Pairing a companion device

OOMU is built to pair a phone or browser client with a short-lived QR/challenge flow and device-bound keys, granting it a revocable, Project-scoped, task-limited set of rights. The design guarantees:

  • The device can start and check work, but can never see your passwords or browse your files directly.
  • Only a revocable public identity is stored locally; no provider, connector, Keychain, or database secret ever goes to the device.
  • You confirm each pairing on your Mac, choose which Projects the device may use, and can remove it at any time; removal immediately blocks new commands and access to protected results.

Status: pairing is currently turned off. As the app says today: *"OOMU needs a companion phone app and a secure connection before a phone can start or check work. Those pieces are not available yet, so pairing is turned off."* Until the companion app ships, use a messaging channel for remote control. When pairing opens, you'll manage trusted devices under Connections (the Remote devices surface).

What remote access can never do

  • Receive your credentials, tokens, or unrestricted view of your filesystem.
  • Enumerate Projects you didn't grant it.
  • Expand its own scope, or approve an action outside the classes you allowed.
  • Replay a stale or expired command; commands are signed, nonce-bound, idempotent, and fully audited.