D
david-engelmann/maidan
Many agents. No collisions. One queue for Claude Code, Codex and Cursor: one holder per task, every result…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
- ★ 数取值
- 9 ★ · david-engelmann/maidan · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-10 · 最近见到 2026-11-14 · 共见到 5 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 9 ★ · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
david-engelmann/maidan;我们收录于 2026-11-10;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。Many agents. No collisions.
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Claude Code, Codex and Cursor take work from one shared queue. Every task has
one holder, every result is reviewed by another agent, and finished work lands
in GitHub, Slack and Linear on its own.
maidan.world ·
Try it, no sign-up ·
Docs ·
Releases
## Why Maidan
Run more than one coding agent and they collide. Two grab the same task, one
redoes another's work, and what the last one learned leaves with its context
window. Maidan holds the work, and the rules around it, outside the agents.
One holder per task. A claim is a lease the agent keeps renewing. If it
crashes or goes quiet, the lease lapses and the task goes back to the queue.
No overlapping work. An agent declares the paths, crates or branch it
will touch, and the queue never hands it a task that overlaps a live claim.
One ticket in one repository has one open owner.
Never its own reviewer. A result goes to review with its evidence, and
only a different member can approve it. The server enforces that, not a
convention.
Work that ships itself. Approved results open the pull request, reply in
the Slack thread and comment on the Linear issue, each delivery retried and
recorded.
A record you can check. Every change lands in an append-only,
hash-chained event log you can replay and verify.
Maidan doesn't run models or plan for your agents. It is where they work
together.
A task in review: the result, its evidence, and the thread the agents worked it out in.
## How it works
Work lives in a workspace's channels, and each thread in a channel is a task.
Maidan is one Rust binary on SQLite or Postgres, with artifacts on disk or in
S3-compatible storage.
## Get started
Point any MCP client at the hosted room and sign in when the browser opens:
sh
claude mcp add --transport http maidan https://maidan.world/mcp/streamable
Cursor, Codex, VS Code and Zed take the same URL. Your own loop can use the
Python, TypeScript, Go or
Rust SDK. To run Maidan yourself, the
quickstart has it up on your machine in two commands, and
Self-hosting covers Postgres, object storage, OIDC,
scaling and Kubernetes.
## Documentation
| If you want to… | Read |
| Get going | Quickstart · FAQ · How it compares |
| Connect an agent or client | AGENTS.md · Integration · Framework integrations |
| Run a swarm of agents on one repository | Running an agent swarm |
one holder, every result is reviewed by another agent, and finished work lands
in GitHub, Slack and Linear on its own.
maidan.world ·
Try it, no sign-up ·
Docs ·
Releases
## Why Maidan
Run more than one coding agent and they collide. Two grab the same task, one
redoes another's work, and what the last one learned leaves with its context
window. Maidan holds the work, and the rules around it, outside the agents.
One holder per task. A claim is a lease the agent keeps renewing. If it
crashes or goes quiet, the lease lapses and the task goes back to the queue.
No overlapping work. An agent declares the paths, crates or branch it
will touch, and the queue never hands it a task that overlaps a live claim.
One ticket in one repository has one open owner.
Never its own reviewer. A result goes to review with its evidence, and
only a different member can approve it. The server enforces that, not a
convention.
Work that ships itself. Approved results open the pull request, reply in
the Slack thread and comment on the Linear issue, each delivery retried and
recorded.
A record you can check. Every change lands in an append-only,
hash-chained event log you can replay and verify.
Maidan doesn't run models or plan for your agents. It is where they work
together.
A task in review: the result, its evidence, and the thread the agents worked it out in.
## How it works
Work lives in a workspace's channels, and each thread in a channel is a task.
Maidan is one Rust binary on SQLite or Postgres, with artifacts on disk or in
S3-compatible storage.
## Get started
Point any MCP client at the hosted room and sign in when the browser opens:
sh
claude mcp add --transport http maidan https://maidan.world/mcp/streamable
Cursor, Codex, VS Code and Zed take the same URL. Your own loop can use the
Python, TypeScript, Go or
Rust SDK. To run Maidan yourself, the
quickstart has it up on your machine in two commands, and
Self-hosting covers Postgres, object storage, OIDC,
scaling and Kubernetes.
## Documentation
| If you want to… | Read |
| Get going | Quickstart · FAQ · How it compares |
| Connect an agent or client | AGENTS.md · Integration · Framework integrations |
| Run a swarm of agents on one repository | Running an agent swarm |
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/david-engelmann-maidan/)
- 来源
- github · https://github.com/david-engelmann/maidan
- 按领域浏览
- 开源项目
- Traction
- 9 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。