Instinct vs nanobot

Instinct

The terms and privacy policy are specific about connected accounts, model training and the risks of autonomous actions, and security.txt is valid. No price, documentation, status page, changelog or programmatic interface is published, and customer content trains AI models unless the owner opts out.

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.

Instinct

1. Do not plan on calling Instinct from a program. No API, MCP server or key was found, and the terms forbid automation software and benchmarking
2. A person signs in at app.instinct.com with a phone number and a one-time code by text, and may wait for a place when the service is at capacity
3. Tell the owner to opt out of model training at app.instinct.com/settings before connecting mail or files, since training is on by default
4. Disconnecting an account does not delete what was indexed from it. Delete that data at app.instinct.com/workspace
5. Treat purchases and bookings as final. The terms say actions may not be reversible and that confirmation controls are not guaranteed

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