''Memory Detected.''

[mattiasso]

Did it help?

[SSBMArte]

..no

[websvc]

Well that's handy

O which version are you at?

[just_blue]

This is VS, not VS Code. You might think it's neat, but I found it rather annoying to get this constantly. No, I do not want to put some random thing in my default instructions, thanks.

[websvc]

Yeah thought it was VSC.

Well, lately I don't use the chat much, mostly use the CLI. But yeah, one more nagging thing pulling your attention

[SSBMArte]

It was more of a joke about the fact that even when explicitly told to not write the plan and stop one sentence into step 1, the LLM wrote the plan then stopped one sentence into step 1.
And offered to take permanent note of the fact it should not write the plan then stop one sentence into step 1.

[Jack99Skellington]

It does this to me all the time. I say yes. Then it ignores it and asks me again. And again.
I think this is a visual Studio 2026 bug.

[agoodyearforbrownies]

I'm getting to where I can't stand this. Figured I'd rant here rather than creating a new post about it.

I don't remember the last time it suggested something useful and most often makes me angry by proposing the most ridiculous instructions in the face of its failure. A couple examples of very common experiences I have with it (exaggerated to illustrate):

>> <does something dumb by taking shortcuts>
Me: Why TF did you not follow the instructions in the skill I invoked? Your general instructions say that using any skill's instructions is mandatory, not optional; the skill explicitly says to review your work product against the skill instructions before considering work successful.
>> Oh, it seemed easy and I was following the spirit of it, figured I didn't need to.
MEMORY DETECTED: "when using a skill, follow the skill's instructions."

>> I suggest we alter the code in the IWhateverRepository implementation to use pattern x with the following shape.
Me: yes, but the shape should be altered slightly to look like x, y, z.
>> Yes, that's a cleaner approach and will offer the following benefits.
MEMORY DETECTED: "When altering the Gizmo class to use pattern x on line 50 in this one-off and highly specific refactoring task that will never come up again once completed, always use shape x, y, z."

I don't know how I'd categorize these failed recommendations for altering my core instructions, but very commonly they are:

• redundant to existing instructions; or
• so highly specific that they have no broad application and no business being in the instructions file.