AI Disruption

AI Disruption

I Changed 8 Settings and Claude Code Got Smarter

I changed 8 Claude Code settings to fix quota stops, lost sessions, and context issues. Here is what each setting does and when to use it.

Meng Li's avatar
Meng Li
Nov 08, 2026
∙ Paid

For a while, I thought Claude Code had a quirk: it kept stopping halfway through a job, at odd moments.

Sometimes my usage quota ran out. Sometimes it popped up a question and waited for me to choose. And sometimes, when I wanted to pick up the next day, the previous session had already been wiped.

At first I assumed the model was unstable. Then I went through settings.json from top to bottom and realized the problem wasn’t the prompt. Claude Code has a pile of default behaviors that sit in /config, or aren’t shown at all. If you don’t change them, it just keeps running at its own pace.

Here are the 8 settings I think are most worth knowing. They aren’t “300% performance boost” magic switches, but each one maps to a very specific annoyance.

One warning first: don’t copy some of these values as-is. Your model, terminal, and team conventions differ from mine, and there are no standard answers for settings.

User's avatar

Continue reading this post for free, courtesy of Meng Li.

Or purchase a paid subscription.
© 2026 Meng Li · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture