Hi, just to confirm what I’m suspecting, I suppose there’s no way to make some UI settings permanent?
In the Instances page, I like to add the Memory column but I have to add it again every time.
As I use the Temporary containers extension in Firefox which creates empty (ie: cookies and stuff) tabs every time, I suppose that’s the reason why I have to set the Memory column every time?
It’s no big deal but if there’s a way to have this column set by default, I’d like to know how 
yeah, that’s correct. I think the UI uses some amount of local browser storage, but your extension would be wiping all the clean.
The current Incus UI is just pretty light fork of the LXD UI which is hosted by Zabbly and included in some distributions. It’s not considered as an official part of Incus.
We’re looking at changing that in the near future with a completely fresh implementation. Currently the top contender is the work from @Hye-Dev. I’m mentioning it because once we do have an official UI project we’ll be able to tie Incus and Incus UI a bit more together, including having ui.XYZ configuration keys on the Incus side allowing for the default behavior of the UI to be controlled that way, avoiding having to configure all systems the same way manually.
In one of my test VMs for Incus, I’ll try to monkey-patch the UI files on disk and pre-select the Memory field to see if it’s active when accessing the UI. I’ll report my results back.
I’ve see the Hye Ararat UI project and plan to test it.
The new data fetching layer I’m working on in the Ararat “re-write” uses IndexedDB for storing/caching information. There are just 2 cookies, one representing the currently selected project, and another for the color scheme (dark / light mode).
I currently haven’t implemented any client-side storage for table settings, however, I think this is a good idea to include. Luckily Ararat currently displays resource consumption information by default on the Instances table (data is fetched only for what’s is in view, so it’s not a problem for the Incus host even if you have lots of instances, I suspect this is why it’s not default on the Canonical UI, but I haven’t looked at their code so not sure). I’ll be re-writing the table component as well in the next release, so lots of room for improvement there.
I’ll be sure to add user.ui (ui.* if those get added!) keys for setting the default values of these options when I do!
also thinking I should make project-specific keys. That way confined users can configure default settings & one can have different views for different projects 
ideally there would also be a way to store persistent settings on the user-level. definitely could do it by storing keys on the authenticated TLS cert. will have to explore more creative approaches for the other providers.