Troubleshooting

Start here

Four causes account for most problems. Check them in this order.

Wrong workspace. Personal and organisation data are entirely separate. Check the switcher. More →
Not switched on for your account. Kyra is in alpha and features roll out per account, plan, and platform. Ask Kyra “can you do X?” — it should say what is missing.
A device permission was refused or reset. Check your phone’s Settings under Kyra.
A different account. The app, the portal, and kyra on your machine must all be signed in as the same account.

Voice

Kyra cannot hear me. Check the microphone permission. Then check whether push-to-talk is on — if it is, you have to hold the button.

No sound from Kyra. Tap the orb on the live screen. Phones and browsers often require a deliberate tap before they will play audio. Then check the volume and whether audio is routed to something else.

Kyra keeps mishearing a name. Add it in Portal → Settings → Key terms. More →

Recognition is poor in a noisy place. Turn on push-to-talk, get closer, use a headset, or type it.

Kyra interrupts me / does not wait. Push-to-talk gives you exact control of when your turn ends.

The session dropped. Kyra reconnects automatically and shows a status bar. The transcript up to that point is kept.

Notes

A note I dictated is not there. Check the workspace, then ask “where did you save that?” — Kyra names the notebook when it saves, and it may not be the one you assumed.

My notes are gone from this device. A local: browser notebook only exists in the browser that made it. Cloud notebooks sync; local ones do not. More →

An equation renders as red text. A $$ block nested inside another $$ block. Fix →

A wiki-link does not resolve. Links are notebook-relative paths without .md. Use the [[ picker to get it right rather than typing the path.

Unsaved changes vanished. Drafts survive switching tabs but are not committed until you save. Save early — every save is a commit, so there is no cost to saving often.

Tasks

A task is stuck. Ask “what are you working on?” A task waiting on a service will resume; one that says needs you is waiting for your decision.

A task finished and I was not told. Turn on notifications.

I did not get a result. Check the queue. Ask “what went wrong?” for a summary of recent failures.

Your machine

Kyra says nothing is running. In order: is kyra connect still up? Are you online? Is a session actually running — and was it started in a plain terminal, which Kyra cannot see? More →

Kyra sees my editor but no coding sessions. Mediation is separate and opt-in. Run kyra install vscode, then reopen the sessions — it applies at launch.

No Kyra item in the VS Code status bar. The extension attaches to the local door, which kyra connect starts. Start the daemon.

kyra login will not approve. Sign in to the portal as the same account and check the code matches.

Nothing works on Windows. Everything must run inside WSL, with VS Code attached to the WSL remote — the title bar should show [WSL: <distro>]. Why →

“address already in use”. A previous run was killed hard. Starting again usually clears it; if not, remove ~/.kyra/bridge/uap.sock.

A provider cannot connect. Check the door is running and that the provider read the current token — it is regenerated on every start.

kyra bridge says it has no binary to run. You are running the CLI from a source checkout rather than an installed tarball. Install it normally.

I edited settings.json and nothing changed. Under WSL, the file that decides it is the remote one.

Account and billing

A feature is missing. Plan gate, or not rolled out yet. Kyra should open the billing page if it is a plan gate.

Credits are going faster than expected. Check which workspace you have been working in — organisation work draws on the organisation’s pool, not yours.

The billing page and Stripe disagree. Believe Stripe. Its confirmation screen is binding.

I cannot buy top-ups. Free accounts cannot. Subscribe first.

Reporting a problem

“File a bug: the queue screen doesn’t refresh after a task finishes.”

Kyra captures it in your words with the device context attached and routes it onward.

For anything involving your machine, include the output of:

kyra version

Both the version and the build stamp — together they identify exactly which build ran.