Currently, when adding a connection to the Gemini CLI provider via OAuth, the projectId field, stored in providerConnections.data, appears to be determined or assigned automatically; there is no option in the user interface to specify it manually during configuration.
Problem:
Google accounts are linked to GCP projects, or the automatically determined project is not the one the user wishes to use for requests. At present, the only way to resolve this issue is to manually edit the SQLite database directly (UPDATE providerConnections SET data = json_set(data, '$.projectId', '...')), which is an unreliable process and not accessible to most users.
Request:
Please add a field in the user interface (for example, on the provider connection editing screen or during the OAuth setup process) that allows users to manually enter or override the projectId for connecting to the Gemini CLI without needing direct access to the database.
Currently, when adding a connection to the Gemini CLI provider via OAuth, the
projectIdfield, stored inproviderConnections.data, appears to be determined or assigned automatically; there is no option in the user interface to specify it manually during configuration.Problem:
Google accounts are linked to GCP projects, or the automatically determined project is not the one the user wishes to use for requests. At present, the only way to resolve this issue is to manually edit the SQLite database directly (UPDATE providerConnections SET data = json_set(data, '$.projectId', '...')), which is an unreliable process and not accessible to most users.
Request:
Please add a field in the user interface (for example, on the provider connection editing screen or during the OAuth setup process) that allows users to manually enter or override the projectId for connecting to the Gemini CLI without needing direct access to the database.