Codex CLI, hosted
OpenAI Codex CLI in a persistent cloud container
Codex runs in your ZeroLog container, signed in with your own account. The container keeps your repository, build tools and caches between sessions, so each run starts where the last one stopped.
# in the container terminal, inside your project $ cd ~/project $ codex # the container keeps these between sessions ~/project node_modules .cache
What you get
- A container that stays
Files persist across restarts and across chats. Several chats can attach to the same container and share one filesystem. You can install anything apt provides, compile code and run services.
- Your own account
Sign Codex in under Settings, AI accounts, with the same flow as Claude Code: the CLI prints a URL, you open it and paste the code back. The vendor bills you on your subscription. This works from the Mini plan.
- Or your OpenAI API key
Store a key under Settings, Provider keys, and an agent in your container can use it. The request goes to OpenAI under your own contract, and ZeroLog adds no margin.
- Or a catalogue model
Codex can also use a model from the ZeroLog catalogue. Then requests count against your ZeroLog credit and limits.
Running it unattended
- Goals and jobs
A /goal run continues on the server when you close the tab, within the time limit of your plan: 4 hours on Mini, 8 on Pro, 12 on Max, none on Ultra. Every long run gets an entry under Jobs with its log, readable live or afterwards.
- Step in by hand
The terminal opens in the same container while the agent works. Fix one thing yourself and hand it back.
- Limits stay the vendor's
On your own subscription the vendor's limits apply unchanged. ZeroLog does not raise them or reroute a request that hit one.
ZeroLog is an independent service. It is not affiliated with, endorsed by or sponsored by OpenAI. OpenAI, ChatGPT and Codex are trademarks of OpenAI.
Where prompts go
With your own account or key, prompts go to the vendor. With a catalogue model, they go to ZeroLog's model provider, Featherless in the USA. The container and its disk are stored in Switzerland. The trust page lists every recipient.
Details: Claude Code and other CLIs, Your own vendor subscription, Trust and security.
Set up Codex
- Create a container.
Any plan from Mini has one. Attach it to a chat.
- Sign Codex in.
Settings, AI accounts, start the Codex sign-in, open the URL, paste the code back.
- Start it in your project.
cd ~/project && codex
- Hand it a task and leave.
Start long work as /goal or a job and read the log under Jobs later.
Questions
- Can Codex keep working after I close the browser?
A /goal run or job can. They run on the server, and the log stays under Jobs. Idle containers can be paused, so do not rely on an open terminal alone.
- Do I need an OpenAI subscription?
You need one of three things: your own account, your own API key, or ZeroLog credit for a catalogue model.
- Are my files kept between runs?
Yes. The container is the durable part. You can also take snapshots, as many as your plan allows.
- Is this an OpenAI product?
No. ZeroLog is independent and not affiliated with OpenAI.
Keep reading
- Swiss AI workspace
Chat with many models and a Linux container in one account.
- Use your own Claude or ChatGPT subscription
Claude Code and Codex on the plan you already pay for.
- Cloud development environment in Switzerland
Where your files, your container and the model calls live.
- Claude Code in the cloud
Your own Claude account, signed in inside a container.
- AI coding agent with a persistent workspace
Files, snapshots, jobs and schedules that outlast a chat.
- Open-source models for your coding agent
The catalogue, how credit pays for it, and your own key.
- ZeroLog Code
Your workspace, in your terminal.
- ZeroLog Extension
Your chat in the side panel of Chrome and Firefox.
Give Codex a container of its own
Ask for access and bring your own account.