Support workspace-scoped API provider profiles and settings across VS Code windows #2303

I use zoo-code across multiple projects, and use different providers and/or different models in each. Currently, I cannot work on another project that uses a different model in any mode while one project is running a long agentic task.

Any change in Zoo-code configuration for model providers in any mode is reflected across all open instances in VS code. This is especially disrupting when I switch mode in one vs code instance, and find the mode switched in another instance with a running task.

This happens also with vs code instances connecting to a remote machine over ssh.

I have tried using "zoo-code.customStoragePath" in settings.json, but that does not seem to include changing providers.

I understand the current state as a default behavior, however it would be really helpful to be able to have a configuration parameter that let's me direct all API configurations to the same directory as "zoo-code.customStoragePath" (ideal for my use case) or instruct zoo code to isolate the API and model configuration for each running instance of vs code.

Steps to Reproduce

1. Open two different projects in two separate VS Code windows.
2. Configure a different absolute zoo-code.customStoragePath in each project's .vscode/settings.json.
3. Open Zoo Code in both windows.
4. Change the active API provider or configuration profile in Window A.
5. Observe that the active configuration in Window B also changes.
6. Restart both VS Code windows and repeat. The behavior persists.

Expected Behavior

Each VS Code workspace should be able to maintain its own independent Zoo Code configuration.

Related Issues

#913 – Multi-tab mode isolation
#978 – Isolate parallel mode and provider profile writes