Answer: Run `codex migrate-nfs-db` on just one Linux host per shared Codex home, using the home owner's account and usual configuration, after stopping Codex on every host and keeping it stopped until migration finishes. Use a build that includes `codex migrate-nfs-db`, such as Codex CLI 0.166.0. Status: Confirmed Entry: tool/codex/troubleshooting/migrate-nfs-home Revision: 1 Digest: sha256:9483bff8f6b35e4b (changes whenever the content changes) Timeline: Created: 2026-11-13T03:51:09Z Last changed: 2026-11-13T03:51:09Z Last verified: 2026-11-20T13:39:28Z Next check: 2026-11-21T13:39:28Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of migration command | codex migrate-nfs-db | [1] | 2026-11-20 required build | Codex CLI 0.166.0 | [1] | 2026-11-20 hosts to run on | one Linux host per shared Codex home | [1] | 2026-11-20 daemon stop command | codex app-server daemon stop | [1] | 2026-11-20 daemon auto start setting | daemon_auto_start | [1] | 2026-11-20 single session flag | --no-daemon | [1] | 2026-11-20 resume command | codex --no-daemon resume | [1] | 2026-11-20 Sources: [1] OpenAI. "Run Codex with an NFS home directory". https://learn.chatgpt.com/docs/environments/network-file-systems.md Role: primary. Accessed: 2026-11-20T13:39:28Z Quote: "codex migrate-nfs-db" (Supports: migration command) Quote: "such as [Codex CLI 0.166.0]" (Supports: required build) Quote: "Run the migration on just one Linux host per shared Codex home." (Supports: hosts to run on) Quote: "Stop the daemon on each host that runs it with `codex app-server daemon stop`." (Supports: daemon stop command) Quote: "set `daemon_auto_start` to `false` under `[features]` in your shared `config.toml`." (Supports: daemon auto start setting) Quote: "For a single CLI session, pass [`--no-daemon`]" (Supports: single session flag) Quote: "[`codex --no-daemon resume`]" (Supports: resume command) Snapshot SHA-256: 976da29ea746c0cb9a551fae9766821606bc219ad63314345782e50a7e6d0764 (captured 2026-11-13T03:51:09Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:51:09Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:39:28Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:39:28Z Last attempt: 2026-11-20T13:39:28Z Notes and limitations: Extracted automatically from a single official source (section "Migrate an existing NFS home"). Related: https://latestn.com/tool/codex/troubleshooting/report-issues-request-features Where do I report issues or request features for Codex? https://latestn.com/tool/codex/troubleshooting/resume-bulk-scan-campaign How do I resume or retry a Codex Security bulk scan campaign after it is interrupted? https://latestn.com/tool/codex/troubleshooting/security-plugin-disabled-by-admin How do I fix a Codex Security plugin that shows 'Disabled by admin' in a managed workspace? https://latestn.com/tool/codex/troubleshooting/headless-login How do I sign in to Codex on a headless device? https://latestn.com/tool/codex/troubleshooting/host-not-visible-on-phone Why don't I see my host on my phone in Codex remote connections, and how do I fix it? https://latestn.com/tool/codex/troubleshooting/large-repos-slow-in-wsl Why do large repositories feel slow in WSL when using Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:51:09Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/troubleshooting/migrate-nfs-home/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/troubleshooting/migrate-nfs-home POST: https://latestn.com/dispute/tool/codex/troubleshooting/migrate-nfs-home with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/troubleshooting/migrate-nfs-home?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate an existing Codex home directory on NFS to avoid SQLite corruption? Revision 1, last verified 2026-11-20T13:39:28Z. https://latestn.com/tool/codex/troubleshooting/migrate-nfs-home (accessed 2026-11-21T10:01:29Z). @misc{LatestN_tool_codex_troubleshooting_migrate_nfs_home_r1, title = {How do I migrate an existing Codex home directory on NFS to avoid SQLite corruption?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/troubleshooting/migrate-nfs-home}}, note = {Revision 1; digest sha256:9483bff8f6b35e4b; last verified 2026-11-20T13:39:28Z; accessed 2026-11-21T10:01:29Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/troubleshooting/migrate-nfs-home