Many people still haven’t realized what the “permanent cache” introduced by Codex and Work actually means.
For most APIs, the Prompt Cache lifecycle is limited to around 12 hours. Once that window expires, the cache automatically becomes invalid and all state is cleared.
But Codex and Work have gone beyond the usual API model: by deeply tying the cache to the logged-in user, they’re making it persist permanently across sessions and cycles.
For most APIs, the Prompt Cache lifecycle is limited to around 12 hours. Once that window expires, the cache automatically becomes invalid and all state is cleared.
But Codex and Work have gone beyond the usual API model: by deeply tying the cache to the logged-in user, they’re making it persist permanently across sessions and cycles.