Skip to content

test(harness): verify Codex MCP discovery and auth lifecycle #879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BYWallace merged 4 commits into from
Sep 9, 2026
+528 −3
Merged

test(harness): verify Codex MCP discovery and auth lifecycle #879

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b096371
test(harness): verify Codex MCP discovery and auth lifecycle
BYWallace Sep 8, 2026
e2ff282
test(harness): name the cause when the Codex MCP probe fails
BYWallace Sep 9, 2026
a3d0c44
test(harness): handle MCP fixture failures safely
BYWallace Sep 9, 2026
6cfd760
test(harness): wait for Codex login to finish
BYWallace Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions packages/harness/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,27 @@ Architecture: a single Node process (Express + ws + node-pty) serves the built
SPA, a small REST API, terminal WebSocket streams, and the local telemetry
ingest endpoint. The interface contract lives in `src/shared/types.ts`.

### Codex MCP validation

The ordinary unit and server tests cover launch/resume conversion, login and
credential refresh, logout, and error reporting. To verify actual tool discovery
with an installed Codex CLI, build the harness's workspace dependencies, then
run the opt-in test:

```bash
pnpm --filter "@sapiom/harness^..." build
RUN_CODEX_MCP_INTEGRATION=1 pnpm --filter @sapiom/harness exec vitest run src/core/adapters/codex-mcp.integration.test.ts
```

The test runs the `codex` binary found on `PATH`. Set `CODEX_TEST_BINARY` to the
path of a different installed version to test that one instead.

This test uses a temporary Codex home, the built `sapiom-dev` server, and local
HTTP fixtures. It requires no Codex login or model request and checks both a
fresh home and an existing configuration with conflicting server registrations.
It also checks that command environments exclude MCP credentials and the Electron
launch flag while preserving unrelated user shell settings.

### Project sessions and Agent Map bootstrap

Every session whose working directory resolves to a Studio project is an
Expand Down
Loading
Loading