openai / openai/codex

[Regression][macOS 26.803] Local/Worktree selector still missing from new-task composer

Open
#37,943 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

Codex / ChatGPT desktop version
  • Version: 26.803.61601
  • Build: 6396
  • Platform: macOS 26.6 (25G5028f), arm64
  • Surface: Codex in the unified ChatGPT desktop app
What happened?

When creating a new Codex task with the local project plural selected, the composer does not show any execution-environment control.

The composer footer shows only:

  • add / attachment button
  • Full access permission control
  • model selector (5.6 Sol Extra High)
  • microphone
  • send button

There is no visible Local, Work locally, Worktree, or New worktree selector. This prevents choosing an isolated managed worktree before submitting the task and leaves no visible confirmation of where the task will run.

Steps to reproduce
  1. Open the unified ChatGPT desktop app on macOS.
  2. Switch to Codex.
  3. Select a local Git-backed project.
  4. Start a new task.
  5. Inspect the composer controls before submitting.
Expected behavior

The composer should expose the Local/Worktree environment selector described in the current documentation, including a starting-branch selector when Worktree is chosen:

https://learn.chatgpt.com/docs/environments/git-worktrees

Actual behavior

No environment selector is present. Submitting from this state risks running directly in the project's shared local checkout without an explicit target choice.

Related issue

This appears to be a current reproduction of #32927, originally reported against 26.707. That issue remains open, and the same missing-selector UI is still present in 26.803.61601.

A screenshot captured on this build shows the project picker and the exact composer controls listed above.

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 by reproducing the missing control in the unified ChatGPT desktop app on macOS with a local Git-backed project, then review related issue #32927 and the linked git-worktrees documentation. Done means the new-task composer exposes the Local/Worktree selector, including a starting-branch selector when Worktree is chosen, and makes the execution target visible before submission.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
desktop-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.