Prerequisites
Toolbox version
0.21.0
Environment
No response
Client
Expected Behavior
When multiple extensions are enabled and given a prompt via the Gemini CLI, the validation for one extension should not affect the others.
If I have Spanner enabled with all necessary environment variables set, I should be able to query Spanner successfully, even if the AlloyDB extension is enabled but lacks its environment variables. The missing AlloyDB configuration should only trigger an error if I specifically try to access an AlloyDB tool.
Current Behavior
The AlloyDB extension acts as a blocker for all other tools when running via Gemini CLI.
When AlloyDB is enabled alongside other extensions (like Spanner or Cloud SQL), if the AlloyDB environment variables are missing and available for other extensions, the CLI returns a generic API Error for any request made for other extensions.
This happens even when:
- Other extensions are enabled.
- Environment variables for those other extensions are correctly set.
- The user explicitly queries the configured database (e.g., "List tables in Spanner").
The configured and valid extensions become unusable simply because the AlloyDB extension is present without its credentials.
Screenshots attached for reference
Spanner (Configured) + AlloyDB (Unconfigured) -> Fails (Spanner is blocked).
Spanner (Configured) + Cloud SQL Postgres (Unconfigured) -> Works (Spanner is accessible).
Spanner (Configured) + AlloyDB (Configured) -> Works
Steps to reproduce?
- Run the Toolbox using Gemini CLI with Spanner and AlloyDB extensions enabled.
- Export valid environment variables only for Spanner (SPANNER_INSTANCE_ID, etc.).
- Do not export environment variables for AlloyDB.
- Send a prompt regarding the configured Spanner DB: "List tables in Spanner or list tables"
- Result: API Error (The valid Spanner configuration is ignored/blocked).
Additional Details
Observation: The error resolves immediately if the AlloyDB environment variables are added (even if not used in the query).
Prerequisites
Toolbox version
0.21.0
Environment
No response
Client
Expected Behavior
When multiple extensions are enabled and given a prompt via the Gemini CLI, the validation for one extension should not affect the others.
If I have Spanner enabled with all necessary environment variables set, I should be able to query Spanner successfully, even if the AlloyDB extension is enabled but lacks its environment variables. The missing AlloyDB configuration should only trigger an error if I specifically try to access an AlloyDB tool.
Current Behavior
The AlloyDB extension acts as a blocker for all other tools when running via Gemini CLI.
When AlloyDB is enabled alongside other extensions (like Spanner or Cloud SQL), if the AlloyDB environment variables are missing and available for other extensions, the CLI returns a generic API Error for any request made for other extensions.
This happens even when:
The configured and valid extensions become unusable simply because the AlloyDB extension is present without its credentials.
Screenshots attached for reference
Spanner (Configured) + AlloyDB (Unconfigured) -> Fails (Spanner is blocked).
Spanner (Configured) + Cloud SQL Postgres (Unconfigured) -> Works (Spanner is accessible).
Spanner (Configured) + AlloyDB (Configured) -> Works
Steps to reproduce?
Additional Details
Observation: The error resolves immediately if the AlloyDB environment variables are added (even if not used in the query).