mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-18 16:08:56 +00:00
* fix(cli): a project .env provider key gives way to the person's own credential A project .env could set OPENROUTER_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY, the Vertex settings or ELEVENLABS_API_KEY and outrank a credential the person set in their shell or saved settings. The earlier rule covered only received projects; a cloned or downloaded project still won. Now every project .env provider key is unset, with a note naming the file, when a competing provider has a credential from a surer source: the shell or saved settings first, then the person's own project .env, then a received one. A project key with no competing credential is still used, model and timeout settings still apply, and the media-use scripts note an ElevenLabs key from any project .env before speech starts. In the CLI process an own-project key yields only within the vision choice; the media-use scripts remake the Gemini audio choice from the passed key origins. * fix(cli): weigh an own project's provider key only against credentials its feature can use Review found that the global yield removed a person's own project keys where the shell credential could not do the job: snapshot's Gemini key next to a shell OpenRouter key, and a Gemini key that music needs next to a shell service account. - Startup keeps the received-project rule only. - Capture drops a project .env vision key only when the shell or settings hold another complete vision credential; the two Vertex parts are one credential and are not weighed against each other. - A key dropped once is not brought back when capture re-reads the same .env, so its note prints once. - In the audio scripts, an own project's Gemini key gives way only to the other Gemini API key, which speech and music both accept, and an own ElevenLabs key stays for an explicit provider choice.