{"id":3549,"date":"2026-05-20T15:43:26","date_gmt":"2026-05-20T15:43:26","guid":{"rendered":"https:\/\/aiopsschool.com\/blog\/?p=3549"},"modified":"2026-05-20T15:43:28","modified_gmt":"2026-05-20T15:43:28","slug":"codex-how-to-switch-codex-accounts-without-losing-your-session-memory-or-context","status":"publish","type":"post","link":"https:\/\/aiopsschool.com\/blog\/codex-how-to-switch-codex-accounts-without-losing-your-session-memory-or-context\/","title":{"rendered":"Codex: How to Switch Codex Accounts Without Losing Your Session, Memory, or Context"},"content":{"rendered":"\n

Absolutely. Here is a focused blog tutorial just for switching Codex accounts without losing memory, session, or context<\/strong>.<\/p>\n\n\n\n

How to Switch Codex Accounts Without Losing Your Session, Memory, or Context<\/h1>\n\n\n\n

When you use Codex CLI for a long coding task, the session becomes valuable. It contains your prompts, Codex\u2019s reasoning trail, file edits, decisions, approvals, and task history. So when one Codex account hits a usage limit, the obvious panic moment is:<\/p>\n\n\n\n

\n

\u201cIf I logout and login with another account, will I lose everything?\u201d<\/p>\n<\/blockquote>\n\n\n\n

Good news: usually, no<\/strong>. Codex stores your conversation transcripts locally, and you can reopen previous work with codex resume<\/code>. OpenAI\u2019s Codex CLI docs say resumed runs keep the original transcript, plan history, and approvals, so Codex can continue using the previous context after you resume. (OpenAI Developers<\/a>)<\/p>\n\n\n\n

This tutorial shows the safest workflow.<\/p>\n\n\n\n

\n\n\n\n

The idea in simple words<\/h2>\n\n\n\n

Codex has two different things:<\/p>\n\n\n\n

Login\/authentication<\/strong>
This is the account currently paying for or authorizing the Codex run.<\/p>\n\n\n\n

Local session\/context<\/strong>
This is the saved transcript and session history on your machine.<\/p>\n\n\n\n

When you run:<\/p>\n\n\n\n

codex logout\n<\/code><\/pre>\n\n\n\n
Codex removes saved authentication credentials. It does not<\/strong> mean your local session history is automatically deleted. The CLI reference says codex logout<\/code> removes saved credentials, while codex resume<\/code> continues a previous interactive session. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
So the workflow is:<\/p>\n\n\n\n
Save the session ID\nExit Codex\nLogout\nLogin with another account\nResume the old session\nContinue working\n<\/code><\/pre>\n\n\n\n
Tiny goblin rule: do not<\/strong> delete ~\/.codex<\/code> unless you intentionally want to remove local Codex state.<\/p>\n\n\n\n
\n\n\n\n
Recommended title for the blog<\/h2>\n\n\n\n
How to Switch Codex Accounts Without Losing Your Session or Context<\/strong><\/p>\n\n\n\n
Alternative titles:<\/p>\n\n\n\n
    \n
  1. Codex Account Limit Hit? Here\u2019s How to Switch Accounts Safely<\/strong><\/li>\n\n\n\n
  2. How to Resume Codex Work After Logging Into Another Account<\/strong><\/li>\n\n\n\n
  3. Switching Codex Accounts Without Losing Memory: Complete CLI Guide<\/strong><\/li>\n\n\n\n
  4. Codex Resume Explained: Continue Your Work After Logout\/Login<\/strong><\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n
    Before switching: understand what Codex saves locally<\/h2>\n\n\n\n
    Codex stores transcripts locally so you can continue previous sessions instead of re-explaining everything. The docs say codex resume<\/code> lets you reopen earlier threads, and that session IDs can be copied from \/status<\/code>, the resume picker, or files under ~\/.codex\/sessions\/<\/code>. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    Codex also stores memory files under your Codex home directory, which defaults to ~\/.codex<\/code>; memory files live under ~\/.codex\/memories\/<\/code>. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    So the most important folder is:<\/p>\n\n\n\n
    ~\/.codex\n<\/code><\/pre>\n\n\n\n
    It may contain things like:<\/p>\n\n\n\n
    ~\/.codex\/sessions\/\n~\/.codex\/memories\/\n~\/.codex\/config.toml\n~\/.codex\/auth.json\n<\/code><\/pre>\n\n\n\n
    But be careful: auth.json<\/code> contains credentials if file-based credential storage is used. OpenAI says cached login details may be stored in ~\/.codex\/auth.json<\/code> or the OS credential store, and warns that auth.json<\/code> should be treated like a password. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    \n\n\n\n
    Step 1: Check your current Codex session<\/h2>\n\n\n\n
    Inside the active Codex session, run:<\/p>\n\n\n\n
    \/status\n<\/code><\/pre>\n\n\n\n
    The \/status<\/code> command shows session state such as the active model, approval policy, writable roots, current token usage, and session information. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    Copy the session ID if it is shown.<\/p>\n\n\n\n
    You can also later find sessions from:<\/p>\n\n\n\n
    ~\/.codex\/sessions\/\n<\/code><\/pre>\n\n\n\n
    But \/status<\/code> is the cleanest option.<\/p>\n\n\n\n
    \n\n\n\n
    Step 2: Ask Codex to create a handoff file<\/h2>\n\n\n\n
    Before switching accounts, ask Codex to summarize everything into a file inside your repo.<\/p>\n\n\n\n
    Inside Codex, type:<\/p>\n\n\n\n
    Create a file named CODEX_HANDOFF.md summarizing:\n- current goal\n- files changed\n- important decisions made\n- commands already run\n- tests passed or failed\n- remaining TODOs\n- exact next command to continue\n<\/code><\/pre>\n\n\n\n
    This gives you a human-readable backup.<\/p>\n\n\n\n
    Why this matters: even though codex resume<\/code> should preserve context, a handoff file gives you a second safety net. It also helps if you accidentally resume the wrong session, switch machines, or need to continue manually.<\/p>\n\n\n\n
    \n\n\n\n
    Step 3: Save your Git state<\/h2>\n\n\n\n
    In another terminal, from your project folder, run:<\/p>\n\n\n\n
    git status\n<\/code><\/pre>\n\n\n\n
    Then save your current diff:<\/p>\n\n\n\n
    git diff > codex-wip.patch\n<\/code><\/pre>\n\n\n\n
    If you have untracked files, list them:<\/p>\n\n\n\n
    git ls-files --others --exclude-standard\n<\/code><\/pre>\n\n\n\n
    Optionally create a temporary branch:<\/p>\n\n\n\n
    git switch -c codex-account-switch-backup\n<\/code><\/pre>\n\n\n\n
    Then commit the handoff file and current work if appropriate:<\/p>\n\n\n\n
    git add CODEX_HANDOFF.md\ngit commit -m \"docs: add Codex handoff before account switch\"\n<\/code><\/pre>\n\n\n\n
    For unfinished code, you may prefer a stash instead:<\/p>\n\n\n\n
    git stash push -u -m \"codex work before account switch\"\n<\/code><\/pre>\n\n\n\n
    This is not strictly required for Codex context, but it protects the actual code changes. Context without code is like a recipe without ingredients. Sad soup.<\/p>\n\n\n\n
    \n\n\n\n
    Step 4: Exit the current Codex session<\/h2>\n\n\n\n
    Inside Codex, run:<\/p>\n\n\n\n
    \/exit\n<\/code><\/pre>\n\n\n\n
    The docs list \/exit<\/code> as the command to close the interactive session. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    Do not<\/strong> use \/clear<\/code>.<\/p>\n\n\n\n
    \/clear<\/code> starts a fresh conversation in the same CLI session, while Ctrl+L<\/code> only clears the terminal view. The docs specifically say \/clear<\/code> resets the visible transcript and starts a new conversation. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    For account switching, use:<\/p>\n\n\n\n
    \/exit\n<\/code><\/pre>\n\n\n\n
    not:<\/p>\n\n\n\n
    \/clear\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Step 5: Logout from the current account<\/h2>\n\n\n\n
    Now run:<\/p>\n\n\n\n
    codex logout\n<\/code><\/pre>\n\n\n\n
    The CLI reference says codex logout<\/code> removes saved credentials for API key and ChatGPT authentication. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    Again, this is about authentication. Your saved sessions are separate local state.<\/p>\n\n\n\n
    \n\n\n\n
    Step 6: Login with the second account<\/h2>\n\n\n\n
    Now login with the other account:<\/p>\n\n\n\n
    codex login\n<\/code><\/pre>\n\n\n\n
    With no flags, codex login<\/code> opens a browser for ChatGPT OAuth. It can also use device auth, API key, or access token flows. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    If you are on a remote server or headless machine, use:<\/p>\n\n\n\n
    codex login --device-auth\n<\/code><\/pre>\n\n\n\n
    OpenAI\u2019s auth docs recommend device code authentication when browser login is difficult in remote or headless environments. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    You can check whether login worked:<\/p>\n\n\n\n
    codex login status\n<\/code><\/pre>\n\n\n\n
    The CLI reference says codex login status<\/code> prints the active authentication mode and exits successfully when credentials are present. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    \n\n\n\n
    Step 7: Resume your old Codex session<\/h2>\n\n\n\n
    Now resume your previous session.<\/p>\n\n\n\n
    From the same project directory, run:<\/p>\n\n\n\n
    codex resume --last\n<\/code><\/pre>\n\n\n\n
    This resumes the latest session for the current working directory. OpenAI\u2019s docs say codex resume --last<\/code> jumps to the most recent session from the current working directory. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    If you are not in the same directory, use:<\/p>\n\n\n\n
    codex resume --all\n<\/code><\/pre>\n\n\n\n
    The docs say codex resume --all<\/code> shows sessions beyond the current working directory. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    If you copied the exact session ID earlier:<\/p>\n\n\n\n
    codex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    Example:<\/p>\n\n\n\n
    codex resume 7f9f9a2e-1b3c-4c7a-9b0e-123456789abc\n<\/code><\/pre>\n\n\n\n
    That is the most precise option.<\/p>\n\n\n\n
    \n\n\n\n
    Step 8: Confirm Codex still has the context<\/h2>\n\n\n\n
    After resuming, ask Codex:<\/p>\n\n\n\n
    Please summarize the current task, what files were changed, what decisions were made, and what remains to do.\n<\/code><\/pre>\n\n\n\n
    Then compare that with:<\/p>\n\n\n\n
    cat CODEX_HANDOFF.md\n<\/code><\/pre>\n\n\n\n
    Also check the code state:<\/p>\n\n\n\n
    git status\ngit diff --stat\n<\/code><\/pre>\n\n\n\n
    If the summary matches, you\u2019re good.<\/p>\n\n\n\n
    \n\n\n\n
    Complete safe workflow<\/h2>\n\n\n\n
    Here is the full flow from start to finish.<\/p>\n\n\n\n
    Inside Codex<\/h3>\n\n\n\n
    \/status\n<\/code><\/pre>\n\n\n\n
    Copy the session ID.<\/p>\n\n\n\n
    Then ask Codex:<\/p>\n\n\n\n
    Create CODEX_HANDOFF.md with the current goal, changed files, decisions, commands run, test status, TODOs, and exact next step.\n<\/code><\/pre>\n\n\n\n
    Exit:<\/p>\n\n\n\n
    \/exit\n<\/code><\/pre>\n\n\n\n
    In your terminal<\/h3>\n\n\n\n
    git status\ngit diff > codex-wip.patch\n<\/code><\/pre>\n\n\n\n
    Optional:<\/p>\n\n\n\n
    git stash push -u -m \"codex work before account switch\"\n<\/code><\/pre>\n\n\n\n
    Then switch accounts:<\/p>\n\n\n\n
    codex logout\ncodex login\ncodex login status\n<\/code><\/pre>\n\n\n\n
    Resume:<\/p>\n\n\n\n
    codex resume --last\n<\/code><\/pre>\n\n\n\n
    Or, if needed:<\/p>\n\n\n\n
    codex resume --all\n<\/code><\/pre>\n\n\n\n
    Or exact session:<\/p>\n\n\n\n
    codex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    What about Codex memory?<\/h2>\n\n\n\n
    There are three things people often call \u201cmemory\u201d:<\/p>\n\n\n\n
    1. Current session context<\/h3>\n\n\n\n
    This is the active conversation\/thread. Use:<\/p>\n\n\n\n
    codex resume --last\n<\/code><\/pre>\n\n\n\n
    or:<\/p>\n\n\n\n
    codex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    This is the most important thing for continuing an unfinished task.<\/p>\n\n\n\n
    2. Codex memories<\/h3>\n\n\n\n
    Codex memories are stored under ~\/.codex\/memories\/<\/code> by default. OpenAI says memories include summaries, durable entries, recent inputs, and supporting evidence from prior threads. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    Inside Codex, you can configure memory behavior with:<\/p>\n\n\n\n
    \/memories\n<\/code><\/pre>\n\n\n\n
    The slash command docs say \/memories<\/code> lets you choose whether Codex should use existing memories, generate new memories, or keep memory disabled. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    3. Project guidance<\/h3>\n\n\n\n
    This is usually AGENTS.md<\/code>.<\/p>\n\n\n\n
    Codex docs describe AGENTS.md<\/code> as durable project guidance that can include repo layout, test commands, conventions, constraints, and what \u201cdone\u201d means. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    For long-term reliability, add recurring instructions to:<\/p>\n\n\n\n
    AGENTS.md\n<\/code><\/pre>\n\n\n\n
    or globally:<\/p>\n\n\n\n
    ~\/.codex\/AGENTS.md\n<\/code><\/pre>\n\n\n\n
    That way, even if you start a fresh session, Codex can still recover important project rules.<\/p>\n\n\n\n
    \n\n\n\n
    What not to do<\/h2>\n\n\n\n
    Do not delete this folder:<\/p>\n\n\n\n
    ~\/.codex\n<\/code><\/pre>\n\n\n\n
    That may remove sessions, memory files, config, or credentials depending on your setup.<\/p>\n\n\n\n
    Do not run:<\/p>\n\n\n\n
    rm -rf ~\/.codex\n<\/code><\/pre>\n\n\n\n
    unless you intentionally want a hard reset.<\/p>\n\n\n\n
    Do not use \/clear<\/code> before switching accounts, because it starts a fresh conversation. Use \/exit<\/code>.<\/p>\n\n\n\n
    Do not rely only on memory. Always save a handoff file and your Git diff before account switching.<\/p>\n\n\n\n
    \n\n\n\n
    Best practical recommendation<\/h2>\n\n\n\n
    My recommended habit is:<\/p>\n\n\n\n
    Before account switch:\n1. Run \/status\n2. Copy session ID\n3. Create CODEX_HANDOFF.md\n4. Save git diff\n5. Exit\n6. Logout\/login\n7. Resume exact session ID\n<\/code><\/pre>\n\n\n\n
    The golden command is:<\/p>\n\n\n\n
    codex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    The lazy-but-usually-fine command is:<\/p>\n\n\n\n
    codex resume --last\n<\/code><\/pre>\n\n\n\n
    The \u201cI forgot where I was\u201d command is:<\/p>\n\n\n\n
    codex resume --all\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Final cheat sheet<\/h2>\n\n\n\n
    # Inside Codex\n\/status\n<\/code><\/pre>\n\n\n\n
    # Inside Codex\nCreate CODEX_HANDOFF.md summarizing current task, changed files, decisions, test status, TODOs, and next step.\n<\/code><\/pre>\n\n\n\n
    \/exit\n<\/code><\/pre>\n\n\n\n
    # Terminal\ngit status\ngit diff > codex-wip.patch\n<\/code><\/pre>\n\n\n\n
    codex logout\ncodex login\ncodex login status\n<\/code><\/pre>\n\n\n\n
    codex resume --last\n<\/code><\/pre>\n\n\n\n
    codex resume --all\n<\/code><\/pre>\n\n\n\n
    codex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Conclusion<\/h2>\n\n\n\n
    Switching Codex accounts does not have to mean losing your work. Your account login and your local session history are different things. codex logout<\/code> removes credentials, while codex resume<\/code> reopens saved local sessions.<\/p>\n\n\n\n
    For the safest workflow, always capture the session ID with \/status<\/code>, create a CODEX_HANDOFF.md<\/code>, save your Git diff, logout, login with the second account, and resume using codex resume <SESSION_ID><\/code>.<\/p>\n\n\n\n
    That gives you three layers of safety:<\/p>\n\n\n\n
    Codex session resume\nHandoff summary file\nGit diff or stash backup\n<\/code><\/pre>\n\n\n\n
    And that is how you switch Codex accounts without nuking your context like a caffeinated raccoon in a terminal.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Absolutely. Here is a focused blog tutorial just for switching Codex accounts without losing memory, session, or context. How to […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3549","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/3549","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=3549"}],"version-history":[{"count":1,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/3549\/revisions"}],"predecessor-version":[{"id":3550,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/3549\/revisions\/3550"}],"wp:attachment":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=3549"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=3549"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=3549"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}