update-cli-config

Update Cursor CLI preferences by merging home and project config overrides.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill update-cli-config-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-cli-config
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.cursor/skills-cursor/update-cli-config
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill update-cli-config-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuring Cursor CLI settings across home and project scopes can be error-prone and repetitive, leading to inconsistent tool behavior.

Core Features & Use Cases

  • Config Discovery & Layering: The CLI merges home config with per-project overrides discovered from .cursor/cli.json files as you navigate the project tree.
  • Settings Coverage: Manages permissions, editor mode, display options, channel, sandbox, and attribution for commits.
  • Use Case: A developer wants vim mode enabled for faster editing while restricting tool calls during automated workflows.

Quick Start

Open the Cursor CLI and run the update-cli-config command to adjust your settings.

Frequently Asked Questions about update-cli-config

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

FAQPage Schema
How do I update Cursor CLI settings like permissions and vim mode?

To update Cursor CLI settings, you modify the ~/.cursor/cli-config.json file to adjust permissions, enable vim mode, change display options, or configure sandbox behavior.

How does Cursor CLI config layering work for project overrides?

Cursor CLI config layering merges your home config with per-project overrides discovered in .cursor/cli.json files as you navigate the project tree, ensuring environment-specific behavior.

Can I restrict tool calls and manage sandbox settings for Cursor CLI?

Yes, you can restrict tool calls and manage sandbox settings by updating the CLI config to enforce specific permissions and runtime behavior for automated workflows.

Do I need to restart the Cursor CLI after changing configuration files?

Yes, you need to restart the Cursor CLI after changing configuration files so the persisted settings merge correctly and take effect across your development environment.

What is the best way to manage per-user and per-project Cursor CLI preferences?

The best way to manage Cursor CLI preferences is by updating the home config and merging project-specific overrides, allowing distinct settings for permissions, editor mode, and channel.