UI discards unsaved changes

[MikeWallis42]

When you have multiple tabs open in the UI, if you modify one of them (without saving) then switch context and back again the UI seems to re-load what is saved to disk and discards your changes.
Often, whilst developing, you need to go and physically look at upstream models and then go back to complete what you're writing... often with partially constructed SQL having been written that sqlmesh/sqlglot would not be able to parse if you tried to save it.

This particular behaviour puts a lot of people off using the UI for writing SQL although we still heavily use it for lineage, documentation and even planning whilst developing.