Add default project name field to gemini-cli settings

[netham45]

Related GitHub Issue

Closes: #5177

Description

This adds the default project name as a user-customizable field in settings. If this is set by the user the user will be able to use paid tiers of Gemini Code Assist,.

Test Procedure

I have a 'Standard' tier gemini code assist plan on a personal account. Without this set I am unable to make any requests from the account like how an unlicensed account can, every request gives a 403 and says it is not using a valid project. Once I set a project name that has a Google Gemini Code Assist Standard license applied in the field it then works.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

• No documentation updates are required.

Additional Notes

Get in Touch

netham45

---

Important

Add geminiCliDefaultProject field to Gemini CLI settings for user-customizable default project name.

• Behavior:
  • Adds geminiCliDefaultProject field to geminiCliSchema in provider-settings.ts for user-customizable default project name.
  • Updates GeminiCliHandler in gemini-cli.ts to use geminiCliDefaultProject as initial project ID.
• UI:
  • Adds input field for geminiCliDefaultProject in GeminiCli.tsx.
• i18n:
  • Adds defaultProject and defaultProjectDescription translations in settings.json.

^{This description was created by for 34a4e2e. You can customize this summary. It will automatically update as commits are pushed.}

[netham45]

Please note that I was unable to test this on a free plan as I don't have a google account on the free plan available.

[daniel-lxs]

Hey @netham45, thank you for your contribution!

I left a question regarding the current Gemini CLI project ID field.
Curious to hear your thoughts on it!

[daniel-lxs]

I'm wondering if we could simplify this by using the existing geminiCliProjectId field for both purposes instead of adding a new field?

The approach could be:

1. If geminiCliProjectId is set, use it as the initial value for discovery
2. If discovery succeeds and returns a different ID, update to use that
3. If discovery fails, fall back to using the provided value directly

This would avoid having two fields that serve similar purposes, which could be confusing for users. They would just set their Google Cloud Project name in geminiCliProjectId, and the discovery process would handle converting it to the proper format if needed.

What do you think? Would this approach work for the paid tier use case you're addressing?

[hannesrudolph]

There is no longer a gemini cli provider. Closing. thank you for your contribution.