Pi vs OpenMausBot

Pi

Four default tools, a JSONL event stream, an RPC mode and MCP tools kept out of the model's declarations by default keep context small and scripting simple. Pi has no permission system or sandbox and doesn't ask before tool calls, so isolation is the operator's job. Version 1.4.0 is dated 21 October 2026.

OpenMausBot

A bounded 20-tool MCP server with typed schemas, annotations and idempotent sends, and a headless CLI with JSON output and exit codes, let another agent hand work to a bot team and wait on it. New bots start at Full access, so provider permission requests pass without a card, and usage analytics stay on until switched off.

Pi

1. Run Pi inside a container or VM for unattended work. It has no sandbox and doesn't ask before running shell commands
2. Use pi --mode json and wait for agent_settled. A failed response doesn't set a nonzero exit code in JSON mode
3. Split the JSONL stream on LF only. Node's readline also splits on U+2028 and U+2029, which are valid inside JSON strings
4. Pass --no-approve or --approve in scripts to make the project trust decision explicit
5. Set PI_TELEMETRY=0 and PI_SKIP_VERSION_CHECK=1, or PI_OFFLINE=1, to stop the default requests to pi.dev

OpenMausBot

1. Ask the owner for a pairing code from Settings > Phone, exchange it at POST /api/auth/pair, and set OPENMAUSBOT_TOKEN with an explicit OMB_PORT
2. Pass a send_id with every send_bot_message and send_channel_message, so a retry returns the first receipt
3. Use wait_for_conversation instead of polling, and on needs-user stop and tell the owner a card is waiting
4. Check a bot's access level with the owner before sending work. New bots run at Full access unless defaults were changed
5. Ask the owner to switch off Settings > General > Usage analytics if nothing beyond model calls should leave the machine