Put the installed codex binary on PATH for review agents

Open
#111 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@muspi-merol-review is already working on this.

Since Nov 16, 2026.

  • #114 by @muspi-merol-review — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
github-actions, typescript
Domain
ci-cd

Research direction

Start with scripts/configure-review.sh and the workflow steps that consume CODEX_BIN; compare how setup exports the binary directory with how later steps receive it. Check the review prompt's advertised CLI tooling, then run a probe such as codex --version in the review environment. Done means the installed CLI is discoverable to the agent; linked pull request #114 indicates work is already underway.

Written by the indexing model from the issue text.

Description

A review run that probed the CLI got:

/bin/bash: line 1: codex: command not found

Exit 127, run 43764183120.

scripts/configure-review.sh installs @openai/codex under $RUNNER_TEMP/codex and exports that bin directory only inside the setup shell. Later steps receive CODEX_BIN, but no PATH entry, and the review prompt advertises codex-cli <version> as available tooling without naming that variable. The agent can run the reviewer, but cannot inspect or drive the CLI it is told is installed.

Append $RUNNER_TEMP/codex/node_modules/.bin to $GITHUB_PATH (or point the prompt at $CODEX_BIN) so a probe like codex --version behaves.

Found while auditing 413 review artifacts; this is the only missing-CLI case in them.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1h 39m
Merged PRs (30d)
84

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from promplate/code-review

All issues in promplate/code-review

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.