Cloud Codex web container creation and removal

Open 💬 1 comment Opened May 22, 2026 by Ravanloft

What issue are you seeing?

I’ve been developing a project on GitHub in my spare time and using Codex Cloud for the workflow. However, starting yesterday, the web cloud agent no longer keeps the container environment alive and immediately deletes it, or does not continue from the existing session.

Now, every time I send a message in the chat, it creates a brand-new container from scratch. After the response is generated, the container is terminated immediately.

Previously, the container/session would usually stay active for around 10–15 minutes, which allowed me to continue working in the same environment, but this behavior has suddenly changed.

What steps can reproduce the bug?

Just sending a prompt in the chat is enough to trigger it.

What is the expected behavior?

For tasks to be completed properly, the container should remain active for at least 10, 15, or ideally 30 minutes. Additionally, whenever the same session is continued, the lifetime of the existing container should be extended instead of creating a new container from scratch.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗