Feature request: Auto-generate Codex local environments from repo config/README (any stack)

What variant of Codex are you using?

Codex App ,CLI

What feature would you like to see?

Summary

It would be extremely valuable if Codex could auto-generate "Local Environment" setup (setup script + actions) from a repo’s existing config and README, for any tech stack (not only Java). This would dramatically speed up onboarding and make worktrees usable immediately.

Motivation

Today, teams manually craft setup scripts and actions in the Codex app settings. For larger orgs with many repos and mixed stacks (Node/Python/Java/go/Rust/etc), this doesn’t scale.

We want Codex to detect common project signals (e.g. package.json, pom.xml, pyproject.toml, go.mod, Cargo.toml) and propose a minimal, safe setup script + action list, leaving secrets/config placeholders to be filled by users.

Proposed Behavior

• Detect project stack by common config files.
• Suggest:

1) Environment dependencies (e.g. Node version, Java version, Python version).
2) Setup script (minimal, non-destructive).
3) Actions for build/test/start.

• Ask clarifying questions if multiple stacks are detected.
• Do NOT assume secrets. Only output placeholders.

Example

• Node repo:
• Setup script: npm install
• Actions: npm run build, npm test, npm start
• Java repo (Spring Boot):
• Setup script: mvn -DskipTests -pl <module> -am package
• Actions: mvn spring-boot:run -Dspring-boot.run.profiles=dev

Why this matters

Worktree environments exist precisely to reduce setup friction. Automating the initial environment suggestions would make Codex more scalable for teams.

Additional information

We run many repositories across multiple stacks and want consistent, automated environment setup for new worktrees. The feature should infer from repository files and README without guessing secrets, and produce a safe, minimal setup script + actions.