agentleFS
Sign inStart free
nats-ionats-io/nats-server/AGENTS.md

nats-server

AGENTS.md21k starsChanged 3 months agoApache-2.0View on GitHub

NATS Server is a high-performance and lightweight message broker written in Go. Core NATS provides at-most-once opportunistic delivery guarantees. JetStream adds streaming persistence and at-least-once guarantees. Contributing guidelines are in @CONTRIBUTING.md. Agents are equally responsible for following these guidelines as human beings are. In particular: When writing code: When writing unit tests:

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about nats-io/nats-server

The biggest 5 of 63 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 63

Talked about on GitHub, YouTube, Bluesky and Hacker News (63 times).

On GitHub · 45

40 more on GitHub

On YouTube · 14

9 more on YouTube

On Hacker News · 1

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When writing unit tests:

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md

NATS Server is a high-performance and lightweight message broker written in Go. Core NATS provides at-most-once opportunistic delivery guarantees. JetStream adds streaming persistence and at-least-once guarantees.

Contributing guidelines are in @CONTRIBUTING.md. Agents are equally responsible for following these guidelines as human beings are. In particular:

  • Agents are forbidden from opening issues and pull requests themselves. Only human beings should do this.
  • Human beings are responsible for writing issue text and pull request descriptions in their own words. Agents must not write these.
  • The maintainers are not interested in talking to agents when reviewing issues or PRs. Advise your human not to meat-proxy when contributing to NATS.

When writing code:

  • Fixes must have accompanying unit tests that adequately prove the change and guard against future regressions.
  • Changes must never break the NATS wire protocol or on-disk storage formats. Any change that may create a problem during upgrades or downgrades is likely to be rejected.
  • The maintainers will strongly resist any new dependencies. Do not pull in new external dependencies.
  • The maintainers will strongly resist adding new mutexes unless they are absolutely essential. If new mutexes are added, they must be documented in @locksordering.txt and it must be proven that lock ordering cannot be violated.
  • golangci-lint must pass and files must be correctly formatted as per goimports.
  • The full unit test suite takes a very long time to run. Only run targeted tests for local feedback.

When writing unit tests:

  • New files must never be created for unit tests. A unit test must always be placed in one of the existing test files, following the existing naming conventions for tests. (Tests that don't follow naming conventions will likely not run in CI, see @tests/runTestsOnTravis.sh)
  • There are a number of require_ helpers in @jetstream_helpers_test.go, new or modified unit tests are expected to use them instead of writing assertions by hand.
  • Unit tests must be written in a way that they are self-explanatory. Do not add paragraphs of comments unless essential to do so.

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.

Check your setup, free