projectb-update-cli-config

Modify CLI configuration settings for Codex or legacy Cursor hosts.

Updated May 28, 2023
One-click install
npx skills add https://github.com/steveulrich/ProjectB --skill projectb-update-cli-config-steveulrich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: projectb-update-cli-config
Source: https://github.com/steveulrich/ProjectB/tree/main/.agents/skills/projectb-update-cli-config
Command: npx skills add https://github.com/steveulrich/ProjectB --skill projectb-update-cli-config-steveulrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Editing CLI configuration files is risky when you do not know which host you are on or which schema applies. This Skill resolves the active host and its configuration first, then applies only the requested changes while preserving sandbox, credential, and approval boundaries. ## Core Features & Use Cases - Host Resolution: Identifies whether the current environment is Codex or a Cursor-compatible host before touching any config file. - Schema-Aware Editing: Uses current Codex config.toml documentation for Codex and the legacy Cursor cli-config.json schema only for verified Cursor hosts. - Boundary Preservation: Changes only the requested settings and leaves unrelated configuration, sandbox rules, credentials, and approval modes untouched. - Use Case: A user asks to enable network access in the sandbox. The Skill verifies the host, locates the resolved config path, updates only the sandbox networkAccess field, and keeps all other settings intact. ## Quick Start Update my CLI configuration to enable vim mode, making sure to detect whether I am on Codex or Cursor first.

Frequently Asked Questions about projectb-update-cli-config

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

FAQPage Schema
How do I change Codex CLI configuration settings?▼

Resolve the current host and its active config.toml paths using current Codex documentation, then edit only the requested settings. Preserve unrelated configuration and existing sandbox, credential, and approval boundaries during the change.

Where is the Cursor CLI config file located?▼

The legacy Cursor CLI config file is ~/.cursor/cli-config.json. Projects can layer overrides via .cursor/cli.json files, which are merged from the git root to the working directory but never written back to the home config.

When should I use the legacy Cursor schema instead of Codex?▼

Use the legacy Cursor reference only for an explicitly identified Cursor-compatible host after verifying its packages, paths, and tool schema. Do not load it for current Codex tasks, which follow the current Codex config.toml conventions.

Which CLI config fields should not be modified?▼

Do not edit internal or cached state fields such as version, model, selectedModel, modelParameters, privacyCache, authInfo, showSandboxIntro, or conversationClassificationScoredConversations. These are managed by the CLI itself and manual edits can break behavior.

Do CLI config changes take effect immediately?▼

Changes to the legacy Cursor cli-config.json take effect after restarting the CLI. Project-level .cursor/cli.json overrides only affect the current session and are not persisted to the home configuration.