agora
Espacio compartido y persistente por repositorio para sesiones de Claude Code: cada sesión registra su actividad vía hooks, ves qué hicieron/hacen las demás, te avisa si vas a pisar trabajo ajeno, y podés dejar notas. Sin daemon.
README
<div align="center">
<img src="./assets/banner.jpg" alt="agora — a shared space for your Claude Code sessions" width="100%" />
agora
A shared, persistent space for your Claude Code sessions — per repository.
See what other sessions are doing, get warned before you overwrite their work, and leave notes. No daemon, no server to run.
</div>
Why
When several Claude Code sessions work on the same repository — in parallel, or just over the course of a day — they're blind to each other. None of them knows what the others touched, they overwrite the same files silently, and the context is lost when you close them.
agora gives every session a shared place to leave a trail and look at each other's work.
How it works
The whole system is one SQLite file per repo: <repo-root>/.agora/space.db (in WAL mode, so multiple processes read and write it at once without corruption).
- No one runs a server. There's no daemon, no web app. The "space" is the file.
- Every session of the repo writes what it does and reads what the others did.
- Because it's a file, it persists by itself — close everything, come back tomorrow, the state is still there.
- It's a shared board, not a live chat: sessions find out when they start, when they're about to edit (collision), or when they ask (the tools).
Multi-worktree friendly: the
.dblives at the main repo root, so every session of the repo — including those in different worktrees — shares one agora.
Features
- 🟢 See who's here and what files each session is touching, live.
- ⚠️ Collision warnings — before you edit a file (or work a branch) another active session already holds.
- 📋 Project resume — open a session and get a summary of what the others did.
- 📓 Activity log — a per-repo timeline of everything that happened.
- ✉️ Notes between sessions (directed or broadcast).
- 🛡️ Best-effort hooks — they exit
0no matter what; they never block your session.
Requirements
- Bun 1.3+
git2.x- Claude Code (or any MCP client)
Installation
git clone https://github.com/vorluno/agora-mcp.git
cd agora-mcp
bun install
# Install the 5 hooks (idempotent). Add --project to scope to the current repo only.
bun run src/cli.ts init
# Register the MCP server
claude mcp add agora -- bun run /absolute/path/to/agora-mcp/src/index.ts
Configuration
Any MCP client works. The mcpServers entry:
{
"mcpServers": {
"agora": {
"command": "bun",
"args": ["run", "/absolute/path/to/agora-mcp/src/index.ts"]
}
}
}
For Claude Code, claude mcp add (above) writes this for you. For Warp or Cursor, paste the snippet into their MCP settings.
Tools
| Tool | Description |
|---|---|
resume_project |
Summary of the agora: active sessions, recent activity, collisions, unread notes. |
who_is_here |
Active sessions and which files each one is touching. |
activity_log |
The repo's event log, filterable by time/session. |
check_collision |
Is another active session touching these files or this branch? |
leave_note |
Leave a note for another session (or broadcast to all). |
read_notes |
Read notes addressed to a session (marks them read). |
How collisions are detected
- File collision: 2+ distinct sessions with an active
writingclaim on the same file. - Branch collision: 2+ active sessions on the same branch but in different worktrees.
Only live sessions are counted, so a session that died without a clean exit won't produce false positives.
Automatic capture (hooks)
init installs 5 best-effort hooks (they always exit 0):
| Hook | What it does |
|---|---|
SessionStart |
Registers the session and injects the agora summary into your context (also fires on /resume and after a context compaction). |
PostToolUse (Edit/Write) |
Records the file claim + event; warns if a new collision appears. |
PreToolUse (Edit/Write) |
Warns you before editing if another session already holds the file. |
Stop / SessionEnd |
Marks the session idle / stopped and releases its claims. |
Development
bun test # full suite (incl. a real WAL concurrency test)
bunx tsc --noEmit # type-check
Built test-first across 14 TDD tasks with per-task and whole-branch review.
License
MIT © 2026 Vorluno
<div align="center">
Built by Vorluno — a software studio from Panamá 🇵🇦
Part of the mcp-s family of MCP servers.
</div>
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。