nanobot vs Orbits

nanobot

nanobot runs on the owner's machine under the MIT licence, with no telemetry found in its source and memory kept as files the owner can read and restore. No per-action approval step was found, and the shell sandbox and workspace restriction are off by default. Five security advisories were published between March and September 2026, all with fixes.

Orbits

Orbits is a family household app whose assistant, Bit, runs shared calendars, lists and meals, reads household email and places restaurant calls after approval, with iOS releases every week or two. No outside agent can call it, prices appear only as App Store in-app purchases, and no status page, security contact or named subprocessors were found.

nanobot

1. Set tools.restrictToWorkspace to true and tools.exec.sandbox to bwrap or seatbelt before giving it real accounts. Both are off by default
2. Run 0.3.0 or later. Earlier versions carry the published SSRF flaw in web fetch (GHSA-vc5v-6vwm-wf9m)
3. Keep allowFrom narrow on every channel and never set ["*"] on Email, which has no pairing
4. Write secrets as ${VAR} references in ~/.nanobot/config.json. Plain values are stored in clear text
5. Use nanobot -m "..." for a one-shot run, and keep nanobot gateway running for channels, schedules and heartbeat

Orbits

1. Don't plan to call Orbits from another agent. llms.txt says no public agent API is offered.
2. Tell the owner the assistant needs an Orbits subscription bought in the app, and that any trial appears only at purchase.