Tag library per location option

I have a situation where I am working on multiple locations for several different clients each using different tag libraries for each client. The system seems to assume that the tag libraries are the same across all folders or all locations but now when are using TagSpaces not only to connect to local folders as sources but I for example am using S3 buckets and other online storage systems from multiple clients. This means the the integrity of the tag libraries get muddied and duplicate tag colors get mixed when loaded, or new tags get missed when I save them to the wrong export.

I am currently exporting the tags generated during my work in to the location folder at the end of each session and then I either have to delete out the tag groups or load a whole new version to get a clean slate for the next client session. This is painful and mistakes are made overtime! I love product but it is hard to scale something like this since it seems to be design for individual use per system. What I really need is the ability to clear the tag library system completely in order to cleanly import a new tag library. The best option would be the ability to auto-load new tag libraries stored in the location folder when new location folders are chosen as this would load the correct tag libraries used for each location folder.

Why not using different portable versions of TagSpaces for each customer?

I am not sure if I understand your suggestion. Particularly the portable aspect as I think you mean instance. I have one instance of your latest software version running on my machine which allows me to working from a centralized place since the setting are previously configured. Loading a new instance would just create a new blank version which I would have to not only regenerated my settings, but locations, and tag libraries. My objective is to simplify my workload in a centralized place not create more for each time I move to new clients through out the day or am I missing something?