Agmente / ACPClient
AGENTS.md545 starsChanged 9 months agoMITView on GitHub
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 32,671 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.
In this repository13 other files it gives its agents.
- Agents.mdAGENTS.md
- Agmente/AGENTS.mdAGENTS.md
- AgmenteTests/AGENTS.mdAGENTS.md
- AgmenteUITests/AGENTS.mdAGENTS.md
- AppServerClient/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- acp-local-runnerSkill
- codex-local-cli-e2eSkill
- repeat-with-delaySkill
- upstream-protocol-drift-watchSkill
- run-agmente-codex-e2eSkill
- run-agmente-e2eSkill
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
- Very specific: line 7
Read .agmente.paths (from repo root) before cross-checking ACP upstream docs/spec.
- Distinctive: line 16
When adding ACP method support:
- Distinctive: line 17
Add the method constant and typed payload mapping.
- Distinctive: line 19
Add response/event parsing coverage.
- Distinctive: line 20
Ensure delegate and pending-request behavior remain correct.
- Distinctive: line 21
Add package tests for success and failure paths.
- Distinctive: line 25
Keep slash-escaping compatibility option functional.
- Distinctive: line 26
Keep request ID/pending continuation behavior deterministic.
- Distinctive: line 27
Keep reconnection/disconnect semantics from breaking in-flight request handling.
- Very specific: line 30
Run package tests for ACPClient.
≈ “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.
Files
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:
- Add the method constant and typed payload mapping.
- Expose a typed service wrapper.
- Add response/event parsing coverage.
- Ensure delegate and pending-request behavior remain correct.
- 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.
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
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.

