Codex Desktop should show current project, cwd, and Git branch in thread UI

Open 💬 2 comments Opened Jun 18, 2026 by shurrman

Summary

Codex Desktop should show the active project/workspace directory and Git branch prominently in the thread UI, similar to how the CLI can expose project and branch context in its status line.

Problem

In Codex Desktop, it is not obvious which local project/directory a thread is currently operating in, nor which Git branch or worktree is active. Users can ask Codex or open the integrated terminal and run pwd, git rev-parse --show-toplevel, and git branch --show-current, but that is friction for something that is fundamental context for every coding task.

This is especially confusing when:

  • multiple Codex Desktop threads are open across different projects;
  • a user switches between Local and Worktree modes;
  • projectless chats create Codex-managed temporary directories;
  • a user expects parity with the CLI/TUI, where status-line context can be configured;
  • a task involves commits, reviews, deploys, or any operation where the wrong repo/branch is costly.

Requested UX

Add a persistent, visible project context indicator to Codex Desktop threads.

Suggested fields:

  • Project name
  • Current working directory
  • Git repository root, when different from the working directory
  • Current Git branch
  • Local vs Worktree vs Cloud mode
  • Worktree path/name, when applicable
  • Dirty state indicator, if cheap and reliable

Suggested behavior:

  • Show a compact label in the thread header, for example: my-repo · feature/foo · Worktree.
  • Allow clicking/hovering to reveal full paths.
  • Provide quick actions to copy cwd, copy repo root, open terminal, open Finder, or open the project in the configured editor.
  • For non-Git/projectless chats, show that explicitly, for example: Projectless chat · Codex-managed directory.
  • Keep this visible during long-running work and when approval dialogs appear.

Why this matters

This context is safety-critical, not just cosmetic. Codex can edit files, run commands, commit, push, create worktrees, and operate across multiple local projects. Users need continuous awareness of where the agent is operating before approving commands or interpreting results.

The CLI already has configurable status-line concepts such as project and git branch. Desktop should provide an equivalent first-class affordance rather than requiring terminal commands or asking the agent.

Current workaround

Open the integrated terminal and run:

pwd
git rev-parse --show-toplevel
git branch --show-current

or ask Codex to run those commands. This works, but it is not discoverable and does not provide persistent situational awareness.

View original on GitHub ↗

2 Comments

shurrman · 2 months ago

Additional real-world example: this issue was discovered from a projectless Codex Desktop chat. The user did not explicitly open a repository/project, but the thread still had a real writable cwd:

/Users/aaa/Documents/Codex/2026-06-18/applications-mentioned-by-the-user-appshot

That makes the problem worse: the UI does not only hide the repo/branch for normal projects, it also hides when the thread is operating inside a Codex-managed generated workspace. In that case the header should explicitly say something like:

Projectless chat · Codex-managed workspace

and expose the actual cwd on click/hover. Otherwise users can create files, outputs, or run commands in a directory whose existence and location are invisible from the main UI.

onodanaoto-main · 1 month ago

I strongly agree with this request.

As a Codex Desktop user (Windows), I often find it difficult to visually confirm which project/workspace Codex is currently operating in and what files exist in that workspace. Asking Codex to show the folder structure works as a workaround, but it is slower and does not provide the same confidence as a persistent file explorer.

A VS Code / Cursor-style file tree or workspace sidebar would make Codex much easier to use as a primary coding tool. In particular, it would help with:

  • Confirming the current project root path
  • Browsing files and folders without leaving Codex
  • Understanding which files Codex created or modified
  • Opening or referencing files directly from the UI
  • Avoiding mistakes when multiple projects or threads are open

Even if the panel is optional or toggleable, having a reliable, visible workspace explorer would greatly improve usability and user confidence.

This is closely related to the need for Codex Desktop to show the current project/cwd more clearly as well: #28977