Can worktree creation be supported for projects with multiple Git repositories?

English translation:

What variant of Codex are you using?

App

What feature would you like to see?

Our projects usually involve multiple repositories that need to be developed together.
My current approach is to create a worktree for each repository, place these worktrees under the same path/folder, and then open that folder with Codex. However, there is a problem with this approach: when I work on requirements in parallel, I need to manually create the same set of worktrees again and then open them with Codex.
I hope Codex can support creating a parallel directory when the root directory is not a Git repository but contains multiple Git projects, allowing the user to specify a project name and then switch all Git repositories under the project to that branch.

Additional information

_No response_

<!-- codex-issue-translator -->

I have the same use case in the Codex App: one non-Git workspace directory contains separate frontend and backend Git repositories that must be changed and tested together.

Currently, the New worktree UI exposes one project-level starting-branch picker. There is no repository selector or visible repository-to-branch mapping, so a managed worktree task cannot isolate both repositories together.

The ideal workflow would:

• allow a Codex project to explicitly include multiple Git repositories;
• create one managed worktree per repository under a single task workspace;
• let the user select the starting branch or working-tree state independently for each repository;
• show the repository-to-starting-state mapping before the task starts;
• keep Handoff, branch creation, cleanup, and task lifecycle coordinated across the set;
• handle repositories whose corresponding feature branches have different names or do not yet exist.

This would make cross-repository feature work compatible with Codex managed worktrees instead of requiring us to construct and maintain paired worktrees manually.