Area
apps/desktop
Steps to reproduce
- Run a T3 Code session that produces progress/reasoning summaries during a long-running task.
- Open the session in the T3 Code desktop client.
- Inspect the progress/reasoning entries in the transcript.
- Open the same session in the T3 Code mobile client and compare the corresponding entries.
The comparison was made using the same project and session, 2026-06-06-repo-fleet / Repo Fleet Recovery Path Defects.
Expected behavior
The desktop client should display the human-readable progress summary associated with each entry, consistently with mobile. For example: Reading release.py, Inspecting function, Refactoring activation flow, Running full tests, and Polling for completion.
If the desktop UI intentionally collapses these entries, expanding one should reveal its summary text rather than only a generic label.
Actual behavior
The desktop client renders repeated entries only as Thought or Thinking, with no meaningful explanation. The same session in mobile displays the readable summaries.
The session data is present: the local T3 Code transcript contains non-empty reasoning-summary messages for this run. This suggests the desktop client is losing or failing to render the summary text, rather than the provider omitting it.
Impact
This makes long-running desktop sessions difficult to follow and can make active work look stalled or broken. It also creates a significant visibility mismatch between desktop and mobile for the same session.
Evidence
I will attach:
- A desktop screenshot showing repeated generic
Thought / Thinking entries.
- A mobile screenshot showing the corresponding readable progress summaries for the same session.
Impact level
Major degradation or frequent failure
Version or commit
Desktop and mobile versions were not recorded at capture time.
Environment
macOS desktop client and T3 Code mobile client; Codex provider/model visible in the attached desktop screenshot.
Logs or stack traces
None.
Workaround
Use the mobile client to view the progress summaries. No equivalent desktop workaround is known.
Area
apps/desktop
Steps to reproduce
The comparison was made using the same project and session,
2026-06-06-repo-fleet/Repo Fleet Recovery Path Defects.Expected behavior
The desktop client should display the human-readable progress summary associated with each entry, consistently with mobile. For example:
Reading release.py,Inspecting function,Refactoring activation flow,Running full tests, andPolling for completion.If the desktop UI intentionally collapses these entries, expanding one should reveal its summary text rather than only a generic label.
Actual behavior
The desktop client renders repeated entries only as
ThoughtorThinking, with no meaningful explanation. The same session in mobile displays the readable summaries.The session data is present: the local T3 Code transcript contains non-empty reasoning-summary messages for this run. This suggests the desktop client is losing or failing to render the summary text, rather than the provider omitting it.
Impact
This makes long-running desktop sessions difficult to follow and can make active work look stalled or broken. It also creates a significant visibility mismatch between desktop and mobile for the same session.
Evidence
I will attach:
Thought/Thinkingentries.Impact level
Major degradation or frequent failure
Version or commit
Desktop and mobile versions were not recorded at capture time.
Environment
macOS desktop client and T3 Code mobile client; Codex provider/model visible in the attached desktop screenshot.
Logs or stack traces
None.
Workaround
Use the mobile client to view the progress summaries. No equivalent desktop workaround is known.