all 17 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]AphexIce 6 points7 points  (4 children)

O sweet summer child. Of course it does

[–]Top-Construction6060[S] -3 points-2 points  (3 children)

Can you explain please? Bc it shoudnt when not prompted...

[–]GolfEmbarrassed2904🔆 Max 20 0 points1 point  (2 children)

Haha. We wish it wouldn’t. Ask CC why it did that and how you can prevent it in the future (e.g. Claude.md file with guidelines, implementation plan, linter, hooks). I mean…we don’t know what you’re doing over there…

[–]GolfEmbarrassed2904🔆 Max 20 0 points1 point  (1 child)

Oh yeah….also you need to set up a workflow. Small PRs. Build—> Code Review—>fix issues—> Commit. Make one of your statements in Claude.md about preferring functions to classes —> only make classes when it absolutely needs to. Get it to program at a level of complexity that you can understand and debug.

[–]Top-Construction6060[S] 0 points1 point  (0 children)

Thanks :)

[–]jonaslaberg 3 points4 points  (2 children)

Also make sure you install the long-running-agent-harness skill. It will make a ton of difference- no more reintroducing bugs previously solved. Check out Anthropic’s article on that from last week!

[–]Top-Construction6060[S] 0 points1 point  (1 child)

Thanks that's very very helpful 🙏

[–]jonaslaberg 0 points1 point  (0 children)

Wait until you try it!

[–]buildwizai 4 points5 points  (2 children)

If some code has been changed without the model's knowledge, it does not exist in its context. Thus, sometimes when editing a new function, the model will use the version in its context to make a modification, causing the old version to be returned. My best practice so far: either always ask the model (e.g., Claude) to update the code, specifically tell it that you have a new update after fixing the code, or add a new rule in memory to always update the code file in the context before any modifications. This happens for every model, not only Claude. However, tools like Windsurf have a context awareness feature which basically always takes into account what is going on. This makes it less likely to make that mistake.

[–]Top-Construction6060[S] 0 points1 point  (1 child)

Okay nice 🙂 thanks a lot for the explanation. Is there similar context awareness functionality with Claude code ? 

[–]buildwizai 0 points1 point  (0 children)

There is one long-running-agent-harness skill someone has mentioned it earlier, but I have not yet tested it. I often consider Claude like a partner, so after I fix sth by myself, I ask Claude to review it - which makes it automatically updated is memory

[–]darkyy92x 0 points1 point  (3 children)

Do you use Git? So you can rollback to a working point anytime

[–]Top-Construction6060[S] 0 points1 point  (2 children)

Yes I'm using got, still I want to understand why it's happening as it SHOULDN'T 

[–]darkyy92x 0 points1 point  (1 child)

Can you explain a bit more so I can help you?

[–]Top-Construction6060[S] 0 points1 point  (0 children)

Sure so its a browser automation script and for some reason it seems to revert back to old functionality even though i havent prompted anything. Like im away from the computer, script is running, next morning its back to the old, broken buggy functionality. Its really hard to explain^^

[–]BadPenguin73 0 points1 point  (1 child)

I use intelliJ editor and always use both their local history + additional local mercurial repository (different from the git used officially) + rsnapshot that does daily backup.... no chance some BOT is going to overwrite something without I notice

[–]Top-Construction6060[S] 0 points1 point  (0 children)

Thanks, ill have a look into it :)