Short-lived credential
TranslateMe sends the Session-Only API Key to the production backend only to create a short-lived OpenAI realtime credential for the active translation session.
Sign-in starts in the extension popup.
Production setup guide
Load the TranslateMe Chrome extension, route translated audio through VB-Audio Virtual Cable, and use your own OpenAI key for one active translation session.
This site explains setup and receives auth callbacks. It does not start sign-in, manage your account, or start translation.
Extension installation
Confirm Windows shows CABLE Input as a playback device and CABLE Output as a recording device after installation.
In Chrome extensions developer mode, load the repository's extension folder and keep the popup available in the toolbar.
Select your physical microphone as the input and CABLE Input as the translated audio output.
Call-platform audio routing
The extension plays translated speech into CABLE Input. Your original physical microphone should stay selected only inside the TranslateMe popup.
Set Google Meet's microphone to CABLE Output so the far participant receives translated audio from the virtual cable instead of the original microphone stream.
Session-Only API Key
TranslateMe sends the Session-Only API Key to the production backend only to create a short-lived OpenAI realtime credential for the active translation session.
TranslateMe does not store, does not fingerprint, does not resell, and does not echo your OpenAI API key in diagnostics or responses.
After setup succeeds, the key field is hidden after setup succeeds and the key remains only in volatile active-session memory until Stop, sign-out, failure teardown, or runtime key loss.
Auth boundary
Sign-in starts in the extension popup for Google Sign-In and Email Magic Link flows. This hosted site only receives the provider callback and returns the result to the extension flow.