Skip to main content
Devin for Terminal is configured through JSON files (with comment support) at the user and project level. These config files control the agent’s model, permissions, MCP servers, and more.

​
Config File Locations

Path: ~/.config/devin/config.jsonYour personal defaults that apply across all projects. This is where you set your preferred model, theme, and global permissions.
On Windows, this path is %APPDATA%\devin\config.json (typically C:\Users\<you>\AppData\Roaming\devin\config.json).
{
  "agent": { "model": "claude-sonnet-4.5" },
  "permissions": {
    "allow": ["Read(**)", "Exec(git)"]
  }
}

​
What You Can Configure

Model

Choose which AI model powers the agent — from Claude Opus to GPT 5.2 to Gemini 3.

Permissions

Pre-approve safe actions, block dangerous ones, and control what the agent can do without asking.

MCP Servers

Connect external tool servers for GitHub, Linear, databases, and any custom APIs.

External Tool Imports

Import rules, skills, and configuration from Cursor, Windsurf, and Claude Code.

​
Quick Start

The fastest way to get started is to create a .devin/config.json in your project root: 
{
  "permissions": {
    "allow": [
      "Read(**)",
      "Exec(git)",
      "Exec(npm run)"
    ]
  }
}
This pre-approves file reads and common commands so the agent doesn’t prompt you for every action.
You can also configure Devin for Terminal interactively — when the agent asks for permission, choose to save the decision to your project or user config for next time.

​
Project vs User Settings

Not all settings are available at every level. Project configs (.devin/config.json and .devin/config.local.json) support:
  • permissions — allow, deny, and ask rules
  • mcpServers — MCP server definitions
  • read_config_from — import settings from Cursor, Windsurf, and Claude
  • hooks — lifecycle hooks (see Hooks)
All other settings — including agent (model), theme_mode, unicode_mode, show_path, sandbox, and other display/behavior options — are user-config only and can only be set in the user config (~/.config/devin/config.json; %APPDATA%\devin\config.json on Windows).

​
Configuration Precedence

For settings that support multiple levels, higher-priority sources win:
PrioritySourceShared?
1 (highest)Organization / Team settingsYes (enterprise)
2Session grants (interactive approvals)No (in-memory)
3Project local (.devin/config.local.json)No (gitignored)
4Project (.devin/config.json)Yes (committed)
5 (lowest)User (~/.config/devin/config.json; %APPDATA%\devin\config.json on Windows)No (personal)
Permissions are merged across levels, while MCP servers are merged by name (higher-priority source wins for same-named servers).
Organization-level settings cannot be overridden by project or user config. See Configuration Precedence for full details on how merging works.

​
Limitations

Devin for Terminal does not support .codeiumignore files. If you use Codeium’s autocomplete and have configured ignore patterns, those patterns will not apply to Devin for Terminal.

​
Learn More

Full Config Reference

Complete list of every configuration option and its format.

Configuration Precedence

How global, project, and local settings interact and merge.