A feature gate in Codex build 9922 hides a cloud runner that drafts its own environment

The sequence in build 9922 is short and ordered. You select repositories and ask for a private environment ^[8]. An onboarding flag tells the server to start an environment-setup conversation, and the server can answer with an environment ID, a conversation thread and an onboarding skill ^[8][9]. Codex then inspects the repositories you picked and prepares an environment draft for a developer to review ^[10].

The default network policy in that new environment is restricted to package-manager access ^[8]. Reach beyond it comes from the Tailscale authentication keys, and access to cloud resources from the OpenID Connect identities ^[11].

Twenty-three of the 31 cloudThreadPrototype references are new since build 9275, close to a fourfold increase ^[6][7]. A string count is a weak signal about intent and a fair one about how much code moved, and the rest of the evidence is the same kind: RuntimeWire compared client code and interface wiring in the two builds, including labels, feature gates, state handling, API schemas and configuration panels ^[20]. The gated code is already inside a production build users have installed ^[1]. RuntimeWire says the client alone cannot establish whether any supporting backend is available ^[13], and that the code establishes active development, not public availability or launch timing ^[3].

The shipped service asks the customer to author the environment. OpenAI's public Codex Cloud documentation still tells developers to connect a source repository, create an environment manually, and configure its dependencies, tools, variables and secrets before starting a task ^[14]. In the gated path the agent writes the draft and a developer signs it off ^[10]. For that swap to be worth taking, the approval screen has to tell the reviewer which network policy and which identity bindings the agent asked for. RuntimeWire's account describes the draft going to review and does not detail that screen ^[10].

Before I enabled gate 375130565 in a tenant that owns real repositories ^[3], I would want two properties written down: a tailnet key scoped to the single node and route the environment needs, and a cloud identity bound to a subject the environment itself cannot rewrite. Azure is the identity path furthest along in this client build, so an AWS or Google Cloud shop is looking at less finished plumbing ^[12]. The existing Codex Cloud service remains available, and RuntimeWire says it found nothing showing whether or when users would move to the new path ^[15].