agentleFS
rebornixrebornix/Agmente/ACPClient/AGENTS.md

Agmente / ACPClient

AGENTS.md545 starsChanged 9 months agoMITView on GitHub

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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:

    Read .agmente.paths (from repo root) before cross-checking ACP upstream docs/spec.

    line 7
  2. Distinctive:

    When adding ACP method support:

    line 16
  3. Distinctive:

    Add the method constant and typed payload mapping.

    line 17
  4. Distinctive:

    Add response/event parsing coverage.

    line 19
  5. Distinctive:

    Ensure delegate and pending-request behavior remain correct.

    line 20
  6. Distinctive:

    Add package tests for success and failure paths.

    line 21
  7. Distinctive:

    Keep slash-escaping compatibility option functional.

    line 25
  8. Distinctive:

    Keep request ID/pending continuation behavior deterministic.

    line 26
  9. Distinctive:

    Keep reconnection/disconnect semantics from breaking in-flight request handling.

    line 27
  10. Very specific:

    Run package tests for ACPClient.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

ACPClient Package Guide

Scope

Typed ACP transport/service package used by the iOS app.

External Repo Paths

  • Read .agmente.paths (from repo root) before cross-checking ACP upstream docs/spec.
  • ACP upstream reference root: AGMENTE_ACP_REPO/docs.

Architecture Model

  • Transport concerns, request orchestration, and ACP parsing are separated layers.
  • Public service APIs should remain typed and hide wire-format details from callers.
  • Parsing helpers should be resilient to optional/partial ACP payloads.

Extension Pattern

When adding ACP method support:

  1. Add the method constant and typed payload mapping.
  2. Expose a typed service wrapper.
  3. Add response/event parsing coverage.
  4. Ensure delegate and pending-request behavior remain correct.
  5. Add package tests for success and failure paths.

Compatibility Rules

  • Preserve support for server-initiated JSON-RPC requests (do not treat as transport errors).
  • Keep slash-escaping compatibility option functional.
  • Keep request ID/pending continuation behavior deterministic.
  • Keep reconnection/disconnect semantics from breaking in-flight request handling.

Tests

  • Run package tests for ACPClient.

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.