Eric Traut f94c49cf46 Use deep links for macOS codex app paths (#25485) ...

## Why

`codex app [PATH]` is the documented CLI entry point for opening Codex
Desktop on a workspace. Recent desktop builds can focus the app while
failing to honor paths passed as macOS document-open arguments via `open
-a Codex.app <workspace>`, which broke `codex app .` for users. See
#25333; related report: #25166.

The desktop app still supports the explicit
`codex://threads/new?path=...` route, so the CLI should use that
app-owned launch surface instead of depending on folder-open event
delivery.

## What Changed

- Build a `codex://threads/new?path=<workspace>` URL in the macOS app
launcher.
- Pass that URL to `open -a <Codex.app>` instead of passing the
workspace path as a document argument.
- Add coverage that workspace paths needing escaping round-trip through
URL query encoding.

## Verification

- `just test -p codex-cli codex_new_thread_url_encodes_workspace_path`

f94c49cf46 · 2026-06-01 09:17:08 -07:00

History

..

src

Use deep links for macOS codex app paths (#25485)

2026-06-01 09:17:08 -07:00

tests

Move memory state to a dedicated SQLite DB (#24591)

2026-05-26 20:07:25 +02:00

BUILD.bazel

Wire realtime WebRTC native media into Bazel (#17145)

2026-04-08 15:15:55 -07:00

build.rs

Add WebRTC media transport to realtime TUI (#17058)

2026-04-08 10:26:55 -07:00

Cargo.toml

Allow API-key auth for remote exec-server registration (#24666)

2026-05-27 21:17:38 +00:00