Codex Desktop: commit message generation and thread naming time out after update

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.519.41501 (3044)

What subscription do you have?

Pro x5

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

After a recent Codex Desktop update, the UI Git commit flow can no longer generate commit messages across multiple local Git repos. Thread naming is also failing intermittently. This appears to be a structured-generation timeout in Codex Desktop, not a Git/repo config issue.

Full relevant error from logs:

Failed to generate commit message errorMessage="Timed out waiting for structured result."

feature=commit_message
model=gpt-5.4-mini
status=error
inputTokens=183823
cachedInputTokens=183168

### What steps can reproduce the bug?

Feedback ID: 019e4fe7-8904-7771-8a6e-be28dc230bbd

## Repro steps

1. Use Codex Desktop on macOS.
2. Open or continue a long/high-context Codex thread.
3. Open a local Git repository with modified files.
4. Use the built-in Codex Desktop Git UI.
5. Try to generate a commit message from the UI commit flow.
6. Observe that commit-message generation fails before the commit can proceed.
7. In the same app/install, create or continue threads and observe thread-title generation also timing out intermittently.

Minimal repo setup for reproduction:

```bash
mkdir /tmp/codex-commit-message-repro
cd /tmp/codex-commit-message-repro
git init
printf "initial\n" > README.md
git add README.md
git commit -m "Initial commit"

for i in $(seq 1 200); do
  printf "line %s\n" "$i" >> README.md
done

git add README.md


inputTokens=183823
cachedInputTokens=183168
outputTokens=321
reasoningOutputTokens=142
totalTokens=184144
model=gpt-5.4-mini
reasoningEffort=low
status=error

### What is the expected behavior?

The expected behavior is that Codex Desktop should generate a commit message reliably from the current Git changes without depending on the full active chat/thread context.

For the Git UI:

- Commit-message generation should use a small bounded input, such as the staged diff, changed file list, branch/repo metadata, and any explicit user-provided style hint.
- It should not inherit the full current Codex thread history.
- It should complete within the UI timeout for normal and large repos.
- If generation fails or times out, the commit flow should fail softly, for example by allowing the user to type a message manually or by falling back to a simple deterministic draft.
- Git commit/push should not be blocked by the model failing to generate a structured commit-message result.

For thread naming:

- Thread-title generation should use a tiny bounded transcript slice, such as the first user request and maybe the first assistant response.
- It should not include tool logs, full transcript history, or unrelated long context.
- If thread-title generation times out, the app should fall back to a local deterministic title rather than leaving the naming flow broken.

In short: commit-message generation and thread-title generation should be bounded helper tasks that complete reliably or fail non-blockingly.

### Additional information

A few extra details that may help narrow this down:

- This started after a Codex Desktop update and affects multiple local Git repositories.
- Git itself works outside the Codex Desktop UI, so the failure appears isolated to the UI’s generated commit-message step.
- The same install also shows intermittent thread-title generation timeouts, suggesting a shared helper-generation/structured-result path rather than a Git-specific failure.
- The commit-message helper logged `inputTokens=183823` and `cachedInputTokens=183168`, which seems unexpectedly large for a commit-message generation task.
- My suspicion is that the helper task is inheriting the current thread context, even though the actual commit diff/prompt should be small and bounded.
- There is also a feature-flag mismatch in the same install:

```text
unsupported feature enablement `auth_elicitation`: currently supported features are apps, memories, mentions_v2, plugins, remote_control, tool_suggest, tool_call_mcp_elicitation