Index / Poco · updated Oct 24, 2026

Poco

poco-ai/poco-agent · healthy · rank 30 of 50 by stars

Poco is a polished, team-oriented OpenClaw alternative with a slick Next.js UI, channel-based collaboration, and a sandboxed Claude Code–powered runtime. It feels like 'Slack meets Claude Code' with built-in IM integrations and one-click Docker self-hosting.

#openclaw-alternative#claude-code#sandboxed-agent#team-collaboration#self-hosted
Compare vs OpenClaw
GitHub ↗

Facts

Repository

Contributors9
Open issues2
Last commitSep 22, 2026
Release cadence~9 days
Latest release0.5.7

Runtime

LanguagePython
Memory90 MB
Boot time250 ms
Deploymentself-hosted · cloud · desktop
Setup difficultyMedium
Plugin ecosystemEmerging

Posture

LicenseMIT
Local-firstNo
Cloud dependencyOptional
Multi-userYes
Privacy postureMixed

Community

Sentiment45% positive
Reddit mentions20
Web results10

Security breakdown

Composite 78 / 100 · how these are scored

Sandboxing9 / 10

higher is safer

API security7 / 10

higher is safer

Network isolation7 / 10

higher is safer

Telemetry safety6 / 10

higher is safer

Shell access risk4 / 10

higher is riskier

Model access

Read from the repository, not written by a model · 77 files examined

5 providers · custom endpoint

Direct
AnthropicDeepSeekMiniMaxOpenAIZhipu
Compatible
OpenAI-compatible

Pinned models

claude-sonnet-4-20250514 released 2025-05-14 — 18 months old (dated in the model id)

Pin last edited 7 months ago

Evidence

Decision

Why choose Poco over OpenClaw?

Why choose this

  • Nicer web UI with artifacts and playback views
  • Built-in sandboxed container runtime by default
  • Native team collaboration via servers, channels, and threads

Tradeoffs

  • Smaller community and younger ecosystem
  • Heavier stack (Next.js + FastAPI + Docker) to operate
  • Tied to Claude Code runtime rather than a standalone agent core

Best fit

  • Teams wanting channel-based agent collaboration
  • Users who prefer a polished web UI over terminal-first tools
  • Self-hosters needing IM integration (DingTalk, Feishu, Telegram)

Avoid if

  • You want a minimal, lightweight single-user agent
  • You avoid Claude Code–dependent runtimes
  • You need a mature, battle-tested ecosystem
Good Confidence62%

README and commit evidence is strong and shows active development, but Reddit matches are unrelated noise and web sentiment is indirect, so community and sentiment scores carry real uncertainty.

AI layer reviewed Oct 5, 2026 · how this is written

Star activity

1,357 stars today

Overview

Poco positions itself as a safer, more beautiful, and easier-to-use OpenClaw alternative, built around a 'pocket coworker' concept. Architecturally it pairs a Next.js 16 frontend with a FastAPI (Python 3.12+) backend, and runs all agent tasks inside isolated containers, with optional local directory mounting for self-hosted deployments. Under the hood it leverages a Claude Code–based agent runtime, giving it native slash commands, Plan Mode, MCP and Skills extensibility, a built-in browser, and GitHub repo integration.

Where Poco differentiates most is collaboration: long-lived servers with channels, DMs, and reply threads let teams mention persistent agents, convert messages into trackable tasks, and publish outputs as shared files. It also ships embedded IM backends for DingTalk, Feishu, and Telegram, mobile support, background execution with scheduled triggers, and a polished UI featuring artifacts previews (HTML, PDF, Excalidraw, Drawio, etc.) and playback of command I/O and tool calls.

Compared to OpenClaw's local-first, chat-app-centric model, Poco is a heavier, server-oriented platform aimed at teams, offered both as one-click Docker self-hosting and a cloud subscription. Recent commits show active hardening — auth redirect fixes, visibility-aware service paths, signed workspace file streaming, and sandbox refinements — indicating a healthy but still maturing project at version 0.5.7.

Nominate a clone

Add a new Claw

Paste a GitHub repository and tell us why it belongs on the tracker.

Opens a prefilled issue on GitHub — every nomination is public. Comfortable with a PR? Adding the repo to projects.json is faster.