Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds first-class OpenAI and Gemini chat support alongside the existing Claude integration.
The main goal was to keep the macOS app's voice flow unchanged while making the chat layer provider-agnostic. The app can now route multimodal screenshot + transcript requests through the Cloudflare Worker to Claude, OpenAI, or Gemini using a shared request/response shape.
What Changed
claude-sonnet-4-6claude-opus-4-6gpt-5.4gemini-2.5-flashCompanionManagerto use a model-agnostic chat pipeline instead of a Claude-specific one/chatroute to support:generateContentWhy
The existing app flow was tightly coupled to Claude. This change keeps the user-facing interaction model the same while allowing Clicky to switch between major multimodal providers with minimal client-side branching.
That makes it easier to compare model behavior, keep provider flexibility, and continue evolving the app without hard-coding one vendor into the primary chat path.
Notes
New worker secrets required:
OPENAI_API_KEYGEMINI_API_KEYExisting secrets still required:
ANTHROPIC_API_KEYASSEMBLYAI_API_KEYELEVENLABS_API_KEYTesting
I did not run
xcodebuildbecause the repo instructions explicitly say not to run it from the terminal due to TCC permission resets.Static validation performed:
git diff --checkFollow-ups
Potential follow-up work, if desired: