Skip to content
cccskills
FreePublished on GitHub

update-cli-config

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.

The English summary is being prepared. Showing the original description.

ax-inc-dev/claude-cursor-orchestration3 stars(GitHub 3 + cccskills 0)
Works withAWS

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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
  • "unrestricted" — auto-approve all tool calls (yolo mode)

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

B2B サイトの戦略・情報設計。価値提案・メッセージマップ・ジャーニー導線・意思決定マップ・信頼棚卸・トーン/禁止表現まで一気通貫でテンプレ化する。実装前フェーズ専用(全PJ共通)。

The English summary is being prepared. Showing the original description.

ax-inc-dev/claude-cursor-orchestration3Updated Apr 25, 2026

Keep a PR merge-ready by triaging comments, resolving clear conflicts, and fixing CI in a loop.

The English summary is being prepared. Showing the original description.

ax-inc-dev/claude-cursor-orchestration3Updated Apr 25, 2026

法人向けHTMLプレゼンスライドの実装エンジン。Claude Codeから指示書(アウトライン+テンプレート指定+カラー+コンテンツ)を受け取り、単一HTMLファイルとして実装する。43種テンプレート+14種アニメーション。トリガー:プレゼン実装、スライドHTML生成、提案資料コーディング。

The English summary is being prepared. Showing the original description.

ax-inc-dev/claude-cursor-orchestration3Updated Apr 25, 2026

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

The English summary is being prepared. Showing the original description.

ax-inc-dev/claude-cursor-orchestration3Updated Apr 25, 2026

canvas

Free

A Cursor Canvas is a live React app that the user can open beside the chat. You MUST use a canvas when the agent produces a standalone analytical artifact — quantitative analyses, billing investigations, security audits, architecture reviews, data-heavy content, timelines, charts, tables, interactive explorations, repeatable tools, or any response that benefits from visual layout. Especially prefer a canvas when presenting results from MCP tools (Datadog, Databricks, Linear, Sentry, Slack, etc.) where the data is the deliverable — render it in a rich canvas rather than dumping it into a markdown table or code block. If you catch yourself about to write a markdown table, stop and use a canvas instead. You MUST also read this skill whenever you create, edit, or debug any .canvas.tsx file.

The English summary is being prepared. Showing the original description.

ax-inc-dev/claude-cursor-orchestration3Updated Apr 25, 2026

Authors Cursor Rules (.cursor/rules/*.mdc) and custom Subagents (.cursor/agents/*.md or ~/.cursor/agents). Use when creating or refactoring rules/subagents, splitting large rules, choosing subagent vs skill, setting model/readonly/background, or replacing repeated delegation prompts.

The English summary is being prepared. Showing the original description.

ax-inc-dev/claude-cursor-orchestration3Updated Apr 25, 2026

See all skills by ax-inc-dev

Report a problem with this skill