Per-Project and/or Per-Chat scoping for connectors
Connector access is currently global: once a folder is granted in Settings → Connectors, those tools are enabled in every conversation by default, with only an all-or-nothing per-chat toggle in the Tools menu. Please allow scoping a connector's granted directory to a specific Project or specific chats — and excluding it everywhere else.
The problem Projects are described as isolated, encrypted environments for distinct workstreams, but the connector permission model doesn't follow that isolation:
A File Access connector granted for one project's directory is available in every other chat, including unrelated and sensitive ones.
The only mitigation available today is manually disabling connectors per conversation in the Tools menu — an opt-out against an on-by-default setting, which is easy to forget and easy to get wrong.
There is no way to bind, say, Project A to ~/projectA and Project B to a ~/projectB, with neither chat seeing the other's files.
I assume this is true of other connectors which would expose chat information potentially places you don't want. So to be inline with Lumo is "Connect everything, expose nothing" it seems like a change is needed as todays workarounds are (a) grant only the narrowest possible parent folder account-wide, (b) manually toggle connectors off in each unrelated chat, or (c) avoid connectors entirely in mixed-use setups. None of these provide the isolation the Projects feature implies.