Problem

The Codex CLI provider failed when LibreFang was started as a desktop application or daemon outside a Git repository.

The provider check still reported Codex as available because it only verified that the executable and credentials existed. The first real completion then failed with:

Not inside a trusted directory and --skip-git-repo-check was not specified.

The driver also passed the deprecated --full-auto option, producing a warning on every request.

Root cause

LibreFang launched codex exec in the process working directory.

Desktop and daemon processes are not guaranteed to start inside a Git repository, while non-interactive Codex execution rejects such directories unless --skip-git-repo-check is explicitly supplied.

Changes

• Always pass --skip-git-repo-check to codex exec.
• Replace deprecated --full-auto with --sandbox workspace-write.
• Update the driver warning and documentation to describe the current sandbox option.
• Add regression tests that verify the complete argument list in both permission modes.
• Add an entry to the unreleased changelog.

Verification

• cargo fmt --check
• cargo test -p librefang-llm-drivers --lib codex_cli
  • 14 Codex CLI driver tests passed.
• cargo clippy -p librefang-llm-drivers --lib -- -D warnings
• Built a local librefang-desktop release package.
• Verified that the packaged executable contains --skip-git-repo-check and no longer contains --full-auto.
• Installed the package and completed real Codex CLI-backed agent requests from the desktop application.

Out of scope

The desktop dashboard currently retries an agent WebSocket connection with an Origin based on its random frontend port, while the API validates it against the separate API listen port. This produces repeated 403 Origin validation failed warnings. HTTP message fallback still works, and this separate desktop/WebSocket issue is not included in this PR.