@sehlceris/claude-code-setup

Non-interactive setup script that configures Claude Code's global settings the way I like them.

Runs once, writes to ~/.claude/settings.json, exits. No prompts, no per-project files, no fuss.

Usage

From a local clone (no publish required)

git clone https://github.com/sehlceris/claude-code-setup.git
cd claude-code-setup
npm start

From npm

npx @sehlceris/claude-code-setup

Or install globally:

npm i -g @sehlceris/claude-code-setup
claude-code-setup

What it does

Deep-merges the following into ~/.claude/settings.json (Windows: %USERPROFILE%\.claude\settings.json). Existing keys are preserved — only the keys below are added or overwritten.

{
  "attribution": {
    "commit": "",
    "pr": ""
  },
  "env": {
    "CLAUDE_CODE_DISABLE_1M_CONTEXT": "1"
  }
}

Why these settings

| Setting | Effect | | --- | --- | | attribution.commit = "" | No Co-Authored-By: Claude... line in git commits | | attribution.pr = "" | No AI attribution footer in PR descriptions | | env.CLAUDE_CODE_DISABLE_1M_CONTEXT = "1" | Disables the 1M-token context window (use the standard 200K context) |

Customizing

Edit the SETTINGS_PATCH object at the top of bin/cli.js to add/remove settings. The script deep-merges, so nested keys are safe to add.

Platform support

Works on macOS, Linux, and Windows. The settings path resolves via $HOME or %USERPROFILE%.

Publishing to npm

# One-time login
npm login

# Scoped packages are private by default — use --access public
npm publish --access public

To publish a new version, bump first:

npm version patch   # or minor / major
npm publish --access public

License

MIT