CodexReviewKit
lynnswap/CodexReviewKit
Native macOS app and local MCP server for running and monitoring Codex review jobs.
Instalação
npx convez-ai lynnswap/CodexReviewKit1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
CodexReviewKit
CodexReviewKit is the native macOS companion app for Codex review.
Launch CodexReviewMonitor.app, register its MCP endpoint with Codex, then run
reviews through the codex_review tools while the app keeps the review state
visible.
Quick Start
-
Launch
CodexReviewMonitor.app. -
Register the local MCP endpoint in the client you use.
Codex CLI:
codex mcp add codex_review --url http://localhost:9417/mcpClaude Code:
claude mcp add --transport http codex_review http://localhost:9417/mcp -
Use the review tools from Codex:
review_startreview_awaitreview_listreview_readreview_cancel
What Runs Locally
CodexReviewMonitor.appshows review jobs, output, and findings.http://localhost:9417/mcpis the app-managed MCP endpoint.codex app-serverruns behind CodexReviewMonitor as the live review backend.~/.codex_reviewis the dedicated Codex home used by CodexReviewMonitor.
Timeout Setup
Long reviews can exceed the default MCP client timeout. codex mcp add does
not currently expose timeout flags, so add them manually after registration:
[mcp_servers.codex_review]
url = "http://localhost:9417/mcp"
startup_timeout_sec = 1200.0
tool_timeout_sec = 1200.0
This config belongs to the Codex client that calls the MCP server. It is
separate from CodexReviewMonitor's dedicated runtime home at ~/.codex_review.
More Detail
- Architecture: package boundaries, runtime flow, and test responsibilities.
- MCP reference: tool schemas, discovery resources, session behavior, and runtime files.
Local Release
Public macOS archives are built locally so Developer ID certificates and notary
credentials stay out of CI. The local script signs, notarizes, staples, pushes
the tag from main, creates the draft release asset, and then explicitly
dispatches the release verification workflow for that tag. The workflow runs
tests with read-only repository access and publishes the draft release only
after verification succeeds.
scripts/publish-local-release.sh \
v0.0.2 \
--signing-identity "Developer ID Application: Your Team (TEAMID)" \
--notary-profile "codex-reviewkit"
Create the notarytool profile in the local Keychain before publishing:
xcrun notarytool store-credentials codex-reviewkit