The hardware (Pico or piglet) should save the config and provide it to the UI, on remote connections to piggui.

However, if piggui is running on a device (Pico) with GPIO hardware itself, then it should be saving that to file, the same as piglet does when running on the same device.

I'd argue that if you use pigglet, and then stop it and switch to piggui, that it should pick up the config from the same files, and vice versa.

Piggui might need to check that a piglet is not running already on the same device when it starts up, and either:

• exit
• warn the user, tell them to stop piglet
• gracefully connect to the running piglet in the background? (have discovery recognize that the piglet discovered is running on the same hardware as the GUI?)