9to5 coverage · Integrations
Code coverage for Codex
Give Codex exact uncovered changed lines and baseline context, then verify its tests against fresh CI coverage.
Upload coverage before connecting
Codex needs a local checkout to inspect source and run tests. 9to5 needs an installed GitHub App and at least one coverage upload for the repository. The connection grants access to coverage metadata; it does not generate the first report or install your test dependencies.
Connect with remote MCP
Add this server to your Codex configuration, then authorize it with your GitHub identity. Review the read-only coverage permission. If organization policy restricts integrations, use the approved client configuration.
[mcp_servers.9to5_coverage]
url = "https://coverage.9to5.software/mcp"codex mcp login 9to5_coverageFor Codex’s supported in-app browser workflow, open the signed-in coverage site and ask Codex to inspect the page. This uses the site’s browser tools without configuring a remote MCP server. Both approaches still require repository access and uploaded coverage.
Ask for a verified result
For OWNER/REPO PR NUMBER, inspect the latest coverage and identify the tested
head commit and recorded baseline. Find uncovered changed lines, inspect their
behavior in this checkout, and add focused tests. Run the relevant tests and
report what remains unverified until CI uploads coverage for the new commit.Review the tests as code. A useful test asserts a behavior, rather than merely executing a line. Ask Codex to paginate uncovered ranges and report missing baselines instead of guessing.
Keep local success and CI verification distinct
Local tests passing does not mean the hosted PR report has updated. After CI runs, inspect the new SHA, patch percentage and regressions. Keep the final report explicit about which checks passed and which are pending.