You started a task in the Codex CLI, but want to finish it in Verboo Code without retyping the context from scratch. Up to version 0.15.29, the only way was to copy pieces by hand or re-explain the history to the agent. In v0.15.30, /resume started seeing Codex sessions directly.
Can I open a session I started in the Codex CLI inside Verboo Code?
Yes, since v0.15.30. Verboo Code's /resume lists the sessions saved in ~/.codex/sessions alongside native sessions, and when you pick one, it converts the history to native format on the spot, no exporting or pasting required.
How to do it
Go into the same directory where the Codex session was created and open Verboo Code as usual:
cd ~/projects/my-app
verbooInside the session, type:
/resumeThe list mixes native sessions with Codex sessions. Codex ones show up with the title Codex already gave them (read from ~/.codex/session_index.jsonl), or with (codex) when there's no title. Pick the session and hit Enter: Verboo Code converts the Codex rollout to native format and resumes the conversation normally, with the message history and tool calls preserved.
The match is by directory: Verboo Code only lists Codex sessions whose saved cwd matches your current directory (or a worktree of the same repository). Change folders and the session won't show up.
What survives the conversion, and what doesn't
A Codex rollout is a raw log with event types that don't exist in Verboo Code's format. The conversion maps what can be mapped and drops the rest:
| Event in the Codex rollout | What it becomes in Verboo Code |
|---|---|
| User message | User message |
| Assistant reply | Assistant reply |
function_call / custom_tool_call | Tool call |
| Tool result | Tool result |
compacted (Codex already summarized the history) | Drops everything before it and restarts from the summary, same logic Codex itself uses |
| Reasoning, token usage, internal state | Dropped |
Two things the conversion doesn't do
- It doesn't sync again. The conversion only happens the first time you pick that session: Verboo Code writes a local copy, and if you come back and select the same session later, it reuses the already-converted file instead of re-reading the rollout. If you keep working on it in the Codex CLI after importing, the new Codex turns won't show up in Verboo Code. The original rollout isn't touched, so
codex resumekeeps working normally, just as a separate timeline. - It doesn't bring the internal reasoning. Codex writes encrypted
reasoningblocks into the rollout; the conversion drops that event type and keeps only the final text the assistant replied with. If you relied on Codex's "thinking out loud" to understand a decision, that part doesn't carry over.
A shortcut: --continue skips the picker
If you already know you want the most recent conversation in that directory, you don't need to open the picker:
verboo --continueThis resumes the most recent session in the current directory directly. If the newest one there was a Codex CLI session, that's the one that loads, converted on the spot, the same way as through /resume.
Switching tools mid-task shouldn't cost you the context you already built. In Verboo Code, on top of the history coming in without friction, the tokens to finish that task are unlimited: the session you just imported doesn't cost more to continue than a brand new conversation.
