Fear of updating: When 'vibe coding' meets production stability

[kolkov]

@bcherny - Your recent interview highlights the irony here

Hi Boris,

In your Peterman Pod interview (Dec 15, 2025), you said:

"You want maintainable code sometimes. You want to be very thoughtful about every line sometimes."

And that 80-90% of Claude Code is now written by Claude Code itself.

The Irony

The .claude.json architecture violates every principle you advocate for:

• No separation of concerns (config + history + state + changelog in ONE file)
• No atomic writes (corruption on concurrent access)
• No data lifecycle management (files growing to 65MB+)
• 30+ second startup delays for long-running projects

Beyond .claude.json — Systemic Stability Issues

This isn't just about config files. Recent versions have introduced critical stability problems:

• Complete system freezes — Claude Code sessions now regularly hang the entire computer (see [Bug] Complete system freeze when running 2+ GoLand IDE instances with Claude Code #14674)
• Only hard reboot helps — no graceful recovery possible
• Memory leaks? — unclear what's causing these freezes, no debugging info available
• Multiple IDE instances crash — running 2+ GoLand instances with Claude Code causes total system freeze ([Bug] Complete system freeze when running 2+ GoLand IDE instances with Claude Code #14674)
• Forcing users away — I'm increasingly switching to my own Go-based agent using Anthropic API directly, which is significantly more expensive but at least doesn't crash my machine

Fresh Bugs in v2.0.73 (just released!)

Here's what "thoughtful about every line" looks like in practice:

• [Bug] Complete system freeze when running 2+ GoLand IDE instances with Claude Code #14674 — Complete system freeze with 2+ IDE instances (requires hard reboot!)
• Markdown tables render incorrectly in terminal (broken layout, truncated text) #14641 — Markdown tables render incorrectly (broken layout, truncated Cyrillic text)
• [Bug] Claude API responses truncating mid-response #14637 — API responses truncating mid-response
• [Bug] Rendering Issue: Large Blank Areas Where Text Should Display #14632 — Large blank areas where text should display (rendering broken)

All are Windows bugs in recent releases. All are regressions.

The Real Problem

Every time I need to end a session or update to a new Claude Code version, I'm genuinely afraid. Not because of the new features, but because I have no idea how many new bugs were introduced — whether by humans or by the very "vibe coding" approach you describe.

If 80-90% of your codebase is written by AI, and you admit vibe coding is only good for "throwaway code and prototypes" — who is being "very thoughtful about every line" before releases?

The Business Impact

When your tool is unstable:

• Users pay MORE to use raw API instead of Claude Code
• Trust erodes with each forced reboot
• Community contributions go ignored for 8+ months

Context

See detailed technical analysis of .claude.json issues: #7243

Simple Ask

Is stability on the roadmap? A one-word "yes" or "no" would be more respectful than silence.

---

Sources:

• Peterman Pod interview (Dec 2025)
• Business Insider article
• Related: [Bug] Complete system freeze when running 2+ GoLand IDE instances with Claude Code #14674 [Bug] The .claude.json elephant in the room: Is this "vibe coding" in production? #7243 History accumulation in .claude.json causes performance issues and storage bloat #5024 Bug: .claude.json automatically stores conversation history when it shouldn't #1449 Critical: .claude.json bloat severely impacting user experience - consolidated community feedback #6394 [DOCS] No release notes for v2.0.0 #8353 Markdown tables render incorrectly in terminal (broken layout, truncated text) #14641 [Bug] Claude API responses truncating mid-response #14637 [Bug] Rendering Issue: Large Blank Areas Where Text Should Display #14632

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.