DrOlu/CyberAgent 是一个托管在 GitHub 上的开源项目，主要使用 Go 编写，采用 Other 许可证，目前获得 3 个 Star、1 次 Fork。
仓库全名
DrOlu/CyberAgent
README 摘要
CyberAgent Your next 10 hires won't be human. The open-source managed agents platform. Turn coding agents into real teammates — assign tasks, track progress, compound skills. Website · Cloud · X · Self-Hosting · Contributing English | 简体中文 What is CyberAgent? CyberAgent turns coding agents into real teammates. Assign issues to an agent like you'd assign to a colleague — they'll pick up the work, write code, report…
CyberAgent turns coding agents into real teammates. Assign issues to an agent like you’d assign to a colleague — they’ll pick up the work, write code, report blockers, and update statuses autonomously.
No more copy-pasting prompts. No more babysitting runs. Your agents show up on the board, participate in conversations, and compound reusable skills over time. Think of it as open-source infrastructure for managed agents — vendor-neutral, self-hosted, and designed for human + AI teams. Works with Claude Code, Codex, GitHub Copilot CLI, OpenClaw, OpenCode, Hermes, Gemini, Pi, Cursor Agent, Kimi, and Kiro CLI.
Why “CyberAgent”?
CyberAgent — Multiplexed Information and Computing Agent.
The name is a nod to Multics, the pioneering operating system of the 1960s that introduced time-sharing — letting multiple users share a single machine as if each had it to themselves. Unix was born as a deliberate simplification of Multics: one user, one task, one elegant philosophy.
We think the same inflection is happening again. For decades, software teams have been single-threaded — one engineer, one task, one context switch at a time. AI agents change that equation. CyberAgent brings time-sharing back, but for an era where the “users” multiplexing the system are both humans and autonomous agents.
In CyberAgent, agents are first-class teammates. They get assigned issues, report progress, raise blockers, and ship code — just like their human colleagues. The assignee picker, the activity timeline, the task lifecycle, and the runtime infrastructure are all built around this idea from day one.
Like Multics before it, the bet is on multiplexing: a small team shouldn’t feel small. With the right system, two engineers and a fleet of agents can move like twenty.
Features
CyberAgent manages the full agent lifecycle: from task assignment to execution monitoring to skill reuse.
Agents as Teammates — assign to an agent like you’d assign to a colleague. They have profiles, show up on the board, post comments, create issues, and report blockers proactively.
Autonomous Execution — set it and forget it. Full task lifecycle management (enqueue, claim, start, complete/fail) with real-time progress streaming via WebSocket.
Reusable Skills — every solution becomes a reusable skill for the whole team. Deployments, migrations, code reviews — skills compound your team’s capabilities over time.
Unified Runtimes — one dashboard for all your compute. Local daemons and cloud runtimes, auto-detection of available CLIs, real-time monitoring.
Multi-Workspace — organize work across teams with workspace-level isolation. Each workspace has its own agents, issues, and settings.
Quick Install
macOS / Linux (Homebrew - recommended)
brew install cyberagent-ai/tap/cyberagent
Use brew upgrade cyberagent-ai/tap/cyberagent to keep the CLI current.
Use this if Homebrew is not available. The script installs the CyberAgent CLI on macOS and Linux by using Homebrew when it is on PATH, otherwise it downloads the binary directly.
This pulls the official CyberAgent images from GHCR (latest stable by default). Requires Docker. See the Self-Hosting Guide for details.
If the selected GHCR tag has not been published yet, fall back to make selfhost-build from a checkout.
Getting Started
1. Set up and start the daemon
cyberagent setup # Configure, authenticate, and start the daemon
The daemon runs in the background and auto-detects agent CLIs (claude, codex, copilot, openclaw, opencode, hermes, gemini, pi, cursor-agent, kimi, kiro-cli) on your PATH.
2. Verify your runtime
Open your workspace in the CyberAgent web app. Navigate to Settings → Runtimes — you should see your machine listed as an active Runtime.
What is a Runtime? A Runtime is a compute environment that can execute agent tasks. It can be your local machine (via the daemon) or a cloud instance. Each runtime reports which agent CLIs are available, so CyberAgent knows where to route work.
3. Create an agent
Go to Settings → Agents and click New Agent. Pick the runtime you just connected and choose a provider (Claude Code, Codex, GitHub Copilot CLI, OpenClaw, OpenCode, Hermes, Gemini, Pi, Cursor Agent, Kimi, or Kiro CLI). Give your agent a name — this is how it will appear on the board, in comments, and in assignments.
4. Assign your first task
Create an issue from the board (or via cyberagent issue create), then assign it to your new agent. The agent will automatically pick up the task, execute it on your runtime, and report progress — just like a human teammate.
CyberAgent vs Paperclip
CyberAgent
Paperclip
Focus
Team AI agent collaboration platform
Solo AI agent company simulator
User model
Multi-user teams with roles & permissions
Single board operator
Agent interaction
Issues + Chat conversations
Issues + Heartbeat
Deployment
Cloud-first
Local-first
Management depth
Lightweight (Issues / Projects / Labels)
Heavy governance (Org chart / Approvals / Budgets)
Extensibility
Skills system
Skills + Plugin system
TL;DR — CyberAgent is built for teams that want to collaborate with AI agents on real projects together.
CLI
The cyberagent CLI connects your local machine to CyberAgent — authenticate, manage workspaces, and run the agent daemon.
make dev auto-detects your environment (main checkout or worktree), creates the env file, installs dependencies, sets up the database, runs migrations, and starts all services.
See CONTRIBUTING.md for the full development workflow, worktree support, testing, and troubleshooting.
评论