Cybara — Your agents. Your tools. Your runtime.

Your agents. Your tools. Your runtime. Cybara is a self-hosted, open-source AI agent platform: agents that code, automate browsers and desktops, message across Telegram, Discord, Slack, and more, and execute on-chain operations — with full operator control.

50+ model providers · 80+ built-in tools · 25+ messaging channels · 100% self-hosted

Features

Multi-agent orchestration. Fan a single turn out to several proposer agents and synthesize one answer with Mixture of Agents, or route by weighted, round-robin, lowest-cost, and priority strategies.
Real tool execution. A large built-in tool library for code, files, browser and API automation, media generation, and a tool-calling code sandbox — all with interactive approval.
Self-improving skills. Agents codify a verified multi-step procedure once, and the loader picks it up for every future session. Memory and skills compound over time.
Encrypted wallet control. On-chain execution across ETH, BTC, and SOL behind an encrypted local wallet with policy caps, allowlists, and private-address SSRF protection.
Broad provider catalog. Dynamic model discovery across major providers with multi-key credential pools, rate-limit rotation, spend caps, circuit breakers, and coding-plan awareness.
Operator in the loop. Per-session and persistent tool allowlists, filesystem checkpoint and rollback, transform hooks, and localhost auth policy keep control where it belongs.
Code-aware IDE. A built-in IDE with semantic workspace indexing — embeddings run locally via Transformers.js — plus LSP diagnostics, git blame, and project-wide search and replace.
Usage-aware routing. Coding-plan windows are detected automatically from your subscriptions. The router skips exhausted plans, downweights near-limit providers, and honors spend caps.
MCP in both directions. Install MCP servers as agent tools from the official registry, Smithery, or npm — or flip it around and expose Cybara's own tools to Claude Desktop and other agents over MCP.
Editor integration over ACP. Drive Cybara agents straight from your editor over the Agent Client Protocol. Run `cybara acp` and connect Zed or any ACP client to code with your own self-hosted runtime.
Live browser preview. A session-bound embedded browser the agent drives — open pages, click, scroll, extract data, and screenshot — while you watch it work live in the chat panel.
25+ messaging channels. Run agents on Telegram, Discord, Slack, WhatsApp, Signal, iMessage, Matrix, Teams, and 20+ more — each gated by pairing, allowlists, and per-channel access policy.
Persistent memory. Agents recall prior work, decisions, people, and preferences from a searchable memory store, with semantic recall that compounds across every session.
Skill registry & install. Browse and install reusable SKILL.md procedures from ClawHub, Skills.sh, and GitHub, or let agents author their own — self-improvement that grows your toolkit.
Voice, in and out. Talk to your agents hands-free with local Kokoro TTS, OS and cloud voices, speech-to-text transcription, and a realtime full-duplex conversation mode.
Computer use. Agents drive the desktop in the background — capture, click, type, scroll, and drag — without taking over your cursor, in a sandboxed flow you approve.
Scheduled automations. A built-in cron scheduler runs agents and tools on your timetable — recurring reports, monitors, and maintenance jobs that fire even while you're away.
Plugins & account connectors. One hub for skill bundles, MCP services, and encrypted account connectors — Google Workspace, Microsoft 365, Dropbox, and Notion — read-only by default with approval-gated writes.
Media generation. Generate images, video, music, and speech from chat through swappable media providers, with artifacts and a canvas to collect what agents produce.
Sandboxed execution. Shell and git run inside a configurable command sandbox — sandbox-exec on macOS, Podman or Docker on Linux — with network allow/deny and path-safety guards for secrets.

Model providers

Bring your own keys or coding plans. Cybara discovers models dynamically, pools multiple credentials per provider, rotates on rate limits, and enforces spend caps and circuit breakers — swap providers without touching a line of agent logic.

OpenAI
Anthropic
Google Gemini
xAI Grok
Meta Llama
Mistral
DeepSeek
Moonshot Kimi
MiniMax
Zhipu GLM
Groq
Ollama
OpenRouter
AWS Bedrock
Azure OpenAI
MCP

Messaging channels

Telegram
Discord
Slack
WhatsApp
Signal
iMessage
Matrix
Mattermost
Microsoft Teams
Feishu / Lark
DingTalk
WeCom
Zulip
LINE
Google Chat
IRC
ntfy
Twitch
Nextcloud
Synology
Zalo
Home Assistant
SMS
Email
Web
Webhook

Platforms

Web & Tauri. Dashboard, chat, IDE, terminal, tools, and settings in the browser or a signed desktop app.
Native macOS. A SwiftUI shell packaged as a .app bundle over the same Bun sidecar runtime.
Mobile companion. A dark Liquid Glass React Native app for iOS and Android that pairs to any gateway.
CLI, ACP & VS Code. A Bun-based CLI and terminal UI, an Agent Client Protocol server for editors like Zed, and a VS Code extension.

Frequently asked questions

What is Cybara?

Cybara is a self-hosted AI agent platform. It pairs a Bun-based agent runtime with a web UI, desktop and mobile apps, a CLI, a broad tool layer, messaging-channel adapters, MCP support, and encrypted wallet controls, so agents can code, automate browsers, run messaging workflows, and execute on-chain operations under operator control.

Is Cybara free and open source?

Yes. Cybara is free and open source under the MIT license, created by Carsen Klock, and runs entirely on infrastructure you control. Use it commercially, fork it, and self-host it with no required account, telemetry, or cloud service.

Which platforms does Cybara run on?

Cybara ships desktop apps for macOS, Windows, and Linux, a native SwiftUI macOS app, mobile apps for iOS and Android, and command-line binaries for macOS, Windows, and Linux — plus a VS Code extension and an ACP server for editors — all built from the same Bun runtime and published on GitHub Releases.

Which messaging channels are supported?

Cybara includes adapters for Telegram, Discord, Slack, WhatsApp, Signal, iMessage, Matrix, Mattermost, Microsoft Teams, Feishu/Lark, DingTalk, WeCom, Zulip, LINE, Google Chat, IRC, ntfy, Twitch, Nextcloud, Synology, Zalo, Home Assistant, SMS, Email, Web, and Webhook — each gated by pairing, allowlists, and per-channel access policy.

How do I migrate from another agent to Cybara?

Run cybara migrate --from openclaw or cybara migrate --from hermes. Cybara detects local installs, previews the import as a dry run, brings over skills and memory, resolves conflicts by skip, overwrite, or rename, and imports API keys only if you opt in.

Do the apps update automatically?

Yes. Desktop apps use a signed updater channel backed by GitHub Releases and install updates in place, and the CLI verifies a published SHA256 checksum on every cybara update.

How does Cybara keep operators in control?

Sensitive tool calls can require interactive approval with per-session or persistent allowlists, the filesystem supports checkpoint and rollback, wallet operations enforce policy caps and allowlists, and the gateway uses a localhost auth policy with rotatable API keys.

Which model providers can I use?

Cybara connects to 50+ providers — OpenAI, Anthropic, Google Gemini, xAI, Meta, DeepSeek, Qwen, Moonshot/Kimi, Z.ai/GLM, MiniMax, Groq, OpenRouter, Azure OpenAI, AWS Bedrock, Vertex AI, and local runtimes like Ollama, vLLM, LM Studio, and llama.cpp. You bring your own keys; Cybara pools multiple keys per provider, rotates on rate limits, routes by weight or cost, and enforces spend caps.

How does Cybara handle my API keys and data?

Everything stays on infrastructure you control. Model keys, wallet keys, memory, and conversations live locally, the wallet is encrypted at rest, and there's no required account, telemetry, or cloud relay. Keys are never printed to logs and never leave your machine unless a tool you approve sends them.

Can I drive Cybara from my code editor?

Yes. Run cybara acp to expose the agent over the Agent Client Protocol (ACP) and connect Zed or any ACP-compatible editor, so you can code with your own self-hosted runtime. The ACP server can be toggled on or off in settings.

What are skills and where do they come from?

Skills are reusable SKILL.md procedures agents follow for recurring work. Browse and install them from the ClawHub, Skills.sh, and GitHub registries, author your own, or let agents codify a verified procedure automatically — the loader picks it up in every future session.

Does Cybara support MCP servers?

In both directions. Install Model Context Protocol servers as agent tools from the official MCP registry, Smithery, or npm — or expose Cybara's own tools to Claude Desktop and other MCP clients.

Can agents use a real web browser?

Yes. Each session gets an embedded browser the agent drives — opening pages, clicking, scrolling, extracting data, and taking screenshots — and you watch it work live in the chat panel. It works cross-platform, including on Windows. Beyond the browser, a computer-use tool can drive the desktop in the background without taking over your cursor.

Can I talk to my agents with voice?

Yes. Cybara supports hands-free voice conversations with local Kokoro TTS, OS speech, or cloud voices, plus speech-to-text transcription — including a realtime full-duplex mode where you and the agent can speak naturally.

Can agents run on a schedule?

Yes. A built-in cron scheduler runs agents and tools on a timetable you set — recurring reports, monitors, and maintenance jobs — with results delivered to the UI or any connected messaging channel.

What does Cybara cost?

Cybara itself is free and MIT-licensed. You only pay for the model provider usage on your own accounts — Cybara adds no markup, subscription, or per-seat fee, and there's no hosted tier to buy.