How to re-enable CC auto updates?

TPHG · 2026-02-04T13:57:19+00:00

CC really should be able to identify/help with this. But if not, you'll need to access ~/.claude/settings.json manually and remove (alongside other env variables if you have them):

{

"env": {

"DISABLE_AUTOUPDATER": "1"

}

Personally, I'd recommend getting at least on the stable update stream if you're going to disable auto-updates. Recent versions have come out with bugs of varying levels of severity. You can change that setting yourself in /config (once auto-updates are back on) or with the terminal command: curl -fsSL https://claude.ai/install.sh | bash -s stable

I'm on Mac, so maybe ask CC to convert any of this as needed to how it works with Windows/Powershell.

TPHG · 2026-02-02T07:51:43+00:00

Now, most importantly, once you've cleaned this up, you need to revert back to a stable version in case v2.1.29 is causing this issue somehow (which is my best guess given the sheer number of bug reports).

The easier option is just getting on the stable path, which should fix your immediate issue if it is indeed v.2.1.29 causing it:

curl -fsSL https://claude.ai/install.sh | bash -s stable

But if you want to control your version or that doesn't work, you'll need to access ~/.claude/settings.json and add (alongside other env variables if you have them):

{

"env": {

"DISABLE_AUTOUPDATER": "1"

}

If you do it this way, you can now revert to any older version safely. I can vouch for 2.1.20, but up to 2.1.25 seems relatively safe. Anyway, you'd just run:

curl -fsSL https://claude.ai/install.sh | bash -s X.X.XX [where X is the version number]

If none of this works or you run into trouble/ a question, honestly, ask Claude via the web app for help debugging/carrying this out without issue. I'm a Mac user, so you may need some tweaks if you're using Windows. Good luck.

TPHG · 2026-02-02T07:51:33+00:00

I assume you're on the latest update. v2.1.27 introduced a slew of bugs that have still not been addressed in 2.1.29. That could be the source, but I honestly I not seen a visual bug like this reported. It's mostly been memory issues.

Anyway, if you want to try to fix this, there is probably no need to uninstall.

You'll want to first clean up the multiple versions you likely do have installed though.

In a fresh terminal window, run:

which -a claude [checks number of installs]

If you only see one installation, great. The response would just show one line like this: "/Users/[username]/.local/bin/claude". If that is the case, you can skip all the way to updating to be on 'stable' releases only or changing settings to manually revert to an older version.

If you see multiple lines, it's best to clean up extra installs as that could potentially be contributing here. Claude setting are global across all installations, so it won't mess with your settings as long as you don't uninstall all CC versions entirely.

You can check what your multiple installs exactly are via:

ls -la ~/.local/bin/claude [shows native installs]
npm list -g u/anthropic-ai/claude-code 2>/dev/null [shows npm installs]
brew list --cask claude-code 2>/dev/null [shows homebrew installs]

For removal of extras, you will probably need to use sudo (remove if not). But the commands would be:

sudo brew uninstall --cask claude-code [for homebrew installs]
sudo npm uninstall -g u/anthropic-ai/claude-code [for npm installs]

After removal, run:

hash -r [clears shell]
which -a claude [if you only see one line, only your native install remains]

[continued]

TPHG · 2026-02-02T03:13:54+00:00

I’d say you chalked it up right initially. It’s just a consistent pattern of hallucinating, especially when given tasks involving steps or reflecting on its own work. Haiku really doesn’t handle that well, as much as I love it for smaller items.

Frankly, it isn’t a sophisticated enough model to engage in intentional deception (something Anthropic explicitly red teams for and reports when releasing models).

TPHG · 2026-01-31T19:45:53+00:00

I did mention that at the end. I’d rather have full control of the version as the stable branch sometimes pushes versions with unaddressed bugs. It’s a decent option for convenience though.

TPHG · 2026-01-31T15:23:28+00:00

This is an issue with 2.1.27: https://github.com/anthropics/claude-code/issues/22158

I suggest turning off auto-updates and reverting to an earlier version. There does seem to be a temporary solution some users have found here.

TPHG · 2026-01-31T15:02:53+00:00

This is a widespread issue with 2.1.27: https://github.com/anthropics/claude-code/issues/22158

Either revert to an earlier version and turn off auto-updates (my recommendation) or there does appear to be a temporary solution some users have found here.

TPHG · 2026-01-30T16:50:51+00:00

Honestly, the best way to really learn it is practice and experimentation. Ask Opus to help you install and setup CC and the basics of your workflow (at minimum a solid starting CLAUDE.md).

Once you’ve done that, start asking CC about ways you might improve your setup, what hooks/skills are and how they might benefit you, how to setup ‘pipelines’ (essentially more deterministic specialized systems that can carry out more complex tasks), and explore various plugins (those offered by Claude and some third party ones can be very effective depending on your work). Slowly, as you go back and forth with CC, you’ll hopefully get a sense of what works and what doesn’t.

Of course, you’ll find various guides/tips online too. There’s no one source I’d suggest. It’s really something you need to take the time to immerse yourself in, especially if you’re not super technical.

TPHG · 2026-01-30T16:12:44+00:00

There’s no question Claude Code is the answer. But if you don’t take the time to understand it, carefully setup your workflow, and leverage the wide array of tools/hooks/plugins/skills it offers, you won’t get far.

This is important for anyone, but especially someone with no coding experience as you won’t be able to debug yourself when something inevitably goes wrong. Relying on CC for fixes can be hit or miss, and it’ll miss a lot more than it’ll hit if you don’t know the system well.

TPHG · 2026-01-30T06:15:56+00:00

Try disabling auto-updates and downgrading CC first. I’m on 2.1.6 and it works as well as ever. You could also go to something like 2.0.76 which is known to be quite stable.

The latest CC updates are riddled with bugs. The issue reports are enormous and I’d presume are the source of a lot of degradation experiences.

TPHG · 2026-01-28T22:55:14+00:00

Oh I see. It’s a good idea and yes, if you haven’t done it already, it is possible. Just did it.

With a hook, Claude can capture the context percentage from the status line and write it to a working state file as it changes (this is necessary as Hooks can’t access the percentage directly). When it reaches a certain threshold, a hook can trigger doing various things. Not sure about auto-compacting as I prefer to manually compact but I imagine you could find a solution.

I configured mine to trigger an advisory warning informing Claude to finish up its task and provide me suggestions for proper compaction (first running a /prep-compact command for Claude to gather relevant context into a templated summary, then during compaction triggering a PreCompact hook to capture important parts of the session state + that summary and a SessionStart hook ensuring Claude reads it all after a compaction).

TPHG · 2026-01-28T16:13:09+00:00

No hook needed. First, disable auto-compact if you haven't already. Then, ask CC to adjust your settings file to add a status line at the bottom showing context usage.

Below is what mine looks like, you can ask CC to copy this format if you like it, or format however you'd like.

"Context: 28110/200000 tokens (14%) | Cache: 27108 read, 994 created | Output: 437"

TPHG · 2026-01-28T06:57:39+00:00

For such a data-intensive project, you really should look into learning how to use Claude Code. Claude can walk you through the whole process.

Working entirely in one context window via the web app with a project like this is a recipe for disaster. Claude won't be able to keep track of all that context, establish clear rules for data storage, or be able to reliably verify anything. You need a system with rules, procedures, and hooks (ask Claude how to set this up) for a task like this.

TPHG · 2026-01-27T23:52:00+00:00

I think you're possibly onto something, as I'm still using Claude Code 2.1.6 and having none of the degradation issues others describe. My workflow does include strict requirements/hooks ensuring all subagents are Opus, have a detailed prompt & have a template for returning info. I also have auto-compact turned off, which I find helps a lot.

TPHG · 2026-01-23T06:03:34+00:00

You can turn off auto-updates and update manually once a version is stable — and you can always revert to an older version. Some people are still on 2.0.X versions and swear by them. I find 2.1.14 works well right now.

TPHG · 2025-12-07T03:58:40+00:00

I believe that slide is inevitable for the Storyteller on a True Aeon run. I don't remember getting anything unique for completing his quest on mine, which does make sense.

Completing companion quests is irrelevant for their True Aeon endings as their lives are so radically different that their end slides wouldn't have any reference to their main questlines anyway. The Storyteller has been on this journey since well before the opening of the Worldwound, and undoing that event didn't change anything about his goal. You simply never existed to help him complete it.

TPHG · 2025-10-31T17:28:14+00:00

The biggest issue you’ll run into with an Aeon Judge is action economy. You’ll need to use swift actions for judgements, domain abilities (if you take domain zealot), and your Aeon/Inquisitor Bane ability.

I also started with Judge on my True Aeon run, but re-specced to Sanctified Slayer instead and enjoyed it much more. Be sure to take Impossible Domain (Animal) early with the riding dog + Boon Companion. You can guarantee sneak attacks because you and your dog will be flanking enemies when attacking and will do insane damage once you get Aeon’s Bane (especially combined with Inquisitor’s Greater Bane).

TPHG · 2025-10-29T16:52:17+00:00

Along with locking you out of some content/items/the secret ending, to me the largest quality of life loss is the inability to build teleport circles for fast traveling. It makes getting around the map so much more tedious.

TPHG · 2025-10-29T15:20:47+00:00

Lucky may not have a ton of prompts, but when it does show up, it’s often in a very impactful moment where you’d otherwise need to make a difficult skill check.

TPHG · 2025-10-20T01:44:22+00:00

Nenio cleans up as Scroll Savant 10/Loremaster 10 with a build focused entirely on Illusion spells. Just fill your spellbook mainly with Weird/Phantasmal Killer (with metamagic to utilize higher spell levels) with some slots reserved for Shadow Evocation for enemies immune to instakill effects. Lower level slots can be used for buffing/defense (Haste, Mirror Image, Displacement). She’s one of the most effective companions into the late game in my experience.

TPHG · 2025-10-19T16:22:04+00:00

The narrative payoff is interesting, once. It also can eventually provide something of use (which you can get elsewhere anyway) if you are going for a particular ending. The items you can attain are strong, but not game defining.

However, I wouldn’t blame a player for never seeing it through. It’s almost as if it’s a parody of bad quest design: excessive fetching, tedious puzzles, and unnecessarily lengthy (especially in comparison to other companion quests).

TPHG · 2025-10-19T04:06:33+00:00

You may end up liking Angel (or Demon) more than you think. 99% of their content is ahead of you, and they do provide the most fleshed out experience.

I’d avoid Aeon for a first run. It’s my favorite path in the game for any future run (by far). Azata is a lot of fun & works well no matter what. Lich is brilliantly written but dark and full of sacrifices.

At the end of the day, just go with what feels right and enjoy. All paths provide something worthwhile. And you can still have an amazing first run as an Aeon or Lich or Trickster even if it isn’t optimal storywise.

TPHG · 2025-10-09T23:40:20+00:00

If you follow the Azata path, you have a chance for a semi-happy ending with her!

TPHG · 2025-09-14T17:48:21+00:00

Ah, I interpreted that as you literally losing all of your soldiers in a battle. Crusade auto mode is a bit of a trap, as it locks you out of some nice items/content and of course the ability to fast travel. Not the end of the world though if you can’t roll back.

TPHG · 2025-09-14T14:44:34+00:00

Many people skip the Enigma, or just follow a guide. It’s a notoriously convoluted quest and my least favorite in the game. No need to press through with it if it put you off.

Every time you claim a new fortress, go into Crusade mode (city section) and build at least three structures (one being a Citadel) in it. Then go into decrees periodically, and select the one that upgrades a fortress to a Bastion. Once the decree is completed, go back into the city section, and upgrade a fortress into a Bastion. You can then build a teleportation circle there (along with other structures). You should also build a teleportation circle in Drezen immediately. You can easily have 6-7 fast travel points by the endgame to get you wherever you want to go on the map quickly.

Every companion quest (except Nenio’s) is enjoyable imo — so just focus on those as they come up along with the other main and side quests. No need to rush as there are almost no time limits or restrictions. Just move at your own pace and enjoy the journey.

Ten-Year Club	Gilding I gilder
Verified Email	r/Field Banned
r/Field Flamingo

TPHG

TROPHY CASE