Cybara

When cloud-hosted agent platforms are off the table — for compliance, cost, or data sovereignty — the usual fallback is stitching a runtime together from libraries. Cybara is a self-hosted, open-source alternative that ships the full stack: multi-agent coordination, a built-in tool library covering code, browser, desktop, file, and API execution, 25+ messaging channel integrations, and on-chain wallet operations, all running on hardware you control. The core workflow is agent-plus-tools: you configure a model provider from the supported catalog, attach tools from the built-in library or install MCP servers from the official registry, set allowlist and spend policies, and agents execute against real environments while you watch approvals queue in the chat panel.

The feature that separates Cybara from a typical agent scaffold is the operator control layer. Tool allowlists, filesystem checkpoint and rollback, transform hooks, and per-channel access policy are first-class — not bolted on. The router is spend-aware: it tracks coding-plan windows from your subscriptions, rotates across multi-key credential pools when rate limits approach, and trips circuit breakers before you hit hard caps. Embeddings for the semantic workspace index run locally via Transformers.js, so the IDE and memory features stay air-gapped if your environment requires it.

Cybara fits teams running agents at the infrastructure level — a developer integrating agent execution into an editor over ACP, an operator automating multi-channel messaging across Telegram and Discord with per-channel policy, or a team running on-chain tasks that cannot touch a third-party runtime. Where it breaks down is for teams that want a managed experience: there is no hosted version, no vendor-run infrastructure, and the breadth of configuration surface means a solo developer building a single narrow prototype will spend more time on setup than the use case warrants. Teams that hit that ceiling typically move to a managed platform and trade control for faster initial deployment.

Editor integration runs over the Agent Client Protocol — executing `cybara acp` connects Zed or any ACP client to the local runtime. MCP works in both directions: Cybara consumes MCP servers as agent tools and exposes its own tools to Claude Desktop and other MCP clients. The skill registry (ClawHub, Skills.sh, GitHub) lets agents install and author reusable SKILL.md procedures that persist across sessions, compounding capability over time without re-prompting.