update-cli-config

View and modify Cursor CLI settings in the cli-config.json configuration file.

3|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill update-cli-config-arangogutierrez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-cli-config
Source: https://github.com/ArangoGutierrez/claude-toolkit/tree/main/.cursor/skills-cursor/update-cli-config
Command: npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill update-cli-config-arangogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cursor CLI settings live in a JSON file at ~/.cursor/cli-config.json with many fields, some of which are internal state that must not be edited. This Skill tells the AI exactly which settings exist, what values they accept, and which fields to leave alone, so configuration changes are made correctly without corrupting the file. ## Core Features & Use Cases - Settings Reference: Documents every configurable field including permissions, editor vim mode, display options, approval mode, sandbox, network, AWS Bedrock, and git attribution. - Project Overrides: Explains how .cursor/cli.json files layer project-level overrides on top of the home config, merged from git root to working directory. - Protected Fields: Lists internal fields (version, model selection, authInfo, privacyCache) that must never be modified manually. - Use Case: A user wants to enable vim keybindings and auto-approve tool calls. The Skill guides the AI to read the config, set editor.vimMode to true and change approvalMode, then write the file back so changes apply on restart. ## Quick Start Ask the AI to enable vim mode and show thinking blocks in your Cursor CLI configuration.

Frequently Asked Questions about update-cli-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change Cursor CLI settings?▼

Cursor CLI settings are stored in ~/.cursor/cli-config.json as standard JSON. Read the file, apply your changes to fields like permissions, editor, or display, and write it back. Changes take effect after restarting the CLI.

How do I enable vim mode in Cursor CLI?▼

Set editor.vimMode to true in ~/.cursor/cli-config.json. The editor section also supports defaultBehavior, which can be set to "ide" or "agent" to control the default behavior mode.

Can I override Cursor CLI config per project?▼

Yes, projects can layer overrides via .cursor/cli.json files. The CLI walks from the git root to the current working directory and merges each file it finds, with deeper files taking precedence. Project overrides only affect the current session and are not written back to the home config.

Which Cursor CLI config fields should not be edited?▼

Do not modify internal or cached state fields: version, model, selectedModel, modelParameters, hasChangedDefaultModel, privacyCache, authInfo, showSandboxIntro, and conversationClassificationScoredConversations. These are managed by the CLI itself.

How do I auto-approve all tool calls in Cursor CLI?▼

Change the approvalMode setting away from the default "allowlist" value to the Run Everything mode, which auto-approves all tool calls. This is equivalent to launching the CLI with the --force or --yolo flags.

How do I configure sandbox network access in Cursor CLI?▼

Set sandbox.mode to "enabled" and choose a networkAccess policy: "user_config_only", "user_config_with_defaults", or "allow_all". Use the networkAllowlist array to specify domains the sandbox is permitted to reach.