You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a Codex skill that researches, revises, and executes plans
a terminal interface where you read and annotate those plans
The npm command installs both. This walkthrough goes from a clean install to a
reviewed plan being built in Codex.
Install it
npm install --global @thisisnsh/planx
You need Node 20.19 or newer. The installer detects Codex and writes the PlanX
skill alongside your other Codex skills.
Start a new Codex session afterward. Skills are part of the agent's available
workflow context; a session that was already running may not have loaded the
new one. You can check the installed CLI separately:
Use n for a note that applies to the whole plan. Use e when you want to
replace a line with exact wording instead of asking Codex to interpret a
correction.
Press s to open the hand-off menu, then choose Revise plan in the session
that wrote it.
PlanX resumes the recorded Codex thread and delivers the complete review. The
repository research is still in that thread; your feedback is added to it
instead of being handed to a fresh agent with no history.
Codex captures the result as v2 and stops again. Reopen it:
planx <plan-id> v2
This time you see a word-level diff against v1, with unchanged text folded.
Press d to switch between the diff and the full document. If anything is
still wrong, leave another comment and repeat. Every round produces one new
version.
Once v2 is right, press s and choose an execute hand-off. The prompt sent to
Codex names the plan and the version:
$planx execute <plan-id> v2
The skill reads the stored plan, keeps its open comments in view while working,
implements the change, runs the checks, and records the Codex thread that built
it. Later, the PlanX picker can resume that build session directly.
Then start a new Codex session and type $ or use /skills to look for planx. If Codex was installed after PlanX, the npm installer could not detect
it on the first pass; add-skills is the repair for that order.
$planx <task> # inside Codex
planx <plan-id> v1 # in the shell
# comment, then press s to revise
planx <plan-id> v2 # review the diff
# press s to execute v2
PLAN → REVIEW → REVISE → EXECUTE → RESUME
The point is not to make Codex plan more. It is to give you a place to decide
what Codex will build, and a version number that preserves that decision.
PlanX is MIT, nothing is hosted, and every plan stays local. If this got your
first Codex review working, a star helps
the next person find it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
How to use PlanX with Codex CLI
PlanX has two pieces:
The npm command installs both. This walkthrough goes from a clean install to a
reviewed plan being built in Codex.
Install it
You need Node 20.19 or newer. The installer detects Codex and writes the PlanX
skill alongside your other Codex skills.
Start a new Codex session afterward. Skills are part of the agent's available
workflow context; a session that was already running may not have loaded the
new one. You can check the installed CLI separately:
More: Installation
Know which command belongs where
This is the only naming wrinkle:
$planx <task>planx <plan-id> v1/plan <task>Codex uses
$for skills. OpenAI documents that you can type$to mention askill or use
/skillsto select one.The unprefixed
planxcommand is the executable installed by npm.So this goes into Codex:
And this goes into the shell after Codex hands the plan back:
Create the first version
Ask PlanX for a real change you have not started implementing:
The skill will:
v1, associated with the current Codex threadIt ends with:
Keep the id and version together. PlanX commands never guess which version you
mean.
More: The skill ·
Planning with Codex
Review it in the terminal
Exit Codex and run the command it printed:
Start by folding what you already accept:
spacefolds the section under the cursor[and]jump between section headingsgandGjump to the top and bottom?opens the complete key listThe goal is not to keep the whole plan expanded and admire it. The goal is to
reduce the screen to the decisions that still need attention.
More: Reviewing
Add feedback without paraphrasing the location
To comment on a passage:
vfand type the commentUse
nfor a note that applies to the whole plan. Useewhen you want toreplace a line with exact wording instead of asking Codex to interpret a
correction.
More: Feedback and edits
Revise in Codex
Press
sto open the hand-off menu, then choose Revise plan in the sessionthat wrote it.
PlanX resumes the recorded Codex thread and delivers the complete review. The
repository research is still in that thread; your feedback is added to it
instead of being handed to a fresh agent with no history.
Codex captures the result as
v2and stops again. Reopen it:This time you see a word-level diff against
v1, with unchanged text folded.Press
dto switch between the diff and the full document. If anything isstill wrong, leave another comment and repeat. Every round produces one new
version.
More: Versions and diffs
Execute the approved version
Once
v2is right, presssand choose an execute hand-off. The prompt sent toCodex names the plan and the version:
The skill reads the stored plan, keeps its open comments in view while working,
implements the change, runs the checks, and records the Codex thread that built
it. Later, the PlanX picker can resume that build session directly.
More: Hand-offs ·
Resuming a build
If
$planxdoes not appearRun:
Then start a new Codex session and type
$or use/skillsto look forplanx. If Codex was installed after PlanX, the npm installer could not detectit on the first pass;
add-skillsis the repair for that order.If the CLI itself is missing, reinstall it:
More: Installation ·
CLI reference
The whole loop
PLAN → REVIEW → REVISE → EXECUTE → RESUMEThe point is not to make Codex plan more. It is to give you a place to decide
what Codex will build, and a version number that preserves that decision.
PlanX is MIT, nothing is hosted, and every plan stays local. If this got your
first Codex review working, a star helps
the next person find it.
All reactions