Cloud environments and repository access

Home Tools Platforms Codex Cloud environments and repository access

Prepare a repeatable remote environment with dependencies, scoped secrets, and a known test command.

Coding & development · Documented · Documentation checked 2026-10-04

Codex CLI, IDE extension, and desktop coding work; cloud environments need separate setup.

Cloud environment and GitHub access must be enabled for the account / workspace. Existing tasks retain their own environment state.

The worked example is illustrative and has not been tested in a signed-in product account.

What it does and how it connects

Prepare a repeatable remote environment with dependencies, scoped secrets, and a known test command.

A cloud environment prepares repository access, dependencies, startup steps, and permitted networking for remote work. Environment preparation differs from the code task itself. Published environment configuration affects new tasks; existing tasks can retain their own saved state.

Walkthrough

Use the product named in the access panel. The steps below combine documented controls with the editorial example.

  1. Confirm eligible cloud access and connect the intended repository identity.
  2. Create an environment through the documented Work cloud-environment flow.
  3. Configure dependency and test setup with scoped secrets; avoid production credentials.
  4. Run a small repository task and inspect setup logs, checks, and the resulting branch or files.

Worked example

Prepare a sample website environment so a remote agent can run its build. The first task should confirm dependency installation and a known test, rather than making broad feature changes. Missing service access should remain an explicit blocker.

Use this sample repository’s prepared cloud environment. Confirm the working directory, dependency setup, and documented test command. Make no feature changes yet. Report actual setup and check outcomes, required unavailable services, and any secret or network dependency needing review.

Inspect and verify the result

Inspect environment setup output and actual test results. Compare dependency versions with the repo lockfile. Confirm task state comes from the intended environment rather than assuming a recently published setup updated an already-running task.

Limits and troubleshooting

Cloud and local environments can differ in files, network, and services. A build passing in one does not establish production behavior. If setup fails, correct the reproducible environment instead of making undocumented one-off changes.

Data, permissions, and actions

Repository clones, setup logs, outputs, and environment secrets have separate handling. Use least-privilege repo access and narrowly scoped test credentials. Environment capability should not silently include permission to deploy or change live systems.

Reviews and repeatable noninteractive runs

Use a code review or noninteractive task as evidence for a human-controlled change.

Explore Reviews and repeatable noninteractive runs

A scoped repository bug fix

Reproduce a sample defect and hand off a checked diff.

Explore A scoped repository bug fix

A prepared cloud task and review handoff

Run a bounded repository task in a reproducible cloud environment.

Explore A prepared cloud task and review handoff

Permissions and meaningful approvals

Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.

Explore Permissions and meaningful approvals

Sources and verification

Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.

Cloud environments · OpenAI

Get started with Work · OpenAI

Share this page