@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": ""
  },
  "autoCompactWindow": 400000
}

It also removes env.CLAUDE_CODE_DISABLE_1M_CONTEXT if a previous run set it.

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 | | autoCompactWindow = 400000 | Auto-compact once the conversation reaches 400K tokens |

autoCompactWindow is the same key the /autocompact slash command writes, so setting it here is equivalent to running /autocompact 400k. It must be an integer between 100,000 and 1,000,000; values outside that range are silently ignored by Claude Code.

The 1M context window is deliberately left enabled. CLAUDE_CODE_DISABLE_1M_CONTEXT caps the model at 200K, and autoCompactWindow is clamped to the model's limit — so with that flag set, any window above 200K is quietly capped back down. Keeping the 1M window and compacting at 400K gives the summarizer headroom instead.

Note that a CLAUDE_CODE_AUTO_COMPACT_WINDOW environment variable, if set, takes priority over this setting.

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. Setting a value to null deletes that key from the existing settings rather than writing it — useful for retiring a setting an earlier run applied.

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