›_ Codex Issues
Codex Issues / #37815

ChatGPT Android app v0.147 hides Codex commands behind generic "Command execution" rows

Open 💬 4 comments Opened Aug 10, 2026 by rebroad
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex app are you using?

ChatGPT Android app version 1.2026.216, with Codex upgraded to v0.147.

What issue are you seeing?

After upgrading Codex to v0.147, the ChatGPT Android app no longer shows the commands being run by Codex. Each tool call is now collapsed to a generic Command execution row with no command text or other detail.

Before the upgrade, the app showed an expandable Ran N commands section and individual command summaries, for example Ran cpto ..., Ran just test -p codex-tui, and the command output/status. See the first supplied screenshot (Photo 1.jpg).

After the upgrade, the same kind of activity is represented only by generic Command execution rows, as shown in the second supplied screenshot (Photo 2.jpg).

Steps to reproduce

  1. Use Codex from the ChatGPT Android app.
  2. Start a task that runs one or more shell commands.
  3. Observe the activity cards while the task is running.
  4. Compare behavior before and after upgrading Codex to v0.147.

Actual behavior

The mobile UI displays Command execution without the command that is being run, making it difficult to understand or audit Codex's activity while a task is in progress.

Expected behavior

The app should continue displaying the command text (and, where available, the expandable command group, output, and status) for each command execution, as it did before v0.147.

Additional information

This appears to be a ChatGPT Android app rendering/regression issue rather than a failure to execute commands: the task continues and Codex's textual progress updates still appear. The regression became visible immediately after upgrading to v0.147.

Suspected regression point

Please investigate upstream PR #36893, commit fcf636a41d (included in the v0.147 release line): Redact secrets from app-server command execution items.

Although this change was introduced for secret redaction, it also changed how client-facing commandExecution.command and commandActions values are projected and sent through the app-server/remote-control path for live items, completed items, and replayed thread history. The local rollout files still contain the full command text, and the TUI can still display it, while recent sessions viewed through the ChatGPT Android remote-control UI show only a generic Command execution row. This suggests the regression may be in the changed backend projection or remote-control payload rather than in the rollout data or Android rendering alone.

Please verify whether the remote-control payload still includes the command field for ordinary commands such as just test, git status, and cpto, and compare it with the pre-v0.147 payload.

Screenshots supplied by the reporter:

  • Photo 1.jpg: previous behavior, session019fdc67-19e7-7340-922f-7ea5788da386 with individual command details visible.

!Screenshot_20260810_123223_ChatGPT.jpg

  • Photo 2.jpg: current behavior, session 019feb5d-b165-7df3-94db-445b2d5caec6 showing only generic Command execution rows.

!Screenshot_20260810_123235_ChatGPT.jpg

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 18 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #37213

Powered by Codex Action

arthurlapertosa · 16 days ago

UP!!
This new mode sucks!!! Why would they remove the commands and put just this generic summary??

higi · 9 days ago

I'm having the exact same issue. Since the latest update, command details are no longer visible in the chat. Previously, I could tap the command execution entry and see the actual command and its output, but now it only shows a generic “Command execution” item with no useful details.

ESKehler · 8 days ago

Additional reproduction observed on 2026-08-20 in ChatGPT Android Remote:

This is not limited to the command label being replaced by a generic Command execution row. Tapping an executed-command row does open a detail sheet, but the sheet is populated with planning/reasoning summaries instead of the executed command.

In the captured reproduction, the opened sheet showed entries such as:

  • Planning precise network metric and SSID restoration
  • Identifying ad-related domains near weather data (repeated)
  • Planning query filtering by timestamp and client
  • Planning timestamp-based filtering

It did not show the shell command, stdout/stderr, exit status, or other execution details.

Reproduction:

  1. Connect the Android ChatGPT app to a Codex Desktop host through Remote.
  2. Open a task in which Codex has executed shell commands.
  3. Tap an executed-command / Command execution row.
  4. Observe that a detail sheet opens with planning/reasoning activity rather than the selected command and its output.

The corresponding task on desktop contains the executed-command activity, so this appears to be incorrect mobile Remote item-to-detail routing or payload rendering rather than missing execution data. This prevents mobile users from auditing what Codex actually ran or diagnosing failed commands.

The Android app build was not rechecked during this occurrence; an earlier build captured on this device was 1.2026.209.