Manage Rovo Dev CLI settings

Rovo Dev CLI configuration file contains multiple parameters

The Rovo Dev CLI configuration file is stored by default at ~/.rovodev/config.yml. Change settings in this file to customize Rovo Dev CLI to suit your preferences and workflow.

To edit the file in your default editor, run:

acli rovodev config

Configuration options

The configuration file uses YAML format with a hierarchical structure. All configuration parameters are optional, Rovo Dev will use sensible defaults if a parameter is not specified.

Rovo Dev behaviour

Settings to control how Rovo Dev responds to you.

agent:
  # Additional system prompt to append to the agent's default system prompt
  additionalSystemPrompt: "Always prioritize code readability and maintainability."

  # Enable streaming responses from the AI model (default: true)
  streaming: true

  # Temperature setting for AI model responses (0.0-1.0, default: 0.3)
  temperature: 0.3

  # Model ID to use for the agent (default: "auto")
  modelId: "auto"

  # Enable the deep planning tool for complex task planning (default: false)
  enableDeepPlanTool: false

  experimental:
    # Enable task delegation to sub-agents (internal users only)
    enableDelegationTool: false

    # Enable shadow mode - run on temporary workspace clone (default: false)
    enableShadowMode: false

    # Disable built-in Atlassian MCP server (internal users only)
    disableBuiltinAtlassianMcp: false

Sessions

sessions:
  # Automatically restore the last active session on startup (default: false)
  autoRestore: false

  # Directory where session data is stored (default: ~/.rovodev/sessions)
  persistenceDir: "~/.rovodev/sessions"

Atlassian connections

Settings to control context Rovo Dev uses from Atlassian apps.

atlassianConnections:
  # Global Jira projects user is part of
  jiraProjects:
    - url: "https://yoursite.atlassian.net/browse/PROJ"
      key: "PROJ"
      name: "Your Project"

  # Directory where local overrides are stored
  localOverridePath: "~/.rovodev/atlassian_local_overrides"

  # Whether Atlassian integration is enabled (default: true)
  enabled: true

Console

Settings to control how Rovo Dev CLI displays information and handles input.

console:
  # Output format for console display (default: "markdown")
  # Options: "markdown", "simple", "raw"
  outputFormat: "markdown"

  # Show tool execution results in the console (default: true)
  showToolResults: true

  # Editing mode for the prompt session (default: "EMACS")
  # Options: "EMACS", "VI"
  editingMode: "EMACS"

  # Maximum width of console output in characters, or "fill" (default: 120)
  maxOutputWidth: 120

Logging

logging:
  # Path to the log file (default: ~/.rovodev/logs/rovodev.log)
  path: "~/.rovodev/logs/rovodev.log"

  # Enable collection of prompts for debugging (internal users only)
  enablePromptCollection: false

MCP (Model Context Protocol)

Configure MCP server connections. When connected to a third-party data source, you are responsible for obtaining the necessary rights, consents, and authorizations for Atlassian to use this data, and for following any terms and policies about the use of data from third-party products. More about Rovo Dev and MCP

mcp:
  # Path to the MCP configuration file (default: ~/.rovodev/mcp_config.json)
  mcpConfigPath: "~/.rovodev/mcp_config.json"

  # List of allowed MCP server names
  allowedMcpServers: []

  # List of globally disabled MCP server signatures
  disabledMcpServers: []

Tools

Control which tools can be used, and whether you are prompted before they are used.

toolPermissions:
  # Default permission for tools not explicitly listed (default: "ask")
  # Options: "allow", "ask", "deny"
  default: "ask"

  # Permission settings for specific tools
  tools:
    # File operations
    create_file: "ask"
    delete_file: "ask"
    move_file: "ask"
    find_and_replace_code: "ask"

    # Safe read operations
    open_files: "allow"
    expand_code_chunks: "allow"
    expand_folder: "allow"
    grep: "allow"

    # Planning tools
    createTechnicalPlan: "allow"

    # Atlassian integration tools
    getJiraIssue: "allow"
    createJiraIssue: "ask"
    updateJiraIssue: "ask"
    getConfluencePage: "allow"
    createConfluencePage: "ask"
    updateConfluencePage: "ask"

  # Bash command permissions
  bash:
    # Default permission for bash commands (default: "ask")
    default: "ask"

    # Specific bash commands with permissions
    commands:
      - command: "ls.*"
        permission: "allow"
      - command: "cat.*"
        permission: "allow"
      - command: "echo.*"
        permission: "allow"
      - command: "pwd"
        permission: "allow"

    # Run bash commands in sandboxed environment (macOS only, internal users)
    runInSandbox: false

  # File/directory paths allowed outside workspace
  allowedExternalPaths: []

Rovo Dev credits

Set the site with your allocation of Rovo Dev credits to use for Rovo Dev CLI.

atlassianBillingSite:
  siteUrl: "https://yoursite.atlassian.net"
  cloudId: "your-cloud-id"

Use a new configuration file

To set a new configuration file in a custom location, run Rovo Dev with the --config-file flag followed by the new location. Rovo Dev will create the file if it doesn’t exist. For example:

acli rovodev run --config-file ~/.rovodev/new-configuration.yml

Was this helpful?

It wasn't accurateIt wasn't clearIt wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community