pr: https://git.cafe/pingdotgg/t3code/pulls/32597 main: 6c9adfb2739205244b84e607736f6fd8b4611e69 original pr: 52c227969f56b453eaa7ab7d30b3245b3387806e corrected head: 98c6c0872f0832926d0d7beb45f091125b51e5cd linux; codex-cli 0.164.0; gpt-6.1-sol; real local proxy main UI: project -> real Codex read/write turn -> configure CODEX_HOME and --profile verify-launch -> regenerate title / commit cause: 'TextGenerationError: Text generation failed in generateThreadTitle: Codex CLI command failed: Error: Model provider `verify-missing-provider` not found commit toast: Text generation failed in generateCommitMessage: Codex CLI command failed: Error: Model provider `verify-missing-provider` not found original pr UI: same real repository, same provider profile -> commit succeeded fa8dc45 docs: clarify provider integration verification MCP discovery (actual CLI): CODEX_HOME=/home/user/verify-codex codex mcp list --json -> [] CODEX_HOME=/home/user/verify-codex codex --profile verify-launch mcp list --json -> profileComputer, enabled=true profileComputer runs installed computer MCP server with a startup-log wrapper, no tools requested original pr UI regenerate title -> startup log count 1 corrected UI regenerate title -> successful title "Verify Codex Launch Arguments", startup log count still 1 corrected UI commit with invalid default provider and working selected profile -> f3119ea docs: clarify profile selection behavior startup log count still 1 nearby behavior: normal gpt-6.1-sol chat, file reading, edits, resumed turn and --config model_reasoning_effort="low" worked blacksmith vp run check:changed: pass format 0.2s pass lint 0.4s pass knip 1/2 5.7s pass knip 2/2 11.7s pass graphql (apps/server) 0.4s pass typecheck (3 packages) 6.0s pass test (3 files) 13.0s CI also runs: full test suites, build unused patch check skipped: no dependency files changed pass not cached: files changed during the run not verified: real Ollama/LM Studio endpoint; native clients; macOS/Windows; older Codex versions profile-configured chat is unsupported by installed app-server CLI (unexpected --profile), separately observed on main and PR; no claim that the PR fixes it