Support VS Code and Cursor workspaces when selecting Codex projects

What variant of Codex are you using?

App 26.623.42026

What feature would you like to see?

Type

Feature request / UX enhancement

Summary

It would be very useful if Codex App could support selecting VS Code / Cursor workspace files as projects, instead of only selecting a single folder.

Problem

In full-stack development, a feature often spans multiple repositories. For example, one task may require changes across:

• Frontend repo
• Backend repo
• Shared SDK repo
• Infrastructure or deployment repo

Currently, Codex project selection appears to be folder-based. This works for single-repo projects, but it is less convenient for multi-repo development.

A possible workaround is to place several repositories under one large parent folder and select that folder. However, this is not always ideal:

• Not every feature needs all repositories under the parent folder
• A large parent folder may include unrelated repos
• It can make the project context noisier than necessary
• It does not match how developers already organize multi-repo work in VS Code or Cursor

VS Code / Cursor workspace files are already a good way to define a precise set of folders for a specific feature or development context.

Proposed solution

Allow Codex App to select and open VS Code / Cursor workspace files as projects.

For example, Codex could support:

• .code-workspace files from VS Code
• Cursor-compatible workspace files, if different
• Multi-root workspace definitions

When a workspace is selected, Codex would treat the folders listed in the workspace as the active project roots.

Use case

A developer working on a full-stack feature may create a workspace containing only the relevant repositories:

• web-app
• api-server
• shared-types

Another feature may require a different workspace:

• admin-dashboard
• billing-service
• notification-service

This gives much finer control than selecting one large parent directory containing all repos.

Expected behavior

When choosing a Codex project, users should be able to select a workspace file and have Codex load the folders defined in that workspace.

Codex should ideally:

• Show the workspace name in the project list
• Include all workspace folders as project roots
• Respect the folder set defined by the workspace
• Avoid pulling in unrelated sibling repositories

Expected benefits

• Better support for full-stack and multi-repo development
• More precise project context
• Less noise from unrelated repositories
• Better alignment with existing developer workflows in VS Code and Cursor
• Easier switching between feature-specific working sets

Additional context

This would make Codex project selection more flexible without requiring users to restructure their repositories. Workspace files already solve the problem of defining a focused multi-folder development context, so supporting them directly would fit naturally into Codex App project management.

Additional information

_No response_