Resume a Codex CLI Session on Lumecoder
Reopen the last chat; keep billing on your Lumecoder account
Finish the install guide first. resume only brings the old chat back. New work uses your Lumecoder points.
Confirm you are still on Lumecoder
Run this from the repository where the session started.
- The install-guide files are still in place
- codex resume --last opens the newest chat in this directory
- codex resume opens the picker; or type /resume inside the app
- New replies still use Lumecoder points
There is no -l short flag. If the config was changed, restore the install-guide files before a long task.
About points
The chat history stays on this computer. Opening it is not a separate fee. The next time it writes code, points come out of the wallet. Models and prices follow the console.
--last follows the current directory
Official docs: codex resume scopes --last to the current working directory unless you pass --all. Non-interactive sessions from codex exec stay hidden unless you add --include-non-interactive.
Commands
| Command | What it does |
|---|---|
| codex resume --last | Skip the picker; open the newest session in this directory |
| codex resume | Open the session picker |
| codex resume <SESSION> | Open by UUID or name; UUID wins if both match |
| codex resume --all | List sessions across directories |
| codex resume --last "keep going" | Resume and send a follow-up prompt |
| codex fork --last | Copy the newest session into a new chat |
| codex exec resume --last | Continue in non-interactive mode |
codex resume --last codex resume codex resume --all
Inside an open session
- /resume: pick a saved chat and reload its transcript
- /rename: give the current chat a name you can find later
- /new: start a fresh chat without leaving the CLI process
- /archive: archive and exit; the transcript stays, it just leaves the active list
- /delete: permanently delete the current session transcript
Archive and delete from the terminal
Session IDs take precedence over names. Deleting a name still asks for confirmation. --force is only for a session UUID.
codex archive <SESSION> codex unarchive <SESSION> codex delete <SESSION> codex delete <SESSION_UUID> --force
What resume does not do
- It does not change repositories for you. cd back, or pass --all
- It is not the usage table in the Lumecoder console
- If the config was overwritten, it will not put Lumecoder back. Use the install guide first
FAQ
Does resume charge again?
Opening history is not a separate fee. New work uses points.
Why did --last open the wrong chat?
You probably changed directories. --last is tied to the current working directory. Add --all, or cd back.
How do I find a codex exec run?
Those sessions are excluded by default. Add --include-non-interactive, or use codex exec resume --last.
You have not finished the install guide?
Do that first. Resume after a normal chat works.