GAIA vs Zo Computer

GAIA

GAIA's source is public, so its approval gate, memory store and token handling can be read. Three approval modes and per-tool overrides exist, but the default mode in the source runs every action unasked, which the privacy policy and release notes do not say. Pro costs $30 a month and self-hosting is limited to noncommercial use.

Zo Computer

Zo publishes an OpenAPI file, Markdown docs, plan prices and a named list of the providers that receive user content. One access token grants full access to the workspace, no approval step before sending or buying was found in the reviewed docs, and no status page, rate limit or SLA is published.

GAIA

1. Set Settings > Approvals to Always ask or Auto before connecting mail. The default in the source runs every action, including send and delete, without asking.
2. Expect no public API on the hosted service. The backend turns off its OpenAPI document in production, so reach GAIA through its apps, bots or CLI.
3. Check the plan before relying on the hosted service. The README and docs describe a Free plan, and the pricing page says GAIA is a paid product.
4. For self-hosting, prepare Docker, Node.js 20, a WorkOS account and a model key first, and confirm the use is noncommercial under the licence.
5. Add outside tools as MCP servers by URL on the Integrations page. GAIA asks before adding a server in every approval mode.

Zo Computer

1. Send POST https://api.zo.computer/zo/ask with Authorization: Bearer zo_sk_... and an input string. The owner creates the token under Settings > Advanced
2. Pass persona_id for a persona with a narrow tool set. The token itself carries every permission the owner has
3. Set memory_mode to off to keep workspace memory out of a request. The field is in the OpenAPI file and absent from the API guide
4. Do not retry /zo/ask blindly after a timeout. No idempotency key is documented and the request may already have sent a message
5. Append .md to any guide or reference URL for Markdown