agentleFS
Sign inStart free
ArangoGutierrezArangoGutierrez/claude-toolkit/.cursor/skills-cursor/update-cli-config/SKILL.md

update-cli-config

Skill4 starsChanged 3 months agoMITView on GitHub

View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ~/.cursor/cli-config.json, apply changes, and write it back.

    line 24
  2. Very specific:

    Run Everything — auto-approve all tool calls (same as --force / --yolo.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cursor CLI Configuration

This skill explains how to view and modify Cursor CLI settings stored in ~/.cursor/cli-config.json.

Config File Location

The config file is ~/.cursor/cli-config.json.

Projects can layer overrides via .cursor/cli.json files. The CLI walks from the git root to the current working directory and merges each .cursor/cli.json it finds (deeper files take precedence). Project overrides only affect the current session; they are not written back to the home config.

How to Modify

Read ~/.cursor/cli-config.json, apply changes, and write it back. The file is standard JSON. Changes take effect after restarting the CLI.

Available Settings

permissions (required)

Tool permission rules. Each entry is a string pattern.

  • allow: string[] — patterns for allowed tool calls (e.g. "Shell(**)", "Mcp(server-name, tool-name)")
  • deny: string[] — patterns for denied tool calls

editor

  • vimMode: boolean — enable vim keybindings in the CLI input
  • defaultBehavior: "ide" | "agent" — default behavior mode

display (optional)

  • showLineNumbers: boolean (default: false) — show line numbers in code output
  • showThinkingBlocks: boolean (default: false) — show model thinking/reasoning blocks
  • showStatusIndicators: boolean (default: false) — show status indicators in the UI

channel (optional)

Release channel: "prod" | "staging" | "lab" | "static"

maxMode (optional)

boolean (default: false) — enable max mode for higher-quality model responses

approvalMode (optional)

Controls tool approval behavior:

  • "allowlist" (default) — require approval for tools not in the allow list
  • Run Everything — auto-approve all tool calls (same as --force / --yolo; set approval mode to the non-allowlist value)

sandbox (optional)

Sandbox execution environment settings:

  • mode: "disabled" | "enabled" (default: "disabled")
  • networkAccess: "user_config_only" | "user_config_with_defaults" | "allow_all" — controls network access from sandbox
  • networkAllowlist: string[] — domains the sandbox is allowed to reach

network (optional)

  • useHttp1ForAgent: boolean (default: false) — use HTTP/1.1 instead of HTTP/2 for agent connections (enables SSE-based streaming)

bedrock (optional)

AWS Bedrock integration settings:

  • enabled: boolean (default: false)
  • mode: "access-key" | "team-role" (default: "access-key")
  • region: string — AWS region
  • testModel: string — model to use for testing
  • teamRoleArn: string — IAM role ARN for team mode
  • teamExternalId: string — external ID for STS assume-role

attribution (optional)

Controls how agent work is attributed in git:

  • attributeCommitsToAgent: boolean (default: true) — attribute commits to the agent
  • attributePRsToAgent: boolean (default: true) — attribute PRs to the agent

webFetchDomainAllowlist (optional)

string[] — domains the web fetch tool is allowed to access (e.g. "docs.github.com", "*.example.com", "*")

Fields You Should NOT Modify

These are internal/cached state and should not be edited manually:

  • version — config schema version
  • model / selectedModel / modelParameters / hasChangedDefaultModel — managed by the model picker
  • privacyCache — cached privacy mode state
  • authInfo — cached authentication info
  • showSandboxIntro — one-time UI flag
  • conversationClassificationScoredConversations — internal cache

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free