Initialization guide

From first launch to your first translated message.

Five calm checkpoints. Start private, verify each connection, and let yukoe speak in Twitch chat only when you decide it is ready.

Start the five checkpoints ↓ Something is not working
≈ 10 minfor a first private translation
5clear checkpoints, in order
Privateuntil you explicitly enable posting
Before opening anything

Bring four small things.

You do not need to understand OAuth or edit every option. The app's own Setup Guide will show the exact values for this installation.

Have these ready

  • ✓The normal yukoe Windows app or a running source checkout.
  • ✓Your Twitch channel login, written exactly as it appears in the URL.
  • ✓A Twitch account with verified email and 2FA for the Developer Console.
  • ✓Optionally, a separate bot account if translations will be posted publicly.
The short path

Complete these in order.

Each checkpoint ends with something visible you can confirm. If that result is missing, stop there and use the matching fix below.

01Correct app

Open the one normal app

Extract the complete Windows archive and open yukoe.exe. There is no separate no-key launcher or configuration command file.

  1. Double-click yukoe.exe. An unconfigured first launch opens setup automatically.
  2. If needed later, open Settings → Setup Guide. It adapts every instruction to the running installation.
  3. Confirm the source badge does not say TEST or MANUAL.
02Twitch app

Register one Twitch application

This gives your local app permission to ask Twitch for chat access. The callback must match character for character.

  1. Sign in to the Twitch Developer Console. Verified email and 2FA are required.
  2. Register an application and paste the exact OAuth callback URL shown in yukoe's local Setup Guide. Do not copy a guessed port from a tutorial.
  3. On the same application's Manage page, copy its Client ID and choose New Secret once. Paste that latest pair into yukoe; creating another secret immediately invalidates the previous one.
Open Twitch Developer Console ↗
03OAuth

Save, restart, then connect Twitch

The same local form stores secrets with Windows DPAPI and restarts yukoe for you. Saved secret values are never displayed back.

  1. Choose Verify with Twitch, save & restart. yukoe checks the ID/Secret pair with Twitch before writing anything, then resumes at OAuth.
  2. Choose Connect Twitch. In the browser, confirm you are authorizing the intended bot account.
  3. Return to yukoe and look for Twitch Connected plus the expected channel name.
04Translation

Choose one translation path, privately

No translation API key is required. Start with Free translation, or add your own provider key in the same form.

  1. In Basic Settings, choose the two languages used by your channel.
  2. Enable Free translation, or add a Google Cloud / Gemini key in yukoe. You can replace or add a key later.
  3. Keep Viewer delivery on Only me, inside yukoe. Confirm the provider status says ready rather than setup.
05Real message

Prove the full path with real Twitch chat

A real message validates the account, channel, EventSub connection, language route, and provider together.

  1. From another Twitch account, send one ordinary message in the source language. Do not use yukoe's Manual Test input for this acceptance check.
  2. Confirm the same display name and Twitch name color appear in yukoe, followed by the translated line.
  3. Only after checking quality, optionally enable TTS or choose Everyone in Twitch chat and send one controlled public test.
  4. Use Focus chat when streaming. It transforms this same movable window and can be pinned or unpinned at any time.
What success looks like

Three green lights, then stop configuring.

You do not need to finish Advanced Settings before a stream. These three results are the useful finish line.

Connected

Twitch is listening

The source is LIVE, the intended channel is named, and new real messages arrive.

Translated

The route works

An original message and its correct translated line appear together.

Private

Nothing was posted by surprise

Viewer delivery remains private until you deliberately change it.

Quick diagnosis

Fix the first missing checkpoint.

Do not change five settings at once. Find the earliest result you cannot see, make one correction, and check again.

No Twitch messages arrive

Confirm you launched the ordinary shortcut, the source says LIVE, the channel login is exact, and OAuth used the configured bot account. Manual Test never connects to Twitch.

The OAuth callback fails

Do not refresh the old callback tab. If Twitch rejects the Client Secret, return to Setup Guide, copy the Client ID from the same Manage page, create one New Secret, and let yukoe verify the latest pair. Otherwise choose the callback page's fresh-authorization button and recheck the exact callback URL.

Messages arrive but do not translate

Confirm translation is on, the provider says ready, and the source/target languages include the message. Start with one provider before adjusting the engine chain.

Translation works but TTS is silent

Turn TTS on, select the intended output device, and check the speech queue state. TTS is optional and independent from translation.

Optional free-tier upgrades

Get each provider key without guessing.

These dedicated guides use the providers' current official instructions and show exactly where each value belongs in yukoe. This website never asks for a key.