Hey everyone, just wanted to share a quick tip that saved me a lot of headaches. I was getting super frustrated with my Claude CLI vesion 1.0.0 constantly throwing "Invalid tool argument" errors and getting stuck in loops. Turns out I was running an outdated version.

After updating to the latest version (1.0.18), it's like night and day - feels way smarter and more responsive.

The Anthropic team seems to be pushing fixes and improvements constantly.

So friendly reminder: take a minute to update your CLI.

npm install -g /claude-code@latest

You can check your current version with:

claude --version

Current version is 1.0.18

Anybody got the error where Claude Code says it failed to auto-update? This happened after every morning I woke up. Though I still see the new information when enter "/release-notes", however, the new releases/features are not there in CC.

My work around was to create a script to uninstall and reinstall it again after every the error happens. Although it was only once a day, but it's a pain and using "/doctor" or installing it locally as CC suggests still doesn't solve the issue.

I like to use Claude Code. However, this month-old bug makes it a lot less than usable.

I've searched how to prevent auto-updates, but all I've found is a ~/.claude/settings.json that does not actually exist.

It there a way to keep Claude Code on a version where compacting works (1.0.44)?

Edit: I’m a noob, for any other confused noobs you just have to create ~/.claude/settings.json yourself

Hey everyone,

Whenever I launch Claude Code, I see this red message:

✗ Auto-update failed · Try claude doctor or npm i -g u/anthropic-ai/claude-code

Thing is, Claude works perfectly fine for me , no crashes, no issues, everything runs smoothly.

So my question is:

• Is this something I should fix right away?

• Or is it safe to just ignore as long as everything is working?

Curious to hear if others see the same thing!

Only see the release notes until 1.0.54? Curious to what was implemented

I don't know what on Earth happened to Opus but it's been awful these past two-three days.

BUT I saw someone on X say that downgrading the CLI to v2.0.64 improved Opus 4.5 performance significantly, and I tried this. It made a huge difference.

Something is wrong with the current harness.

To downgrade:

Would like to hear your input on this as well.

If you’re back to Claude Code after testing GPT5 (or maybe you never left 👀), we have something you might be interested in.

Clauder is an open source, auto-updating, safety first toolkit for Claude Code. The idea is to provide you with a safer configuration and a strong toolkit to work on production grade projects, and to have it auto-update so you don’t have to think about it again.

Claude Code CLI 2.0.70 changelog:

• Added Enter key to accept and submit prompt suggestions immediately (tab still accepts for editing)

• Added wildcard syntax mcp__server__* for MCP tool permissions to allow or deny all tools from a server.

• Added auto-update toggle for plugin marketplaces, allowing per-marketplace control over automatic updates.

• Added plan_mode_required spawn parameter for teammates to require plan approval before implementing changes.

• Added current_usage field to status line input, enabling accurate context window percentage calculations.

• Fixed input being cleared when processing queued commands while the user was typing.

• Fixed prompt suggestions replacing typed input when pressing Tab.

• Fixed diff view not updating when terminal is resized.

• Improved memory usage by 3x for large conversations.

• Improved resolution of stats screenshots copied to clipboard (Ctrl+S) for crisper images.

• Removed # shortcut for quick memory entry (tell Claude to edit your CLAUDE.md instead).

• Fix thinking mode toggle in /config not persisting correctly.

• Improve UI for file creation permission dialog.

Source: Anthropics (GitHub)

🔗: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

🔗: https://code.claude.com/docs/

How do you guys update Claude.md? And how often?

Do you delete it and rerun init?

Or do you ask Claude to do it?

Or do you do it manually ?

The latest version of Claude-Code has completely lost its agentic qualities. It now behaves more like a basic, guessing flashlight-style local model dumb and unresponsive rather than the intelligent tool it used to be.

In [email protected], everything worked perfectly: it followed context seamlessly, remembered previous actions, created its own to-do lists, and genuinely felt like collaborating with a real coder buddy. But the new release is an absolute disaster. I have no idea whose idea it was to approve and release this version—it's a huge step backward.

I've disabled auto-updates in the .claude.json and downgraded back to [email protected], which is still perfect for my needs. I highly recommend others try downgrading too if you're facing the same issues.

With the latest version of Claude Code I am hitting context limits within 1-2 messages, which doesn't even make sense. Token usage is not correct either. I downgraded claude code to 1.0.88 and did /context again, went from 159k tokens to 54k tokens which sounds about right. Something is very wrong with the latest version of Claude Code. It's practically unusable with this bug.

I used these commands to downgrade and got back to a stable version of Claude Code, for anyone wondering:

https://github.com/anthropics/claude-code/issues/5969#issuecomment-3251208715

npm install -g @anthropic-ai/[email protected]
claude config set -g autoUpdates disabled

And you can set the model back to Sonnet 4.5 by doing
/model claude-sonnet-4-5-20250929

Edit: apparently setting autoUpdates to disabled does nothing now, check the github link to turn autoupdate off

Is there a way to subscribe to Claude Code updates via RSS or a webhook? I found this website, but it doesn't seem to offer anything.
https://claudelog.com/claude-code-changelog/

Hi everyone,

Yesterday I stumbled upon a video on youtube

https://www.youtube.com/watch?v=s9nt8xaXFdg

and tried Auto-Claude.

https://github.com/AndyMik90/Auto-Claude?tab=readme-ov-file

I have to admit the project is still rough around the edges, but look incredibly promising. It has good things all around, and some others that need some small tweaks.

I was wondering if anyone has used it and what are your thoughts.

Full disclosure: I am not involved in the project, I am just sharing this because I like what I see and I'd love to hear if anyone else tried it and has some feedback!

You will need to update to v1.0.11 to be able to use Claude Code with a Pro subscription.

Figured this wouldn't fit the Megathread but - every update in terms of the UI that Code has received so far has been absolute buttcheeks.

First, the errors Claude would get from tool calls got hidden away, sure, no big deal, not like it's THAT important whether the issue is some access thing or smth more innocuous, not too bad

Then the remaining context label disappeared so now instead of being able to time compact requests, you now suddenly learn you only have 10% context left and have to compact immediately, right after a 3-message-long context setup. Starting to be a bit annoying. Hell, sometimes the context warning doesn't arrive until the entire context window is full, so now you lost both the context AND tokens

Now the TODO lists are completely obfuscated! What's even the point? It feels like Anthropic hired a new designer who's previous job was Airbnb with the way each update was just going more and more into minimalism.

A bit absurd really

Hey Folks,

Just wanted to quickly report that Claude Code is running perfectly again for me! Had some issues with it over the past few days/weeks, but after updating normally today, everything is working as it should.

Anthropic announced today that they've fixed various bugs, and I can confirm - it's definitely noticeable. The performance is back and commands are executing correctly.

Has anyone else had similar experiences?

• Did you also have problems with Claude Code recently?

• Is it working better for you after the update?

• What specific improvements have you noticed?

Curious to hear about your experiences!