Restore worktree & environment selection for Scheduled Tasks

Open 💬 1 comment Opened Jul 13, 2026 by meded90

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.62119

What subscription do you have?

PRO

What platform is your computer?

_No response_

What issue are you seeing?

What variant of Codex are you using?

Desktop App

Version

Powered by Codex & OWL
Version 26.707.62119
Released Jul 13, 2026

Platform: macOS

What feature would you like to see?

Please restore the ability to choose an existing Git Worktree and Environment when creating a Scheduled Task.

In previous versions I could create a scheduled task that executed inside a specific worktree with its configured environment. This was essential for unattended automation.

After the latest update this option is gone. Scheduled Tasks no longer allow selecting the worktree/environment, making many existing automation workflows impossible.

Why this matters

Many developers keep multiple feature branches as separate git worktrees.

Typical workflow:

  • feature-a → worktree A
  • feature-b → worktree B
  • each worktree has its own environment, dependencies and configuration
  • scheduled tasks run independently in the correct workspace

Without worktree selection:

  • scheduled tasks cannot target the intended workspace;
  • existing automations are broken;
  • users cannot safely run background coding tasks in parallel;
  • multiple repositories and environments become difficult to automate.

What steps can reproduce the bug?

Requested solution

Either:

  1. Restore the previous worktree/environment picker for Scheduled Tasks.

or

  1. Allow selecting any existing Project + Worktree + Environment when creating a scheduled task.

Please keep this functionality, as it was one of the strongest features for unattended Codex workflows.

What is the expected behavior?

_No response_

Additional information

This appears to be a regression rather than an intentional product change. If the feature was removed intentionally, please document the replacement workflow. Otherwise, please restore the previous behavior.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗