Cache on Cloud is not properly working
Resolved 💬 6 comments Opened Oct 7, 2025 by fpalumbo-gpicd Closed Oct 11, 2025
What version of Codex is running?
Codex Cloud
Which model were you using?
_No response_
What platform is your computer?
Ubuntu
What steps can reproduce the bug?
Every time I run a prompt, the machine re-executes the full setup instead of using the cached environment. Setup is executed on every run, causing slow start times and unnecessary resource usage.
What is the expected behavior?
If I run a task without any setup configuration changes and less than 12 hours have passed since the last task, the environment should run the maintenance script only (reuse cache) rather than executing the full setup.
What do you see instead?
the setup is loaded (with all the installations)
Additional information
i'm using poetry with python to manage requirements
6 Comments
I managed to change the path where to save the environments, but the lack of documentation made it difficult. It seems to be working now
@fpalumbo-gpicd - can you share details to help users who find this post resolve the same issue? What path did you use to cache that persisted between runs?
no, you don't need that, the cache works in an upper lever, is the image of the container that is cached
@fpalumbo-gpicd , but how did you get it working?
I have this exact issue and it makes codex cloud useless to me, as I have to wait 10 minutes for a response to every message.
First, I added a counter to know exactly the time for each step in the setup. Than I did some tricks to decrease the time but depends the installs you may need, ask some Chatgpt how to improve. 10 minutes of startup time is too much
but how did you get it to start caching? we have the same issue