update-cli-config
Skill0 starsChanged 2 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.
7 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- ArangoGutierrez/claude-toolkitedited, first seen Oct 15, 2026
- 0mlkrizzz655335v/claude-skills-zhtheir own version, first seen Oct 15, 2026
- leishifu666/skillsedited, first seen Oct 9, 2026
- Goodnessmbakara/codex-skillsword for word, first seen Oct 8, 2026
- JameMy0001/antigravity-skills-hubedited, first seen Oct 2, 2026
- filipefalcaofs/repo-padraoedited, first seen Jul 8, 2026
Other versions7 projects use a version of this.
Word for word · 1
- Goodnessmbakara/codex-skills★ 1100% same
Edited · 5
- ArangoGutierrez/claude-toolkit★ 498% same
- JameMy0001/antigravity-skills-hub★ 194% same
- leishifu666/skills★ 196% same
- PandelisZ/skills★ 196% same
- filipefalcaofs/repo-padrao★ 096% same
Wrote their own version · 1
- 0mlkrizzz655335v/claude-skills-zh★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/base-rule.mdcCursor rule
- .cursor/rules/bash-style.mdcCursor rule
- .cursor/rules/groovy-implicit-return.mdcCursor rule
- .cursor/rules/groovy-style.mdcCursor rule
- .cursor/rules/markdown-style.mdcCursor rule
- .cursor/rules/python-style.mdcCursor rule
- automateSkill
- autopilotSkill
- canvasSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- create-subagentSkill
- cursor-blameSkill
- git-messageSkill
- goalSkill
- loopSkill
- migrate-to-skillsSkill
- new-repoSkill
- onboardSkill
- originSkill
- rename-chatSkill
- review-bugbotSkill
- review-securitySkill
- reviewSkill
- sdkSkill
- shareSkill
- shellSkill
- split-to-prsSkill
- statuslineSkill
- update-cursor-settingsSkill
The file
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 5 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
- Very specific: line 24
Read ~/.cursor/cli-config.json, apply changes, and write it back.
- Very specific: line 58
Run Everything — auto-approve all tool calls (same as --force / --yolo.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
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 inputdefaultBehavior:"ide"|"agent"— default behavior mode
display (optional)
showLineNumbers: boolean (default: false) — show line numbers in code outputshowThinkingBlocks: boolean (default: false) — show model thinking/reasoning blocksshowStatusIndicators: boolean (default: false) — show status indicators in the UI
channel (optional)
Release channel: "prod" | "lab" | "static"
maxMode (optional)
boolean (default: false) — enable max mode for higher-quality model responses
subagentModels (optional)
Per-subagent model settings.
explore:"default"|"inherit"|"disabled"or{ "modelId": string, "parameters"?: [{ "id": string, "value": string }], "maxMode"?: boolean }— use Cursor's default Explore model, inherit the parent agent's model, disable the Explore subagent, or pin a specific model. Whenparametersis omitted, saved per-model parameter preferences apply; whenmaxModeis omitted, the parent conversation's max mode applies.
exploreSubagentModel (optional, legacy)
"default" | "inherit" (default: "default") — legacy Explore model setting. subagentModels.explore wins when both are set; keep this in sync ("inherit" when explore inherits, otherwise "default") so older CLI versions reading the same config behave sensibly.
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 sandboxnetworkAllowlist: 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 regiontestModel: string — model to use for testingteamRoleArn: string — IAM role ARN for team modeteamExternalId: 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 agentattributePRsToAgent: 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 versionmodel/selectedModel/modelParameters/hasChangedDefaultModel— managed by the model pickerprivacyCache— cached privacy mode stateauthInfo— cached authentication infoshowSandboxIntro— one-time UI flagconversationClassificationScoredConversations— internal cache
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
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.

