Are you using the client-side editing paradigm, where the files on your VS Code workstation are managed with, say, Git, and imported to an IRIS server for execution? Or are you using the server-side editing paradigm, which is equivalent to the IRIS Studio way of working?

Also, please explain why you don't want the storage information in the class file.

I agree that source control is a good way of tackling the "who changed it, when, and why?" questions.

If you haven't already, please take a look at Deltanji from my company, George James Software. LUTs are treated the same way as Classes, Routines, Schemas and many more component types. Deltanji operates natively inside all InterSystems platforms, including HealthConnect, dealing with deployment as well as versioning.

I'm guessing you are using the client-side editing paradigm, creating a new Foo/Bar.cls file (probably in the src subfolder of the folder you opened in VS Code), defining Foo.Bar as a subclass of %Persistent. Then when you save it VS Code imports the class into the namespace of the server your configuration connects to. When it compiles this for the first time the server adds the storage definition. VS Code should automatically reload the updated class definition into your local file.

When you begin a debugging session VS Code by default saves modified documents before launching server-side execution of your code.

None of this should produce the symptoms you reported. I recommend moving the investigation to the extension's Issues section in its GitHub repository. A good way of opening an issue there is to begin at the Report Issue option from VS Code's Help menu. This will automatically include version information in the report. You can't paste screenshots or animated GIFs into that dialog but it's easy to edit the issue description on the GitHub page that opens after the dialog closes.