codex - 💡(How to fix) Fix Codex UI shows git branch but not the effective working directory used by agent tool calls

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

This creates confusion and risk because branch information is only meaningful relative to a repo/worktree. A user may believe work is happening in one repo when files are actually being created or modified in another.

RAW_BUFFERClick to expand / collapse

Title: Codex UI shows git branch but not the effective working directory used by agent tool calls

Issue: The Codex UI exposes the current git branch, but it does not clearly show the effective working directory/repo root being used by the agent for each turn or tool call.

Why this matters: The visible terminal prompt can remain on one directory while the agent executes commands with an explicit different workdir. In that case, Ctrl-J or the terminal prompt can show: C:\Users\Richard\source\repos\PhxBiz\Eventryx\Eventryx.AgenticSDKPlugin

while the agent is actually editing/running commands in: C:\Users\Richard\source\repos\PhxBiz\phoenix-sdk-integration-mcp

This creates confusion and risk because branch information is only meaningful relative to a repo/worktree. A user may believe work is happening in one repo when files are actually being created or modified in another.

Expected behavior: Codex should show the effective working directory and git repo root alongside the branch. Ideally it should distinguish:

  • Thread default CWD
  • Visible terminal prompt CWD
  • Last tool-call workdir
  • Git repo root
  • Current branch

Suggested UI: Active workdir: <absolute path>

Git repo: <absolute repo root>

Branch: <branch name>

Last command workdir: <absolute path>

Impact: This would reduce wrong-repo confusion, improve trust in multi-repo workflows, and make worktree changes easier for users to audit.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex UI shows git branch but not the effective working directory used by agent tool calls