---
title: "Comment by OnlineProxy on \"[CLI] Multiple Codex (ChatGPT) accounts on one machine\" | Hashnode"
description: "WAL does stop corruption, but codex's lock handling is the shaky part, since it sets busy_timeout to 5000 and doesn't retry SQLITE_BUSY. issues 20213 and 35555"
url: "https://hashnode.com/posts/cli-multiple-codex-chatgpt-accounts-on-one-machine/6ac2931a73f4e91095662fe0/comment/6ac941103b027169609627c2"
---

[Discussion](https://hashnode.com/posts/cli-multiple-codex-chatgpt-accounts-on-one-machine/6ac2931a73f4e91095662fe0)

Comment [\[CLI\] Multiple Codex (ChatGPT) accounts on one machine](https://hashnode.com/posts/cli-multiple-codex-chatgpt-accounts-on-one-machine/6ac2931a73f4e91095662fe0)

[OnlineProxy](https://hashnode.com/@onlineproxyio)

[Oct 9](https://hashnode.com/posts/cli-multiple-codex-chatgpt-accounts-on-one-machine/6ac2931a73f4e91095662fe0/comment/6ac941103b027169609627c2)

WAL does stop corruption, but codex's lock handling is the shaky part, since it sets busy\_timeout to 5000 and doesn't retry SQLITE\_BUSY. issues 20213 and 35555 seem to show that under concurrent use, and 35555 was still open as of august. the journal\_mode stall in 35704 only involves one process, so I'd treat it as a side note

unquoting the pattern inside excluded should make state\_\*.sqlite match and survive schema bumps, so test that on a scratch copy first. keep each DB with its wal and shm files in the same folder. and check with sqlite3 whether unified history is in state\_5.sqlite, because if it is, excluding the DBs loses most of the benefit

[Sanghun Kang](https://hashnode.com/@sanghunkang)

[Oct 10](https://hashnode.com/posts/cli-multiple-codex-chatgpt-accounts-on-one-machine/6ac2931a73f4e91095662fe0/comment/6ac941103b027169609627c2#reply-6ac9e1e2f21e51700d1f1ddf)

Thanks, you're right. WAL supports concurrent access, but depending on how Codex handles locking, running multiple instances at the same time can lead to startup failures or temporary hangs.

In my case, I switch to another account when one runs out of usage. Since I don't run both instances at the same time, I haven't encountered these issues so far. They could occur if you run both simultaneously.

I've updated the post to clarify this. Thanks for pointing it out!
