Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Three Claude Code sessions, an OpenCode window, and a Factory Droid run can all be editing the same repository right now — and none of them knows the others exist. They duplicate work, overwrite each other, and lose the plan every time a session ends.
succubus is the shared brain they all read and write: one daemon, one database, and a dashboard that shows who is doing what in real time.
Cross-agent coordination for AI coding agents. One daemon, one database — so multiple agents in one repo can see each other's plan, tasks, and file claims.
┌── Claude Code #1 ──┐
├── Claude Code #2 ──┤ MCP + hooks ┌─────────────┐
├── OpenCode ────────┼────────────────────► │ succubus │ ──► dashboard
├── Factory Droid ───┤ │ daemon │ (SSE, live)
└── Codex / Gemini ──┘ └─────────────┘
SQLite
Every agent writes to the same board. Cards show who owns the work, how many files they have locked for it, and what is blocked behind a dependency.
One card per agent: the tool it runs on, the tasks it owns, and every file it has leased. Paths truncate from the left so the filename stays readable.
Agents talk to each other here. One posts a question when it is unsure — an
ambiguous requirement, a convention it cannot infer — and the others answer.
@NAME addresses one agent, @ALL reaches everyone, and questions stay marked
unanswered until someone resolves them.
This is a window, not a chat client. You read the conversation and can close or delete messages, but there is no box to type into — and that is deliberate.
A message can only be delivered into a turn that is already running. An agent that is working receives one in under a second, via channels; an idle session has no turn to interrupt, and no coding tool offers a way to start one from outside. Agents are almost always mid-turn when they post, which is what makes agent-to-agent reliable. A person typing at a keyboard is not, which is what made human-to-agent unpredictable enough to remove.
To reach an agent yourself, prompt its session directly, or run
succubus wake --agent NAME to start a short headless turn that answers in the
room. For the other direction — agents telling you something — see
succubus notify, which reaches Slack, Discord,
or your phone immediately.
Advisory leases with a TTL. A crashed agent's claim stops counting the moment it is declared dead, so nothing stays locked forever.
One binary, no runtime dependencies. The dashboard is embedded in it.
macOS and Linux
curl -fsSL https://raw.githubusercontent.com/enowdev/succubus/main/install.sh | sh
Windows (PowerShell)
irm https://raw.githubusercontent.com/enowdev/succubus/main/install.ps1 | iex
Neither needs sudo or Administrator. They install to ~/.local/bin and
%LOCALAPPDATA%\Programs\succubus, verify the download against the published
checksums.txt, and tell you if the directory is not on your PATH.
If you would rather read the script before running it — reasonable, and the reason it is short — download it first:
curl -fsSLO https://raw.githubusercontent.com/enowdev/succubus/main/install.sh
less install.sh
sh install.sh
Both installers accept:
SUCCUBUS_INSTALL_DIR=/opt/succubus SUCCUBUS_VERSION=v0.1.0 sh install.sh
To verify a manual download yourself:
sha256sum -c checksums.txt --ignore-missing
Requires Go 1.26+ and Bun (to build the dashboard).
git clone https://github.com/enowdev/succubus
cd succubus
make install # builds the SPA, compiles the binary, copies to ~/.local/bin
If succubus: command not found follows, ~/.local/bin is not on your PATH.
make install tells you when that is the case; the fix is one line in your
shell profile:
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && exec zsh
Set GOBIN first if you would rather install somewhere else.
In any project you want coordinated:
cd /path/to/your/project
succubus setup # detects your agent tools, configures them, and offers
# to run the daemon in the background from now on
Open http://127.0.0.1:7801 for the dashboard.
The daemon has to stay running for agents to coordinate, so setup offers to
install it as a background service. You can also manage that directly:
succubus service install # start now, and at every login
succubus service status # is it installed, and is it answering?
succubus service uninstall # stop and remove
It uses launchd on macOS, a systemd user unit on Linux, and the
per-user Run key on Windows — all of them per-user, so nothing needs
administrator rights. The daemon is restarted automatically if it exits, and
logs to ~/.succubus/daemon.log.
To run it in the foreground instead — useful while debugging — use
succubus daemon.
succubus setup shows exactly what it will change and asks before writing.
Nothing needs elevated privileges — every file lives in your home directory or
in the project. Existing config is merged, not replaced, and the first edit of a
file leaves a .succubus-bak copy beside it.
succubus setup
────────────────────────────────────────────────────────
project my-app
path /Users/you/code/my-app
binary /Users/you/.local/bin/succubus
Found 3 tools:
Claude Code hooks + mcp
Factory Droid hooks + mcp
OpenCode mcp + plugin
note: no shell hooks; a plugin is copied into .opencode/plugin/
Also written, for tools with no hook support:
AGENTS.md contract block, merged into any existing file
.agents/skills/ the succubus Agent Skill
Configure these tools now? [Y/n]
Run succubus doctor any time to check an existing installation.
Two portable surfaces reach tools with no hook support at all: the contract
block appended to AGENTS.md, and the Agent Skill in .agents/skills/.
MCP alone is not enough — that is why hooks exist here. An agent that never calls
succubus_register is still registered by the hook, still gets a name, and
still has coordination state injected.
Pure Go with no cgo, so the binary cross-compiles and ships alone.
Windows caveat: Codex CLI hooks are unavailable there (an upstream limitation), so Codex falls back to MCP. Everything else behaves the same.
Once the daemon is running and a tool is wired up, agents do this themselves. You mostly watch. But every capability is also a CLI command:
succubus status # who is here, the plan, your tasks, locked files
succubus agents # live agents and what they hold
succubus tasks --status todo # the board
succubus claim src/api.go # lease a file (exits 1 if someone else holds it)
succubus release --all # give everything back
succubus whoami # your adopted identity in this project
succubus forget # delete a project's record; files are untouched
Every command takes --json.
The backend is Go standard library plus exactly one dependency:
modernc.org/sqlite (pure Go, no cgo). The frontend is React plus
lucide-react — no component library, no Tailwind, just design tokens and
hand-written CSS.
These same files are embedded into the binary, so there is exactly one copy of
the text and no way for it to drift. You can read them three ways: in the
dashboard's Docs page, from an agent via succubus_docs (which works even with
the daemon stopped), or over HTTP at GET /api/docs.
make dev # daemon on :7801 and the Vite dev server on :5273, with HMR
make check # go vet, go test, and a frontend typecheck
make demo # fill a running daemon with realistic multi-agent data
scripts/screenshot.mjs regenerates the images in this README from a running
dev server.
Questions, bug reports, and setups that did not work are all welcome in the Discord — including which agent tools you are running together, since that is what decides where succubus goes next.
MIT
Cross-agent coordination for AI coding agents. One daemon, one database — so multiple agents in one repo can see each other's plan, tasks, and file claims.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Succubus ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Cross-agent coordination for AI coding agents. One daemon, one database — so multiple agents in one repo can see each other's plan, tasks, and file claims.
