Codex Web: environments fail for GitLab projects nested in a subgroup
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
In Codex Web (chatgpt.com/codex), creating/testing an environment against a GitLab project that lives in a subgroup (group/subgroup/project) consistently fails with:
Terminal errored
Error connecting to the test environment
The same account and same settings work reliably for a GitLab project at the top level of a group (group/project).
What steps can reproduce the bug?
- Connect a GitLab account that has projects in a subgroup.
- Go to Settings -> Environments -> Create environment.
- Select a project nested in a subgroup, e.g.
group/subgroup/myproject. - Click "Restart session" on the Terminal panel
What is the expected behavior?
The container starts and runs like any top-level project.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Codex Web at Settings → Environments → Create environment, then reproduce the failure by selecting a GitLab project under group/subgroup and using Restart session in the Terminal panel. Compare the environment startup path for subgroup projects with a top-level project; done means the nested project container starts and runs like the top-level case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, rust
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100