Release Codex Deck v0.5.0 - #1
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 97fa2d23ce
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if ($process.CommandLine -match '--remote-debugging-port=(\d+)') { | ||
| $candidate = [int]$Matches[1] | ||
| try { | ||
| $response = Invoke-WebRequest -UseBasicParsing -Uri "http://127.0.0.1:$candidate/json/version" -TimeoutSec 1 | ||
| if ($response.StatusCode -ge 200 -and $response.StatusCode -lt 300) { return $candidate } |
There was a problem hiding this comment.
When a user already has Codex running with --remote-debugging-port bound to a non-loopback address, for example --remote-debugging-address=0.0.0.0, this reuse path accepts the session just because /json/version answers on 127.0.0.1, so the launcher skips the code below that starts Codex with --remote-debugging-address=127.0.0.1 and leaves the privileged CDP bridge reachable from the network. Please only reuse ports whose command line is explicitly loopback-bound, or restart them.
Useful? React with 👍 / 👎.
1 participant
What changed
awaiting-approvalandawaiting-responsestates so they remain orange until the user responds.Why
This turns the original six-slot integration into a complete and more responsive Codex Micro control surface while keeping protected keycap SVGs local and out of the public package.
Validation
npm cinpm audit --omit=dev— 0 vulnerabilitiesnpm run checknpm test— 19/19 passingnpm run validatenpm run qa:local-icons— 30/30 local iconsnpm run pack-DryRun