You're working across two projects and open the Verboo Code session picker, only to find yesterday's conversation in the other repo missing from the list. It didn't disappear: /resume only shows sessions from the current project by default, and switching projects without losing context takes two extra steps.
Why doesn't /resume show sessions from other projects?
Because by default the picker filters by the directory you ran the CLI from: only sessions from the current project and its worktrees show up (copies of the same repository created with git worktree, which Verboo Code recognizes as the same project living in a different folder). That keeps the list from turning into noise with dozens of unrelated projects every time you just want to continue what you were doing right there.
How do you see sessions from every project, not just the current one?
Inside the picker (/resume with no argument), press Ctrl+A. It toggles to list sessions from any project on the machine, and shows each project's path next to its title so you can tell them apart.
Other shortcuts in the same picker, verified in src/components/LogSelector.tsx:
Ctrl+Atoggles between the current project and every projectCtrl+Wfilters by worktree, when the repo has more than oneCtrl+Bfilters by branch
What happens when you pick a session from another project?
Depends on which "other project" it is.
If it's a worktree of the same repository, the session resumes right away, nothing else needed: Verboo Code recognizes it as the same project, just living in a different folder.
If it's a genuinely different project, it won't switch directories on its own, because the running process is already inside the current directory and can't move mid-execution. Instead of trying, it builds the right command and copies it to your clipboard:
This conversation is from a different directory.
To resume, run:
cd /path/to/project && verboo --resume <session-id>
(Command copied to clipboard)Paste and run. No manual step to find the session ID or the project path: both already come filled in.
Can you skip the picker and resume straight from the terminal?
You can. Two flags cover the common cases:
verboo --resume <session-id>
verboo -r <session-id>Resumes a specific session with no picker at all, straight from the terminal, from inside the right folder.
verboo --continue
verboo -cResumes the most recent session in the current folder, no picking required.
If you want to keep the original session intact and open a copy under a new ID instead of continuing to overwrite the same one, add --fork-session to either.
Gotcha: --resume <id> and --continue operate on the session saved in the directory you run the command from. If you paste the command the CLI copied but skip the cd in front of it, it looks in the wrong directory and finds nothing. The copied command already has that cd built in for exactly this reason: don't strip it.
Switching sessions between projects, testing again, opening a third one to compare: each resume is a full session running again, with the whole history reread by the model. On Verboo Code that never turns into a cost decision, because every plan runs on unlimited tokens. There's no reason to avoid opening one more session just because the bill might close higher at the end of the month.
