You open /resume and find a list of sessions that all start with "fix", "look at this error" or "continue". Which one was the OAuth login? /rename solves that: it gives the current Verboo Code session a name, and from then on you get back to it by typing the name instead of hunting through the list.
What does /rename do?
It saves a name for the current session. That name shows up in the /resume picker, in /status, in the prompt bar and in the resume command the CLI prints when you exit.
/rename login-oauthThe reply is:
Session renamed to: login-oauthThe name you type is saved as is, only trimmed at the ends. It can contain spaces (/rename login with oauth), but a name without spaces is easier to type in the terminal later.
What if I run /rename without a name?
Verboo Code reads the conversation and suggests a short kebab-case name of 2 to 4 words, such as fix-login-bug or refactor-api-client. Since version 0.15.40 this suggestion uses the catalog's fast model when one is available.
/renameTwo messages can show up instead of a name:
| Message | Why | What to do |
|---|---|---|
Could not generate a name: no conversation context yet. Usage: /rename <name> | The session has no conversation to summarize yet | Send your first request first, or pass the name yourself |
Could not generate a name: the model request failed. Try again or use /rename <name> | The model call failed | Run it again or type the name |
The second message is new in 0.15.40. Before that, a model failure looked as if the session had no context.
How do I resume a session by name?
From the terminal, with --resume and the name:
verboo --resume login-oauthYou don't even need to remember it: when you exit a named session, the CLI prints the ready-made command, already quoted:
Resume this session with:
verboo --resume "login-oauth"An unnamed session prints the same hint with its ID (a UUID), which nobody remembers. That is the practical difference /rename makes.
Inside an open session, the equivalent is:
/resume login-oauthWhen you type /resume followed by a space and part of the name, the CLI suggests up to 10 sessions whose name contains what you typed, newest first.
How is the name matched?
By exact match, case insensitive. Login-OAuth finds login-oauth, but login alone does not. What happens in each case:
| Situation | verboo --resume name | /resume name |
|---|---|---|
| One matching name | Resumes the session directly | Resumes the session directly |
| No matching name | Opens the picker with name already in the search | Session name was not found. |
| Two or more sessions with the same name | Opens the picker with name already in the search | Found 2 sessions matching name. Please use /resume to pick a specific session. |
That is why one name per task pays off. If you call every bug-fixing session bug, the direct resume never happens.
Gotcha: the name lookup searches the sessions of the repository you are in, including its worktrees. Running verboo --resume login-oauth from another folder won't find the session and falls back to the picker. Go back to the project folder or, in the picker, press Ctrl+A to see all projects. Resuming a session from another project has its own path, covered in how to resume a session opened in another project.
Can I name the session when I open it?
Yes, with -n or --name:
verboo -n login-oauthThe name shows up in /resume and in the terminal window title, and it is written to the session file along with the first message you send. Handy if you open one session per task and already know the name before you start.
How do I rename an old session without opening it?
From the /resume picker. Select the session with the arrow keys and press Ctrl+R. Rename session: appears, you type the new name and confirm with Enter (or cancel with Esc). The picker has more shortcuts that help you find the session before renaming:
| Shortcut | What it does |
|---|---|
Ctrl+R | Renames the selected session |
Ctrl+V | Shows a preview of the conversation |
Ctrl+A | Toggles between the current folder and all projects |
Ctrl+B | Filters by the current git branch |
| typing | Searches the name, summary, first request and branch |
Does the session get a title on its own?
It does. Since 0.15.40, Verboo Code generates a session title in the background and shows it in /resume. In 0.15.41 the title started coming out in the language of the conversation. If generation fails, the title becomes your first request.
/rename still wins: the code stores both in separate fields and, when reading, the name you chose always beats the automatic title. To resume by name with --resume without surprises, use a name you picked yourself.
If you use CLAUDE_CODE_DISABLE_TERMINAL_TITLE to keep the terminal window title untouched, note that since 0.15.41 that variable does only that. The session still gets a title in /resume.
Where else does the name show up?
/status: theSession nameline. Without a name it shows the hint/rename to add a name.- Status line: the JSON your script receives includes the
session_namefield when the session has a name. You can show the task name under the prompt, as in the status line with /statusline tutorial. - Prompt bar: the name stays visible in the session while you work.
How do I use /rename day to day?
A flow that works well with /clear, which clears the context but does not delete the previous session:
/rename login-oauth # name the current session before switching topics
/clear # start a clean conversation for the next task
/resume login-oauth # go back to the login work when you need itTo fork a conversation and try another path without losing the original, the command is a different one: /branch. Give the two ends different names and /resume stays readable.
A named session is one you pick up the next day without explaining the problem to the agent again. To work like that, across as many sessions as you need, create your account at Verboo Code and run /rename in the first one.
Behavior verified in the Verboo Code source (verbeux-ai/code, v0.15.41) on 2026-11-02: src/commands/rename, src/commands/resume, src/components/LogSelector.tsx, src/utils/gracefulShutdown.ts and src/main.tsx.
