
ratmmmhsquishyrat/agent-coexist
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
A small CLI for AI agents to collaborate through local Markdown files. No server, no database.
Обзор
agent-coexist is a small command-line tool for projects that more than one AI agent works on. It keeps their threads, directory claims, reading lists, and profiles as plain Markdown files in the project, where any agent with file access can find them. Agents on the same project usually cannot see each other's context. Most harnesses do not talk to one another, main sessions rarely see each other, subagents rarely see their siblings, and a session that resumes or moves to another harness often has no record of what came before. agent-coexist does not monitor harness chat transcripts, sync across networks, or automatically capture session histories. Instead, agents explicitly write messages, directory claims, and reading routes to Markdown files (*.agent-coexist.md) in the workspace. Any agent with file access can inspect them with standard file tools or the CLI.
README
Показан фрагмент оригинального README. Открыть оригинал.
agent-coexist
Different harnesses, different sessions, sibling subagents — if they share a filesystem, they can work together.
agent-coexist is a small command-line tool that gives agents on one project a shared place to look: threads, directory claims, reading routes and profiles, kept as plain Markdown files next to the work.
Why
Agents on the same project usually cannot see each other’s context. The harness boundary is only the most obvious wall:
- Different harnesses do not talk to one another at all.
- Different sessions of the same harness start blank — including a session that resumes your own work tomorrow, or migrates to another tool.
- Sibling subagents under one harness cannot see each other, even while editing the same repository at the same moment.
- Main sessions running side by side are equally blind to each other.
None of those walls are the same problem, and none of them can be fixed from inside the harness. But they all have one thing in common: the agents share a filesystem. So put the record there.
Agents write messages, directory claims and reading routes to Markdown files
(*.agent-coexist.md) next to the work, and any agent that can open the
project finds them there — with this CLI, or with the file tools it already
has. No server, no database, no network, and nothing to keep running.
That the parties never need to meet is the point: an agent can answer a question left by a session that ended yesterday, in a harness it has never heard of.
What it looks like
Every line above is real output from agent-coexist 0.4.1. bob never met
alice: he could be in another harness, in a session that started tomorrow, or
a sibling subagent spawned a second ago. The answer comes from the files.
Install
Every route below leaves agent-coexist as a bare command on your PATH,
which is what the bundled skill and the built-in guide tell agents to run.
The cargo routes are removed with cargo uninstall agent-coexist; a binary
you placed by hand is removed by deleting it.
Cargo (Recommended)
Requires Rust 1.89 or newer:
Рекомендуемые инструменты
Попробуйте другой запрос или уберите фильтр.
Установка
npx skillfish add ratmmmhsquishyrat/agent-coexist