Configuration

Amp reads settings from these locations:

  • User settings:
    • macOS: ~/.config/amp/settings.json or ~/.config/amp/settings.jsonc
    • Linux: ~/.config/amp/settings.json or ~/.config/amp/settings.jsonc
    • Windows: %USERPROFILE%\.config\amp\settings.json or %USERPROFILE%\.config\amp\settings.jsonc
  • Workspace settings: the nearest .amp/settings.json or .amp/settings.jsonc, searched upward from your current working directory to the repository root, or the current directory outside a Git repository
  • Custom user settings: pass --settings-file <path> to point Amp at a different user settings file

Run amp config edit to open your user settings file in $EDITOR, or add --workspace to edit workspace settings.

When the same setting appears in multiple places, workspace settings override user settings.

All settings use the amp. prefix.

Settings

  • amp.fuzzy.alwaysIncludePaths

    Type: array, Default: []

    Glob patterns for paths that should always be included in fuzzy file search, even if they are ignored by Git. This is useful for build output directories or generated files you want to reference with @ mentions.

    Examples: ["dist/**", "node_modules/@myorg/**"]

  • amp.showCosts

    Type: boolean, Default: true

    Show cost information for threads in the CLI while working. Workspace admins can also hide costs for all workspace members in workspace settings.

  • amp.git.commit.ampThread.enabled

    Type: boolean, Default: true

    Add the Amp thread trailer to Git commits. When disabled, commits made by the agent will not include the Amp-Thread-ID: <thread-url> trailer. You can also set the environment variable AMP_DISABLE_AMP_THREAD_TRAILER=1.

  • amp.git.commit.coauthor.enabled

    Type: boolean, Default: true

    Add Amp as a coauthor in Git commits. When disabled, commits made by the agent will not include the Co-authored-by: Amp <amp@ampcode.com> trailer. You can also set the environment variable AMP_DISABLE_AMP_COAUTHOR_TRAILER=1.

  • amp.keymap

    Type: object, Default: {}

    Customize the CLI keymap. Keymap entries in user settings override entries in workspace settings. See Customize the Keymap for more information.

  • amp.mcpServers

    Type: object

    Model Context Protocol servers that expose tools. See the MCP documentation.

  • amp.defaultVisibility

    Type: object

    Define default thread visibility per repository origin using mappings such as {"github.com/org/repo": "workspace"}. Values are private, workspace, and group.

  • amp.notifications.enabled

    Type: boolean, Default: true

    Play notification sounds when the agent completes a task or is blocked waiting for user input. Over SSH, or when AMP_FORCE_BEL is set, Amp sends a terminal bell instead of using host audio.

  • amp.remoteThreadCreation.enabled

    Type: boolean, Default: false

    Let ampcode.com create new threads that open in the interactive Amp TUI on this machine, in the directory where it was started. Toggle it from the TUI command palette with amp: enable remote creation of threads.

  • amp.skills.disableClaudeCodeSkills

    Type: boolean, Default: false

    Disable loading skills from Claude Code directories (.claude/skills/, ~/.claude/skills/, and ~/.claude/plugins/cache/). This does not affect .agents/skills/, ~/.config/agents/skills/, ~/.agents/skills/, ~/.config/amp/skills/, amp.skills.path, built-in skills, personal skills, or workspace skills.

  • amp.skills.path

    Type: string

    Path to additional directories containing skills. This setting supports colon-separated paths, or semicolon-separated paths on Windows. Use ~ for your home directory. Example: ~/my-skills:/shared/team-skills

  • amp.terminal.copyOnSelect

    Type: boolean, Default: true

    By default, the Amp TUI copies the selection to the clipboard. When set to false, selecting text in the thread transcript does not copy it automatically. Press Ctrl+C to copy an active transcript selection manually.

  • amp.terminal.detailsExpandedByDefault

    Type: boolean, Default: false

    Expand thinking and tool call details by default in the CLI transcript. Press

    Alt+T to collapse or expand details for the current session.

  • amp.thread.autoArchiveOnQuit

    Type: boolean, Default: false

    Automatically archive open CLI threads when quitting Amp. This applies to the active thread and any background threads connected in the current CLI session.

  • amp.tools.disable

    Type: array, Default: []

    Disable specific tools by name. Use builtin:toolname to disable only the built-in tool with that name while allowing an MCP server to provide a tool by the same name. Glob patterns using * are supported.

  • amp.mcpPermissions

    Type: array, Default: []

    Allow or block MCP servers that match a pattern. Amp applies the first matching rule. If no rule matches an MCP server, Amp allows it.

    • For a remote MCP server, use the url key to match the server endpoint.
    • For a local MCP server, use the command and args keys to match an executable command and its arguments.

    Here are some examples:

    "amp.mcpPermissions": [
  // Allow specific trusted MCP servers
  { "matches": { "command": "npx", "args": "* @playwright/mcp@*" }, "action": "allow" },
  { "matches": { "url": "https://mcp.trusted.com/mcp" }, "action": "allow" },
  // Block potentially risky MCP servers
  { "matches": { "command": "python", "args": "*bad_command*" }, "action": "reject" },
  { "matches": { "url": "*/malicious.com*" }, "action": "reject" }
]

    The following rules block all MCP servers:

    "amp.mcpPermissions": [
  { "matches": { "command": "*" }, "action": "reject" },
  { "matches": { "url": "*" }, "action": "reject" }
]

  • amp.updates.mode

    Type: string, Default: "auto"

    Control update checking. "warn" shows update notifications. "disabled" turns off update checks. "auto" installs updates automatically. Setting the AMP_SKIP_UPDATE_CHECK=1 environment variable overrides this setting and disables all update checks.

Enterprise Managed Settings

Enterprise workspace administrators can enforce settings that override user and workspace settings by deploying their policies to these locations on machines that run Amp:

  • macOS: /Library/Application Support/ampcode/managed-settings.json
  • Linux: /etc/ampcode/managed-settings.json
  • Windows: %ProgramData%\ampcode\managed-settings.json

This managed settings file uses the same schema as regular settings files, with one additional field:

  • amp.admin.compatibilityDate

    Type: string

    The date used to determine which migrations Amp must apply for backward compatibility. Use the YYYY-MM-DD format, such as 2024-01-15.

Proxies and Certificates

When using the Amp CLI in a corporate network with proxy servers or custom certificates, set these standard Node.js environment variables in your shell profile or CI environment as needed:

export HTTP_PROXY=your-proxy-url
export HTTPS_PROXY=your-proxy-url
export NODE_EXTRA_CA_CERTS=/path/to/your/certificates.pem