Manage sessions in Rovo Dev CLI

Sessions in Rovo Dev CLI let you continue from where you left off by maintaining conversation history and context across multiple interactions.

Each session maintains its own message history and conversation context, and are tied to specific workspaces. Each workspace maintains its own set of sessions, and sessions created in a workspace are only visible when working in that workspace.

Commands

Session menu

/sessions - Open the interactive session menu to view, switch, and manage sessions.

The sessions menu shows all sessions for the current workspace, sorted by last activity. It displays message count, creation date, token usage, and a conversation preview.

Session menu hotkeys

↑ ↓ - Navigate between sessions.

Enter - Switch to selected session.

n - Create a new session.

f - Fork the selected session.

d - Delete the selected session (with confirmation).

q - Quit without making changes.

Create new session

/sessions new - Create a new session with default title.

/sessions new [title] - Create a new session with custom title.

Fork session

/sessions fork - Fork the current session with default title.

/sessions fork [title] - Fork the current session with custom title.

When you fork a session, it creates a parent-child relationship and forked sessions show as nested under their parent in the session list. Deleting a parent session doesn't affect its children.

Rename session

/sessions rename [title] - Rename the current session.

/sessions rename [current_title] [new_title] - Rename a specific session.

Default titles are created based on conversation content.

Manage history

/clear - Clear the current session's message history (cannot be undone).

/prune - Reduce token size while retaining context (removes tool results).

Storage

Sessions are stored by default at ~/.rovodev/sessions/:

• session_context.json: full conversation history and context.

• metadata.json: session metadata like title, workspace, and fork information.

Restoring a session

To start Rovo Dev CLI and restore the last session in the current working directory, run:

You can also enable sessions.auto_restore in your configuration file (stored by default at ~/.rovodev/config.yml) to automatically restore the last session when you run Rovo Dev CLI.

Tips for working with sessions

• Start a new session for each distinct coding task or feature.

• Fork sessions when trying different approaches to the same problem.

• Use custom titles to help identify sessions quickly.

• Sessions with extensive history may load more slowly.

• Monitor context usage to avoid hitting context limits and use the /prune command.