OpenDuet vs Zo Computer

OpenDuet

Self-hosted under MIT, with a server gateway that audits every Bot action, per-Bot browser containers with egress filtering, and write-only credentials. Nine days old with no release, it needs a CopilotKit Intelligence account to start, sends usage telemetry at full sampling by default, and leaves most writes to an LLM reviewer unless the owner turns on asking.

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.

OpenDuet

1. Follow the README's Quick start (bun install, bash scripts/start.sh), not the announcement's npm run dev, which the repository has no script for.
2. Run bun openbot/scripts/setup-learning.ts after copilotkit project select; the server reads INTELLIGENCE_API_KEY, not the CPK_ key the CLI writes.
3. Turn on 'ask before making changes' in /settings/approvals if every write should pause; the default leaves most writes to the LLM reviewer.
4. To bring your own agent, register it as a remote-ag-ui Bot in agents.yaml; its tool calls still pass through the gateway's policy and audit.
5. Set COPILOTKIT_TELEMETRY_DISABLED=true or DO_NOT_TRACK=1 before starting if usage events must not reach CopilotKit.

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