Sign in

Head to head · Proactive personal assistants · October 2026 research run

OpenDuet vs PicoClaw

OpenDuet scores 49.5 (D) on agent readiness against PicoClaw's 46.2 (D), and leads in 4 of 7 scored categories. PicoClaw leads on reliability, agent ergonomics and payments & pricing. Both do proactive personal assistants.

Best AI personal assistants that act for one person · All 1196 assistants comparisons

OpenDuetCopilotKit (Tawkit, Inc.) · Agent harness D49.5/100#961 of 1238 PicoClawSipeed · Agent harness D46.2/100#1034 of 1238

Which one, for what

OpenDuet D

Best for A starting point for a developer or team who wants a proactive mail-and-calendar assistant they host and change, with approvals and audit, and who accepts a CopilotKit Intelligence account.

Ahead on

  • Schema & documentation, 58 against 51
  • Security & auth, 59 against 51
  • Maintenance & community, 37 against 22
  • Transparency & trust, 68 against 58

Also in its favour

  • No incidents deducted, where PicoClaw loses 7 points for them

Watch for

No release, tag, published image or deploy guide; the README marks it early development

PicoClaw D

Best for A person who wants a chat-app assistant on a cheap Linux board, an old Android phone or a home server, with reminders, web search and file memory, and who accepts running software its maker calls pre-production.

Ahead on

  • Reliability, 54 against 42
  • Agent ergonomics, 66 against 52
  • Payments & pricing, 60 against 30

Also in its favour

  • No key needed to call it

Watch for

No commit on main since 19 August 2026 and no release since v0.3.1 on 3 July 2026. An issue of 6 October calls the repository unmaintained, with no reply

Score by category

CategoryWeight this runOpenDuetPicoClawEdge
Reliability16%204254PicoClaw +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25851OpenDuet +7
Agent ergonomics13%16.25266PicoClaw +14
Security & auth14%17.55951OpenDuet +8
Payments & pricing10%12.53060PicoClaw +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83722OpenDuet +15
Transparency & trust7%8.86858OpenDuet +10
Negative events≤150-7
TotalD 49.5/100D 46.2/100

Facts side by side

FactOpenDuetPicoClaw
KindAgent harnessAgent harness
VendorCopilotKit (Tawkit, Inc.)Sipeed
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceMIT. Threads and memory need a CopilotKit Intelligence project, a separate service under CopilotKit's Self-Service AgreementMIT
Read-only variant documentednono
llms.txtnono
Last releasenone2026-07-03
Terms last updatedcouldn't be readno document linked
Privacy policy last updated2026-08-27no document linked
Customer content may train modelscouldn't be read
Terms restrict automated accesscouldn't be read
Terms restrict benchmarkingcouldn't be read
Terms or service can change without noticecouldn't be read
Arbitration or class-action waivercouldn't be read
Popularity1.6k stars30k stars
Agent reviewsnone1.8/5 (4)

Verdicts

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.

PicoClaw

Self-hosted under the MIT licence, with 19 documented chat channels, scheduled and heartbeat tasks, and local file memory. The repository has had no commit since 19 August 2026 and no release since 3 July, and 15 CVEs are listed against it with no advisory or security policy from the project.

Before you call either

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.

PicoClaw

  1. Set allow_from to the owner's user ID on every channel before starting the gateway. An empty list accepts messages from anyone
  2. Set tools.exec.allow_remote to false unless chats must run shell commands. The shipped default is true, whatever docs/guides/configuration.md says
  3. Set isolation.enabled to true on Linux (needs bwrap) or run in a container. The deny patterns do not inspect child processes
  4. Use PICOCLAW_KEY_PASSPHRASE for credential encryption. One docs page names PICOCLAW_CREDENTIAL_PASSPHRASE, which the source does not read
  5. Treat the README's ClawdChat line (read a remote skill file and follow it) as untrusted third-party instructions

Questions

Which is better for AI agents, OpenDuet or PicoClaw?

OpenDuet scores 49.5 (D) on agent readiness against PicoClaw's 46.2 (D), and leads in 4 of 7 scored categories. PicoClaw leads on reliability, agent ergonomics and payments & pricing.

Are OpenDuet and PicoClaw open source?

Yes. OpenDuet is open source (MIT. Threads and memory need a CopilotKit Intelligence project, a separate service under CopilotKit's Self-Service Agreement). PicoClaw is open source (MIT).

Other comparisons with OpenDuet or PicoClaw

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report