agentleFS
xmtpxmtp/libxmtp/sdks/AGENTS.md

libxmtp / sdks

AGENTS.md127 starsChanged 11 days agoMITView on GitHub

Shared behavior belongs in Rust/core and crates/xmtp_sdk; platform packages wrap it. Never edit generated bindings. Keep native streams open through retryable faults; core owns ordered recovery and durable delivery progress. For JS/TS SDKs (node, browser, agent, react-native): - Use the root pnpm workspace. dev/nix-shell 'just install-js' installs it; dev/nix-shell 'just js sdk-products [node|browser|react-native]' stages products. - Use the task graph; never --parallel or --no-sort. Agent consumes Node's dist. Read package preparation when changing build routes. - Client creation requires explicit…

The file

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

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the root pnpm workspace.

    line 9
  2. Very specific:

    Use the task graph; never --parallel or --no-sort.

    line 11

≈ “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

XMTP SDKs

Shared behavior belongs in Rust/core and crates/xmtp_sdk; platform packages wrap it. Never edit generated bindings. Keep native streams open through retryable faults; core owns ordered recovery and durable delivery progress.

For JS/TS SDKs (node, browser, agent, react-native):

  • Use the root pnpm workspace. dev/nix-shell 'just install-js' installs it; dev/nix-shell 'just js sdk-products [node|browser|react-native]' stages products.
  • Use the task graph; never --parallel or --no-sort. Agent consumes Node's dist. Read package preparation when changing build routes.
  • Client creation requires explicit backend; Browser also requires storage. env labels database files, never selects a backend. Preserve the API cache key <backendUrl>|<appVersion>.
  • Tests need just backend up through Nix unless documented otherwise.
  • Iteration acknowledges the previous message on the next read; close/end do not acknowledge. Callback mode acknowledges only after callback success and cannot also iterate. Keep typed failures; never automatically replace failed readers. Read delivery rules for stream work.

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.