Agmente
CLAUDE.md545 starsChanged 9 months agoMITView on GitHub
This file is the entrypoint for cloud/Claude coding agents. Use it with Agents.md.
In this repository13 other files it gives its agents.
- ACPClient/AGENTS.mdAGENTS.md
- Agents.mdAGENTS.md
- Agmente/AGENTS.mdAGENTS.md
- AgmenteTests/AGENTS.mdAGENTS.md
- AgmenteUITests/AGENTS.mdAGENTS.md
- AppServerClient/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- acp-local-runnerSkill
- codex-local-cli-e2eSkill
- repeat-with-delaySkill
- upstream-protocol-drift-watchSkill
- run-agmente-codex-e2eSkill
- run-agmente-e2eSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
14 rules. About 0 are common, 8 are distinctive, and 6 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Use root .agmente.paths for machine-local external repo paths.
- Distinctive: line 18
Read this file when running upstream-spec/source checks.
- Distinctive: line 23
Keep ACP and Codex behaviors separate unless a shared abstraction is intentional and tested.
- Distinctive: line 26
Prefer component-local changes.
- Distinctive: line 27
Do not add personal local filesystem paths to tracked files.
- Distinctive: line 28
If behavior differs by protocol, document both expected paths.
- Distinctive: line 32
Update Agents.md and this file in the same PR when:
- Very specific: line 36
Update nested <component>/AGENTS.md in the same PR when behavior in that component changes.
- Very specific: line 37
If no docs are needed, include Docs: N/A in PR notes.
- Distinctive: line 40
Run focused tests for touched components first.
- Very specific: line 47
Treat run, execute, validate, and reproduce E2E requests as execute-only and agentic: run the real backend and tools, capture evidence, …
- Distinctive: line 48
Do not modify repo files during an execute-only E2E run unless the user explicitly asks to fix, stabilize, add hooks, or make the scenario …
- Very specific: line 53
Do not assume the in-session mcp_xcodebuildmcp_* subset includes interaction tools (tap, swipe, gesture, type-text, long-press).
- Very specific: line 54
If any required UI automation tool is missing from MCP exposure, switch to xcodebuildmcp CLI for simulator interaction.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.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
Agmente Cloud Agent Guide
This file is the entrypoint for cloud/Claude coding agents. Use it with Agents.md.
Read Order
Agents.md(root policy and protocol overview)- Component docs closest to changed code:
Agmente/AGENTS.mdACPClient/AGENTS.mdAppServerClient/AGENTS.mdAgmenteTests/AGENTS.mdAgmenteUITests/AGENTS.mde2e/AGENTS.md
Local Path Config
- Use root
.agmente.pathsfor machine-local external repo paths. - Required vars:
AGMENTE_ACP_REPO,AGMENTE_CODEX_REPO. - Read this file when running upstream-spec/source checks.
Core Architecture
- Agmente supports two protocol modes: ACP and Codex app-server.
- Protocol is detected after
initializeand routed to protocol-specific view models. - Keep ACP and Codex behaviors separate unless a shared abstraction is intentional and tested.
Contribution Rules
- Prefer component-local changes; avoid cross-cutting refactors unless needed.
- Do not add personal local filesystem paths to tracked files.
- If behavior differs by protocol, document both expected paths.
- For UI changes, keep accessibility identifiers stable or update UI tests in the same PR.
Documentation Rules
- Update
Agents.mdand this file in the same PR when:- adding a new top-level component,
- adding protocol support,
- changing cross-component architecture.
- Update nested
<component>/AGENTS.mdin the same PR when behavior in that component changes. - If no docs are needed, include
Docs: N/Ain PR notes.
Testing Expectations
- Run focused tests for touched components first.
- For protocol lifecycle changes, run both:
AgmenteTests/CodexServerViewModelTestsAgmenteTests/ViewModelSyncTests
- For UI flow or accessibility changes, run relevant
AgmenteUITests. - Codex E2E remains opt-in via environment configuration (see
AgmenteUITests/AGENTS.md). - For manual or simulator E2E requests, resolve the scenario from
e2e/scenarios/before consulting any skill. - Treat
run,execute,validate, andreproduceE2E requests as execute-only and agentic: run the real backend and tools, capture evidence, evaluate assertions, and clean up. - Do not modify repo files during an execute-only E2E run unless the user explicitly asks to fix, stabilize, add hooks, or make the scenario executable.
- For simulator interaction, prefer the
xcodebuildmcpCLI as the source of truth for available features:
npx -y xcodebuildmcp@latest tools- Do not assume the in-session
mcp_xcodebuildmcp_*subset includes interaction tools (tap,swipe,gesture,type-text,long-press). - If any required UI automation tool is missing from MCP exposure, switch to
xcodebuildmcpCLI for simulator interaction.
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.

