The installer selects the correct release for the current platform and verifies its published SHA256 checksum. You can also run Cybara without installing it with bunx cybara.
Cybara in Action
What Cybara Is
Cybara is one operator-controlled runtime for:
persistent conversations with streaming activity, queueing, steering, stopping, forking, reverting, and multi-chat workspaces
repository work through the integrated IDE, LSP, terminal, file diffs, browser preview, desktop control, and iOS/Android simulators
hosted, OAuth, gateway, proxy, and local models with dynamic discovery, usage-aware account pools, plan monitoring, and configurable routing
replayable trajectories, golden runs, objective benchmarks, computer-use datasets, and training-data exports in the Lab
voice conversations, encrypted Nearby session transfer, and policy-controlled wallet operations across ETH, BTC, and SOL
If you need an agent platform that can plan, execute, verify, and report with strong operator control, Cybara is built for that.
Capability Snapshot
Persistent agent workspace: streamed and persisted messages, grouped live activity, plans, artifacts, file diffs, queue/steer/stop controls, forks, reverts, and multi-chat panes
Provider choice and routing: dynamic model discovery, named usage-aware account pools, coding-plan monitoring, fallback policies, spend controls, and mixture-of-agents synthesis
Coding and automation: workspace instructions, IDE, LSP, Git, terminal, browser preview, computer use, and iOS/Android simulator control
Memory and orchestration: context compaction, workspace indexing, durable memory, scheduled tasks, subagents, agent transfers, and dependency-aware work boards
Research and reliability: replayable trajectories, golden regression runs, objective benchmark suites, training-data exports, and computer-use datasets in the Lab
Everywhere access: Web/Tauri, native SwiftUI macOS, React Native mobile, CLI/TUI, ACP, external channels, Nearby LAN transfer, and voice conversations over one gateway contract
Build From Source
Source development uses Bun only for dependency installation, tasks, and tests.
# Clone
git clone https://github.com/metaspartan/cybara.git
cd cybara
# Install dependencies
bun install
# Start full dev stack (backend + built UI + watch)
bun run dev
Then open:
UI: http://localhost:4269
API health: http://localhost:4269/api/health
Update an installed CLI with:
cybara update # verify SHA256, then download + install
cybara update --check # just report whether a newer release exists (non-zero if stale)
cybara update --force # reinstall even when already current
The Tauri desktop app checks the same GitHub release channel from Settings -> Desktop Updates and can install signed app updates in place. The native SwiftUI macOS app provides its own checksum-verified updater from App -> Check for Updates....
Cybara ships two desktop shells over the same Bun sidecar/runtime contract:
Tauri desktop for macOS, Windows, and Linux, including signed updater artifacts through GitHub Releases
Native SwiftUI macOS shell in apps/macos/Cybara, packaged as a .app bundle with the compiled sidecar, web UI, secp256k1.wasm, and local indexing runtime assets
bun run tauri:dev # Tauri desktop dev mode
bun run tauri:build # Tauri production build
bun run tauri:build:release # Tauri build with updater config/signatures
bun run native:macos:run # Build UI + sidecar, then run the SwiftUI shell
bun run native:macos:package # Build native SwiftUI .app + zip
Cybara Mobile is a system-aware Liquid Glass-inspired React Native app for iOS and Android, with light and dark appearance overrides. It connects to a Cybara gateway already running from CLI, Tauri/Web UI, native macOS, or a hosted deployment, then manages remote sessions and operator settings.
bun run mobile:dev
bun run mobile:ios
bun run mobile:android
bun run mobile:expo-check
# on the device running Cybara
cybara mobile connect --url http://192.168.1.20:4269 --device "Carsen iPhone"
The CLI and Web UI/Tauri Mobile page create QR pairings with revocable per-device tokens, so a phone can be revoked without rotating the root gateway API key. Pairing can use LAN access or a configured remote access URL from Settings → Gateway, including private mesh networks such as Tailscale/ZeroTier/NetBird or password-protected HTTPS tunnels. The mobile surface covers gateway health, sessions, agents, providers, provider plan limits, metrics, speech settings, tool approvals, wallet policy, channels, tasks, memory, terminal/log entrypoints, gateway controls, and settings summaries. See apps/mobile/README.md.
Release CI exports Expo bundles for iOS and Android and can also build signed Android AAB/APK and iOS IPA/TestFlight artifacts when the relevant store signing secrets are configured.
Session-aware execution with persistence and recovery
Agent tool allowlist and permission enforcement support
Tooling Layer
Tool categories currently shipped:
file: read/write/edit/search/grep/workspace_index/apply_patch — with a hard path-safety deny-list (credentials, SSH keys, .env) enforced before every write
media: image/tts + image_generate / video_generate / music_generate via a swappable provider registry (OpenAI, fal.ai, and MuAPI with FAL_KEY/FAL_API_KEY or MUAPI_API_KEY)
skill: calc/convert/pdf/ocr/summarization/video_frames/weather/mactop + skill_save (agents codify a successful procedure as a reusable skill for future sessions)
channel: message/telegram_media
planning: todo (session task-list with status discipline) + clarify (structured multi-choice questions to the user)
media: computer_use (bundled background desktop control for capture/click/type/scroll/drag without stealing the cursor)
orchestration: the kanban multi-agent tier — show/list/complete/block/heartbeat/comment/create/unblock/link for durable task graphs — plus mixture_of_agents (fan out to N proposer agents, synthesize one answer)
Named roles map to capability scopes: full / standard / readonly
Per-device scopes gate what a paired device may do: chat, manage, read, wallet, terminal — so a phone can be granted chat access without wallet or terminal
Device tokens are stored hashed (SHA-256) and compared in constant time; any device can be revoked without rotating the root gateway API key
Tauri desktop app with sidecar server wiring, bundled runtime resources, and in-app signed update checks via GitHub Releases
Native SwiftUI macOS app in apps/macos/Cybara that reuses the same local Cybara sidecar contract and can be packaged into a signed/notarized .app bundle
Provider Layer
Cybara supports popular providers including OpenAI, Anthropic, Google Gemini, xAI Grok, Z.AI, MiniMax, Kimi, Qwen, DeepSeek, and OpenRouter, plus local runtimes such as Ollama and vLLM. Model lists are discovered dynamically when supported.
Provider plan monitoring tracks local usage against manual limits or provider-specific coding-plan presets. The router can enforce rolling 5-hour, rolling-week, and monthly windows for flat coding plans, while pay-as-you-go routes can use token pricing and monthly budgets for spend-aware routing.
Named provider account pools group multiple configured accounts for usage-balanced routing or an explicit priority override. Agents and model-router routes can target a pool directly, while per-account environment key rotation (ANTHROPIC_API_KEY, _2, _3, …) remains available for API-key failover. Anthropic prompt caching is applied automatically to stable prompt content and recent turns, with provider-reported cache reads and writes included in usage metrics.
Popular Pre-configured Servers: Filesystem, GitHub, GitLab, PostgreSQL, SQLite, Puppeteer, Brave Search, Google Maps, Slack, Fetch, Obsidian, Raycast, and more
Tool Exposure: MCP server tools are automatically exposed to agents with full JSON-RPC communication
Settings → Plugins brings installed skill bundles, a searchable built-in catalog, MCP services, and account apps into one extension surface. Installed plugins can be enabled or disabled without restarting the gateway. Google Workspace, Microsoft 365, Dropbox, and Notion account apps default to read-only access; optional writes remain subject to Cybara's normal tool approval policy. Credentials and OAuth tokens use the encrypted secret store.
Plugins can be discovered from bundled, local, and workspace directories. Additional services can be connected through HTTPS or trusted local MCP servers.
bun run dev # Full dev flow
bun run build # Build backend
bun run build:all # Build UI + backend + CLI + main
bun run start # Run built backend
bun run start:prod # Build all then run
bun run package # Build local release/cybara + release UI assets
bun test # Full test suite
bun run test:smoke # Runtime + API + E2E smoke
bun run test:smoke:full # Broader live E2E smoke suite
RUN_BROWSER_E2E=1 bun test tests/e2e/ide-web-ui-browser-smoke.test.ts # Real browser IDE smoke
bun run check # Typecheck + lint + format check
bun run check:loc # Enforce max TS/TSX file size
bun run check:ci # CI gate (typecheck + lint + loc + Expo mobile check + smoke + deadcode report)
bun run tauri:dev # Desktop dev mode
bun run tauri:sidecar # Build the platform sidecar and bundled sidecar runtime assets
bun run tauri:build # Desktop production build
bun run tauri:prepare-release # Generate signed updater config from env
bun run tauri:build:release # Build desktop app with updater artifacts
bun run native:macos:build # Build the SwiftUI macOS app shell from source
bun run native:macos:run # Build UI + sidecar, then run the SwiftUI shell
bun run native:macos:package # Package the native SwiftUI macOS app bundle
bun run mobile:typecheck # Type-check React Native companion
bun run test:mobile # Mobile helper tests
API Highlights
Cybara exposes a broad REST API and streaming interfaces.
The terminal chat supports the same session-oriented workflow as the app clients: searchable
history, queued follow-ups while a run is active, steering, pending-message edit/delete/reorder,
agent switching, workspace switching, markdown emphasis, grouped tool/activity output, numbered
response copying, and portable conversation export.
Cybara builds each model request from the effective runtime state rather than one static prompt:
the selected agent, provider/model, workspace, channel, sandbox, and approval mode
only tools that survive the selected tool profile, enabled toolsets, explicit allowlists, inherited policy, permission checks, and runtime availability
eligible skill descriptions with on-demand SKILL.md loading
bounded memory recall and workspace instruction files
session plans, subagent context, token budgets, and context-compaction state
Tool policy and sandbox enforcement remain authoritative even if prompt text or untrusted content
claims otherwise. See Agent Runtime and Prompt Architecture for the
implemented contract.
Trading fees support the continued development of the Cybara project.
Meme tokens are highly volatile and speculative. Verify the contract address, trade responsibly,
and never risk more than you can afford to lose. $CYB does not represent equity, ownership, or a
claim on Cybara software or revenue.
Contributing
Create contribution branches from dev and open pull requests against dev.
The main branch is reserved for releases. See
CONTRIBUTING.md for setup, validation, and review requirements.
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Questions
Comment installer Cybara ?
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Cybara nécessite-t-il une clé API ?
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Quel transport Cybara utilise-t-il ?
Cybara s'exécute en local via stdio.
Quand Cybara a-t-il été vérifié pour la dernière fois ?
Dernière vérification : 2026-11-10. Self-hosted, open-source AI agent platform — CLI