pingdotgg / pingdotgg/t3code

[Bug]: Codex's command activity displays shell-wrapper quoting instead of the executed command

Open
#11,362 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. Open any project in T3 Code using the Codex provider.
  2. Ask Codex to run this exact command:
pwd && rg --files -g 'AGENTS.md' -g '!node_modules'
  1. Wait for the command to complete successfully.
  2. Expand the command activity row.
  3. Copy the displayed command and run it in zsh.

The copied command contains altered quoting around !node_modules and fails with a zsh error. The command originally submitted to the shell succeeds.

Expected behavior

The command activity row should display the exact command Codex executed. Copying it should produce a valid command with the original quoting preserved.

Here I tested it using the Claude provider, it shows correctly:
Image

Actual behavior

The command runs successfully, but the activity row displays the shell launcher's escaped version instead of the command Codex executed. Single-quoted arguments are altered, so copying the displayed text produces an invalid command that fails in zsh.

Here I tested it using the Codex provider with the same prompt, it produced '"'!node_modules'"':
Image

Impact

Cosmetic issue

Version or commit

v0.0.41-nightly.20260911.1520

Environment

Linux desktop AppImage, zsh, Codex provider

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apps/web by tracing the Codex command-activity rendering and compare the displayed command with the command submitted to the shell. Reproduce with the provided pwd and rg command in zsh; done means the activity row preserves the original quoting and the copied command runs successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.