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 Twitch-connected entry

The ordinary yukoe shortcut is the real app. The Manual Test shortcut is deliberately local and cannot receive Twitch chat.

  1. Launch yukoe, not yukoe Manual Test (no Twitch).
  2. Open Settings → Setup Guide. Keep it open: 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. Open Manage, copy the Client ID, create one Client Secret, then follow yukoe's local guide to store them.
Open Twitch Developer Console ↗
03OAuth

Restart fully, then connect Twitch

yukoe loads credentials and starts its local callback listener at launch. Closing the window only hides it, so use the tray when a full restart is required.

  1. After saving credentials, choose Exit yukoe from the system tray, then relaunch the normal app.
  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

One working provider is enough. More providers and advanced routing can wait until the first message works.

  1. In Basic Settings, choose the two languages used by your channel.
  2. Configure one available translation provider by following the local guide. Save and apply the change.
  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

Keep yukoe running, return to the app, and choose Connect or Re-authorize again. Use the newly opened OAuth page; do not refresh an old callback tab. 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.