@bpasero just an extension of this would be to add a "save workspace" command. i have read that this isn't desirable in these tickets for whatever reason, but, given the difficulties in efficiently capturing the state periodically, it might be a reasonable means to allow someone to save the state when they know that they really need it captured. without this the only means we have of ensuring the state is saved is to basically create a new workspace. it's about giving control to users to make the editor do something that is probably already being done. i like automation, but i don't think it should prevent a user from asserting control.