The session just fixed a nasty bug, and you want to keep the reasoning: paste it into the PR, send it to a teammate, attach it to the ticket. Selecting the terminal with the mouse cuts lines, grabs box borders and loses the start of the conversation. Verboo Code's /export pulls out the whole conversation at once, as plain text, to a file or to the clipboard.
What does /export do in Verboo Code?
It turns the current conversation into plain text and delivers it in one of two ways: copies it to the clipboard or writes a .txt file in the folder where the session is running. The text is the same one you see on screen, rendered by the CLI itself, with terminal colors stripped.
How do you export the conversation, step by step?
Inside the session, type:
/exportThe Export Conversation menu opens with two options:
Copy to clipboard: copies the conversation and closes the menu withConversation copied to clipboard.Save to file: asks for a file name, prefilled with a suggestion. Press Enter to save, or Esc to go back to the menu.
If you already know the name, pass it directly and the menu never opens:
/export login-bug-session.txtThe CLI replies with Conversation exported to: followed by the full path of the file.
What name and extension does the file get?
Always .txt, in the session's current folder. If you type another extension, the CLI replaces it with .txt. If you type nothing, the suggestion is the date and time plus the start of your first message.
| You type | File written |
|---|---|
/export session | session.txt |
/export session.md | session.txt (the extension is replaced) |
/export docs/session.txt | docs/session.txt, if the docs folder already exists |
/export then Save to file | 2026-10-16-093015-fix-the-login-test.txt (editable suggestion) |
The suggestion uses only the first line of the first message, up to about 50 characters, lowercased, with spaces turned into hyphens. Accents and special characters are dropped: "Corrija a função" becomes corrija-a-funo. If nothing is left, the name is conversation- plus the date and time.
Gotcha: the file lands in the project folder. /export writes to the session's current directory, which is almost always the root of your repository. A careless git add . commits the whole conversation along with the code, including log snippets, machine paths or keys that showed up along the way. Export to an ignored folder or move the file right after:
echo "*.txt" >> .git/info/exclude
# or export to a folder already covered by .gitignore
/export tmp/login-bug-session.txt.git/info/exclude works like a local .gitignore that never goes into the repository.
Why did "Copy to clipboard" paste nothing?
Because how the copy works depends on where the CLI is running. Locally, it calls the system tool. Over SSH or inside tmux, it relies on the terminal accepting the OSC 52 sequence, and some terminals ship with that turned off.
| Where Verboo Code runs | How it copies | If nothing pastes |
|---|---|---|
| Local macOS | pbcopy | Rarely fails |
| Local Linux | wl-copy, xclip or xsel, whichever exists first | Install one of them, for example sudo apt install xclip |
| Windows | PowerShell Set-Clipboard | Rarely fails |
| Server over SSH | OSC 52 sequence sent to your terminal | Enable OSC 52 in the terminal (off by default in iTerm2) or use Save to file |
| Inside tmux | tmux load-buffer | Paste with prefix + ], or set set -g allow-passthrough on in ~/.tmux.conf |
On a remote server, the most reliable path is to save to a file and download it:
scp user@server:~/my-project/login-bug-session.txt ./export or the raw session file?
/export is for people to read. For scripts, use the session file: each conversation is stored as <session-id>.jsonl inside ~/.claude/projects/, or under VERBOO_PROJECTS_DIR if you set that variable.
| You want to | Use |
|---|---|
| Paste the conversation into a PR, ticket or message | /export then Copy to clipboard |
| Keep the history of a fixed bug | /export login-bug.txt |
Process the conversation with jq or another script | The session's .jsonl |
| Continue the conversation later | Nothing to export: /resume picks the session back up |
A session worth exporting is usually a long one, with the agent rereading the whole project on every reply. With Verboo Code the plans run with unlimited tokens, so the conversation can go on until the bug is closed, and /export keeps the whole path.
