agentleFS
Cotal-AICotal-AI/Cotal/llms.txt

Cotal

llms.txt393 starsChanged 15 days agoApache-2.0View on GitHub

An open standard for AI agents to coordinate in real time as lateral peers in a shared pub/sub space, not as nodes in an orchestrator tree. The wire contract runs over NATS + JetStream; the reference implementation is TypeScript. Cotal's wire contract (subjects, message schemas, presence and discovery conventions) is the standard; libraries are thin clients over it. SPEC.md is normative; the docs/ are informative companions. Paths below are repo-relative; the hosted docs site serves its own task-routed index at…

The file

Files
llms.txt
# Cotal

> An open standard for AI agents to coordinate in real time as lateral peers in a shared
> pub/sub space, not as nodes in an orchestrator tree. The wire contract runs over NATS +
> JetStream; the reference implementation is TypeScript.

Cotal's wire contract (subjects, message schemas, presence and discovery conventions) is the
standard; libraries are thin clients over it. `SPEC.md` is normative; the `docs/` are
informative companions. Paths below are repo-relative; the hosted docs site serves its own
task-routed index at `https://docs.cotal.ai/llms.txt` with absolute URLs, and every docs page
there has a Markdown twin (append `.md` to its URL).

## Start here

- [README.md](README.md): what Cotal is, the three addressing modes, and a quick start.
- [docs/README.md](docs/README.md): the docs index, with task dispatch for agents.
- [docs/what-is-cotal.mdx](docs/what-is-cotal.mdx): what Cotal is and what it can do.
- [docs/getting-started.mdx](docs/getting-started.mdx): install and run a local mesh.
- [docs/architecture.mdx](docs/architecture.mdx): how it is built (subjects, streams, auth, the manager).
- [docs/connect-claude.mdx](docs/connect-claude.mdx): how a Claude Code session joins the mesh.

## Reference

- [SPEC.md](SPEC.md): the normative wire contract.
- [docs/cli.mdx](docs/cli.mdx): every `cotal` command.
- [docs/mcp-tools.mdx](docs/mcp-tools.mdx): the `cotal_*` tool catalog agents use in-session.
- [docs/manifest.mdx](docs/manifest.mdx): every field of the `cotal.yaml` mesh manifest.
- [docs/identity-and-auth.mdx](docs/identity-and-auth.mdx): who can do what, and how it is enforced (static and per-user auth).
- [docs/transport.mdx](docs/transport.mdx): protocol vs transport, and the capability contract.
- [docs/spaces.mdx](docs/spaces.mdx): spaces vs channels, and the federation direction.
- [docs/security.mdx](docs/security.mdx): the trust boundary and threat model.
- [docs/build-a-client.mdx](docs/build-a-client.mdx): implement a conformant client in another language.
- [docs/examples.mdx](docs/examples.mdx): index of runnable examples.

## For contributors

- [AGENTS.md](AGENTS.md): the guide for coding agents working in this repo.
- [docs/setup-internals.md](docs/setup-internals.md): how the `cotal setup` flow works.
- [docs/release.md](docs/release.md): how to version and publish.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.