Skip to content

fix(desktop): use augmented PATH for readiness probes#1613

Open
Areson wants to merge 1 commit into
block:mainfrom
Areson:Areson/fix-codex-readiness-path
Open

fix(desktop): use augmented PATH for readiness probes#1613
Areson wants to merge 1 commit into
block:mainfrom
Areson:Areson/fix-codex-readiness-path

Conversation

@Areson

@Areson Areson commented Jul 7, 2026

Copy link
Copy Markdown

Why

Packaged desktop launches can have a sparse GUI PATH. Readiness probes resolved the Codex/Claude binary but then ran it without the augmented PATH used for agent startup, so npm shims with /usr/bin/env node could fail before checking login state.

What

  • Run CLI login probes with the same augmented PATH used for managed agent launches
  • Split CLI probe execution into a small readiness submodule and add a Unix regression test for /usr/bin/env node shims
  • Update Codex setup copy to codex login and remove an unused runtime re-export that blocked targeted clippy

Risk Assessment

Low — scoped to desktop managed-agent readiness probes and setup nudge copy. Probe execution still uses the resolved absolute binary path and only augments PATH for child process interpreter lookup.

References

  • ./bin/just desktop-tauri-fmt-check
  • pnpm --dir desktop check:file-sizes
  • ./bin/just desktop-tauri-test
  • Pre-push hooks on fork: check-push-org, rust-tests, desktop-test, desktop-tauri-test, mobile-test
  • ./bin/just desktop-tauri-clippy currently fails on broader existing Tauri warnings outside this PR; not expanded here.

Generated with Codex

@Areson Areson force-pushed the Areson/fix-codex-readiness-path branch from 1ea100a to 517e9f9 Compare July 8, 2026 00:21
Co-authored-by: Ian Oberst <ioberst@squareup.com>
Signed-off-by: Ian Oberst <ioberst@squareup.com>
Co-authored-by: Codex <noreply@openai.com>
Ai-assisted: true
@Areson Areson force-pushed the Areson/fix-codex-readiness-path branch from 517e9f9 to a2a90be Compare July 8, 2026 00:40
@Areson Areson marked this pull request as ready for review July 8, 2026 01:34
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