tailscale / tailscale/aperture-cli
Document working configuration to use Aperture and Gemini provider with antigravity-cli
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 74
- Forks
- 13
- Avg merge
- 1h
- Merged PRs (30d)
- 7
Description
I was able to get Aperture to work with the Gemini provider and the antigravity-cli:
- Follow the Aperture docs to add Google Gemini as a model provider, https://tailscale.com/docs/aperture/how-to/use-google-gemini
- Create the antigravity-cli settings.json file to set the modelProvider as gemini:
mkdir -p ~/.gemini/antigravity-cli && echo '{"modelProvider": "gemini"}' > ~/.gemini/antigravity-cli/settings.json
- Export env to set a fake api key (Aperture will override)
export GEMINI_API_KEY="__aperture_key__"
- Export env to set the base url to your Aperture endpoint
export GOOGLE_GEMINI_BASE_URL="..."
Fwiw: I have had no luck at all finding any client that will work with Aperture using the Google Enterprise Agent Platform (vertex) provider with Gemini models (not Anthropic)...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Aperture Google Gemini documentation and verify the commands and settings.json path described in the issue. Document the working Aperture and antigravity-cli configuration, including the modelProvider setting and required environment variables, so another user can reproduce it.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100