Skip to content

Add public local Codex speed testing - #3

Merged
timmyagentic merged 4 commits into
mainfrom
codex/public-local-speed-test
Jul 16, 2026
Merged

Add public local Codex speed testing#3
timmyagentic merged 4 commits into
mainfrom
codex/public-local-speed-test

Conversation

@timmyagentic

Copy link
Copy Markdown
Owner

Summary

  • Add a guided local codexspeed command that discovers the installed Codex model catalog, shows the exact turn count and usage warning, requires explicit confirmation, prints local metrics, and never uploads automatically.
  • Add checksum-verified one-command launchers plus self-contained macOS, Linux, and Windows release packages, including Windows codex.cmd compatibility and native CI smoke tests.
  • Add /local, where any visitor can download the runner and open a result JSON entirely through the browser File API without API traffic.
  • Add a gated v0.2.0 release workflow that verifies, packages six platform/architecture targets, writes SHA256SUMS, and publishes only after every asset succeeds.

Validation

  • corepack pnpm check
  • 125 runner tests, 44 UI tests, 31 Worker tests, and 15 Playwright E2E tests
  • Final macOS ARM64 portable launcher doctor with Node/npm absent from PATH
  • Real bounded local run: GPT-5.6-Sol / low, 1 warm-up + 1 measured turn, valid local JSON, nothing uploaded
  • Interactive no-argument model/effort selection and cancellation before any model turn
  • Sensitive-output scan over tracked, untracked, and built outputs

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a6fd487f8f

ℹ️ 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".

Comment on lines +189 to +191
warmup: true,
models: [model.id],
efforts: [effort],

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Warm up using the selected reasoning effort

When a user selects a non-default effort (for example --effort high on a model whose default is medium), this schedule delegates the warm-up to buildSchedule, which chooses the model default effort for warm-ups rather than the filtered effort. The runner therefore displays and obtains confirmation for one selected effort but starts an additional real turn at a different effort; this can both misrepresent the chosen test configuration and consume a different allowance than the user expects. Construct the guided warm-up with effort explicitly, or disclose that distinct warm-up effort before confirmation.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2244dfa75f

ℹ️ 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".

Comment on lines +87 to +91
isAvailable: async (path) =>
access(path).then(
() => true,
() => false,
),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Require an executable Codex candidate

access(path) defaults to an existence check, so a non-executable file (or directory) named codex in an earlier PATH entry is selected and prevents discovery from reaching a later working Codex installation. In that setup every guided command fails when spawning the chosen candidate, rather than using the usable binary; probe executable permission on POSIX (and an appropriate runnable-file check on Windows) before returning it.

Useful? React with 👍 / 👎.

@timmyagentic
timmyagentic merged commit f1b955a into main Jul 16, 2026
2 checks passed
@timmyagentic
timmyagentic deleted the codex/public-local-speed-test branch July 16, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant