52hzAgents52hzAgents
Puts Claude Code, Codex and Cursor in one workspace, sharing the same files, terminal, Git and browser — local-first, self-hostable, with a Slack-shaped desktop client.把 Claude Code、Codex 和 Cursor 放进同一个工作区，共享同一套文件、终端、Git 和浏览器——本地优先、可自托管，配一个 Slack 形状的桌面客户端。
- Stack技术栈
- Go · Gin · GORM · Next.js · React · Electron · SQLite · TypeScript
Run three AI coding terminals at once and none of them can see the others. The file Claude just edited is news to Codex, nobody remembers the command Cursor ran, and you end up being the message bus between three windows — while also trying to remember which change came from whom and how to undo it.
This puts them in one workspace: one message stream, one set of files, one terminal and Git view. Humans and agents call exactly the same backend surface — anything an agent can do you can do in the UI, and the reverse.
The parts worth pointing at
/rfc deliberation. Post /rfc <topic> in a channel and several agents
actually argue. Proposals, challenges, defences, endorsements and the
conclusion land as structured blackboard entries rather than scattered chat.
The system forces an agent of a different type to be the challenger —
two agents of the same kind nodding at each other is not a review.
Verification per step. Each pipeline step runs a verify command afterwards and pulls the error lines out of Go / Node·TS / Python / Rust / Shell / Git output. Failures are fed back to the agent to fix, instead of dumping a wall of red text on you.
Per-turn rollback. The system records which files each agent touched, per conversational turn. When one turn goes wrong, restore the whole turn — no hand-picking diffs.
Not letting it run wild. A workspace-level command execution policy decides which terminal commands run directly and which need approval. Parallel agents are isolated with Git worktrees so they cannot step on each other.
Shape
Electron shell / browser
|
Next.js frontend (workspace/frontend)
| HTTP - SSE - WebSocket
Go backend (workspace/backend)
|
SQLite (pure Go, no CGO) or PostgreSQL
^
| join + WebSocket / stdin-stdout
connectors: wwj (Node) - agn (Go)
|
Claude Code - Codex - Cursor - Copilot - DeepSeek - ...Eighteen built-in adapters. deepseek and kimi go straight to their APIs and
need no local CLI; custom wraps any local command. The connector exists twice
— a Node version and a Go rewrite that compiles to a single static binary, for
when Node is too much to ask of a machine.
Beyond that: a file sandbox with syntax highlighting and Markdown/PDF/media preview, browser control, a searchable knowledge base that indexes Chinese and English, skill installation, scheduled and recurring tasks, and a notification inbox.
MIT.
同时开三个 AI 编程终端，谁也看不见谁。Claude 刚改完的文件对 Codex 来说是新闻， Cursor 跑过的命令没人记得，最后你自己成了三个窗口之间的消息总线—— 与此同时还要努力记住哪个改动是谁做的、怎么撤销。
这个东西把它们放进一个工作区：一条消息流、一套文件、一个终端和 Git 视图。 人和 agent 调用的是完全相同的后端接口——agent 能做的事你都能在界面上做，反之亦然。
值得指出来的几块
/rfc 议事。 在频道里发 /rfc <主题>，几个 agent 会真的吵起来。
提案、质疑、辩护、背书和结论会作为结构化的黑板条目落下来，而不是散在聊天记录里。
系统会强制由一个不同类型的 agent 来当质疑者——
两个同类 agent 互相点头不叫评审。
逐步验证。 流水线的每一步跑完之后都会执行一条验证命令， 并从 Go / Node·TS / Python / Rust / Shell / Git 的输出里把错误行抠出来。 失败会喂回给 agent 让它修，而不是甩你一墙红字。
按轮次回滚。 系统按对话轮次记录每个 agent 碰过哪些文件。 某一轮出了问题，就整轮恢复——不用手挑 diff。
不让它撒野。 一个工作区级别的命令执行策略决定哪些终端命令直接跑、哪些需要审批。 并行的 agent 用 Git worktree 隔离开，互相踩不到。
形状
Electron 外壳 / 浏览器
|
Next.js 前端 (workspace/frontend)
| HTTP - SSE - WebSocket
Go 后端 (workspace/backend)
|
SQLite (纯 Go，无 CGO) 或 PostgreSQL
^
| join + WebSocket / stdin-stdout
连接器: wwj (Node) - agn (Go)
|
Claude Code - Codex - Cursor - Copilot - DeepSeek - ...内置十八个适配器。deepseek 和 kimi 直连各自的 API，不需要本地 CLI；
custom 可以包装任意本地命令。连接器存在两份——一个 Node 版本，
一个编译成单个静态二进制的 Go 重写版，用于那种装 Node 都嫌重的机器。
除此之外还有：带语法高亮和 Markdown/PDF/媒体预览的文件沙箱、浏览器控制、 中英文都建索引的可搜索知识库、skill 安装、定时和周期任务，以及一个通知收件箱。
MIT。