Manage Rovo Dev CLI settings
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設定オプション
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
# Disable built-in Atlassian MCP server (internal users only)
disableBuiltinAtlassianMcp: falseセッション
sessions:
# Directory where session data is stored
persistenceDir: "~/.rovodev/sessions"
# (Experimental) When enabled, Rovo Dev may warn and offer to switch your
# workspace git state (branch/commit) to match the session checkpoint when
# restoring or switching sessions.
enableWorkspaceStateSync: falseAtlassian 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コンソール
Settings to control how Rovo Dev CLI displays information and handles input.
console:
# Output format for console display (markdown, simple, or raw)
outputFormat: markdown
# Show tool execution results in the console
showToolResults: true
# Per-tool configuration for whether to show tool execution results in the
# console
toolResultVisibility:
bash: true
powershell: true
open_files: true
create_file: true
delete_file: true
move_file: true
expand_code_chunks: true
find_and_replace_code: true
grep: true
expand_folder: true
update_allowed_external_paths: true
# Editing mode for the prompt session
editingMode: EMACS
# Shell command to generate a command prompt that replaces the default '> '.
# For example, set 'STARSHIP_SHELL=rovodev starship prompt' to use Starship.
customCommandPrompt: null
# Color theme for syntax highlighting. Options: 'dark' (Dracula), 'light',
# 'auto' (detect system theme), or any [Pygments theme
# name](https://pygments.org/styles/)(e.g., 'monokai', 'solarized-light')
theme: textual-dark (bg)
# Maximum width of the console output in characters, or 'fill' to fill the
# terminal width
maxOutputWidth: 120
# Enable or disable animated startup loading screen
enableStartupAnimations: true
# Automatically copy selected text to clipboard when text is selected in the
# chat
copyOnSelect: true
# Terminal tab title settings
terminalTitle:
# Enable or disable automatic terminal tab title updates
isEnabled: true
# Terminal tab title format string. Supported template variables: • {cwd}
# — workspace directory name • {project} — full workspace path •
# {branch} — current git branch • {session} — session title • {model}
# — current model name
displayValue: 'Rovo Dev: {session} | branch: {branch}'ログ
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: falseMCP (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: []ツール
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 クレジット
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
この内容はお役に立ちましたか?