Jules vs OpenMausBot

Jules

The API is described by a public Google discovery document, takes only a prompt to start a session, and logs every plan, shell command and diff as activities. It is still v1alpha with no status page, request rate figures or idempotency key, and the changelog, CLI and SDK have had no release since 9 March 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.

Jules

1. Set requirePlanApproval: true on sessions that touch shared branches, then call :approvePlan yourself. API sessions otherwise run their plan without review
2. Session creation has no request ID. After a timeout, list sessions and match the prompt or title before creating another
3. Poll activities with a create_time filter and cache them. Activities never change once written
4. Read the request fields from the discovery document at https://jules.googleapis.com/$discovery/rest?version=v1alpha. The field tables on jules.google render empty
5. Budget against the daily task quota of 15, 100 or 300 by plan. New sessions are refused until the rolling 24 hours reset

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