Use memory in Rovo Dev CLI

Rovo Dev CLI uses memory to retain important information about your project and preferences.

This might include project-specific context, coding standards, architectural decisions, frequently used patterns or code snippets, external dependencies and their versions, or information about development workflow and best practices. Rovo Dev uses this information to customize its responses and the code it generates.

User memory is stored in ~/.rovodev/AGENTS.md. User memory applies to all your Rovo Dev CLI sessions.

Project memory is stored in AGENTS.md and AGENTS.local.md in your workspace directories. Project memory is specific to directories you work in.

Memory files are written in markdown.

Commands

Manage memory while in interactive mode.

/memory - edit the current directory’s memory file.

/memory user - edit your user memory file.

/memory init - Rovo Dev analyzes the current project and generates content for your project file.

Memory file priority

Rovo Dev prioritizes memory files in this order:

1. User memory files in ~/.rovodev.

2. Project memory files in the current working directory.

3. Project memory files in parent directories (directories closer to the working directory are higher priority).

Writing memories

When writing memories, remember Rovo Dev can adopt concrete examples and specific patterns more effectively than general advice. Use headings and structured information make it easier for Rovo Dev to find and apply memories.

We encourage you to explore different uses for memory to improve and streamline your workflow. For user memories:

• Store your general coding preferences and style guidelines.

• Include frequently used code snippets or templates.

• Document your preferred project structures and naming conventions.

• Note any global tools or utilities you commonly use.

For project memories:

• Document unusual project setup or configuration requirements Rovo Dev will need to work with.

• Note temporary workarounds or technical debt that needs to be addressed in the directory.

• Describe the testing strategy and important test patterns.

Memory initialization

The /memory init command analyzes your workspace and creates a comprehensive memory file, including:

• Detected language, frameworks, and technologies.

• Key configuration files, entry points, and directories.

• Observed patterns in code structure, naming, and organization.

• Inferred best practices from existing code patterns.

This information can be especially useful for new team members or when starting on a new project.

Legacy file support

Rovo Dev provides migration support for several legacy memory file formats:

• CLAUDE.md, CLAUDE.local.md

• codex.md, .codex/*.md

• .cursor/rules/*.mdc, .cursorrules.md, .cursorrules

• rules.md, .rules.md

• .agent.md, .agent.local.md

When using /memory init, content from legacy files will be migrated to the AGENTS.md format.