Configured GROQ_API_KEY secret is not available to Cloud task runtime

What version of the Codex App are you using (From “About Codex” dialog)?

26.715.52143

What subscription do you have?

Pro

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

The Cloud environment aj47/clippy-desktop lists GROQ_API_KEY under Secrets, but a Codex App task using that Cloud environment cannot see it at runtime.

When asked whether it could access the Groq API, the task checked its environment and reported GROQ_API_KEY is not set. This indicates the configured Cloud secret is not being injected into, or is not visible within, the task runtime.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019f82ba-632d-75a1-b6cd-0b8bfed2aa1e

What is the expected behavior?

A task started with the Cloud environment aj47/clippy-desktop should receive the configured GROQ_API_KEY secret at runtime. The task should be able to detect that the variable is present without displaying its value. If the secret cannot be injected, Codex should show a clear configuration or provisioning error.

Additional information

_No response_