codex-local-cli-e2e
Skill545 starsChanged 9 months agoMITView on GitHub
Run and debug Agmente iOS end-to-end tests against a real local Codex CLI app-server instance. Use when validating Codex websocket/protocol compatibility, connect/initialize/thread flows, or reproducing Codex-only UI test failures with an actual local Codex server.
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
- CLAUDE.mdCLAUDE.md
- acp-local-runnerSkill
- repeat-with-delaySkill
- upstream-protocol-drift-watchSkill
- run-agmente-codex-e2eSkill
- run-agmente-e2eSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Run Agmente's Codex UI E2E test against a real local codex app-server, using the repo-owned scenario spec as the source of truth, collect …
- Very specific: line 20
Use references/agmente-codex-e2e-contract.md only for the UI-test environment-variable harness contract.
- Distinctive: line 22
Start or verify server.
- Very specific: line 23
If managed server, start the command and wait until the endpoint port is reachable.
- Very specific: line 24
If existing server, verify reachability before running tests.
- Distinctive: line 26
Run only the Codex UI E2E test.
- Very specific: line 35
Read .xcresult details when xcodebuild is not explicit.
- Distinctive: line 39
Stop app-server if this run started it.
- Distinctive: line 46
Use the bundled script for deterministic runs:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
Codex Local CLI E2E
Overview
Run Agmente's Codex UI E2E test against a real local codex app-server, using the repo-owned scenario spec as the source of truth, collect actionable failure details, and always clean up simulator/app-server state.
Workflow
- Resolve run inputs.
- Require
endpoint(for examplews://127.0.0.1:8788) and simulatorUDID. - Decide run mode:
existing server: server already running.managed server: start server with a provided command and stop it during cleanup.
- Read
e2e/scenarios/codex/local-cli-smoke.md. - Use
references/agmente-codex-e2e-contract.mdonly for the UI-test environment-variable harness contract.
- Start or verify server.
- If
managed server, start the command and wait until the endpoint port is reachable. - If
existing server, verify reachability before running tests.
- Run only the Codex UI E2E test.
- Export:
AGMENTE_E2E_CODEX_ENABLED=1AGMENTE_E2E_CODEX_ENDPOINT=<endpoint>
- Execute targeted test only:
AgmenteUITests/AgmenteUITests/testCodexDirectWebSocketConnectInitializeAndSessionFlow
- On failure, extract root cause.
- Parse
xcodebuildoutput for the failing test and assertion. - Read
.xcresultdetails whenxcodebuildis not explicit. - Include failing file/line and endpoint/simulator context in the report.
- Always clean up.
- Stop app-server if this run started it.
- Uninstall app from simulator:
xcrun simctl uninstall <UDID> com.example.Agmente
- Optionally shut simulator down if requested.
Preferred Execution
Use the bundled script for deterministic runs:
scripts/run_codex_local_e2e.sh
Managed-server example:
scripts/run_codex_local_e2e.sh \
--endpoint ws://127.0.0.1:8788 \
--udid <SIMULATOR_UDID> \
--start-codex-cmd "codex app-server --listen ws://127.0.0.1:8788"Existing-server example:
scripts/run_codex_local_e2e.sh \
--endpoint ws://127.0.0.1:8788 \
--udid <SIMULATOR_UDID>Reporting Requirements
Always report:
- Endpoint used.
- Simulator UDID used.
- Pass/fail status.
- Failing assertion and file/line (if failed).
- Paths to
xcodebuildlog and Codex server log.
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.

