Yandex-Claude-Assistant
Say "Клод", ask a question, get a spoken answer — all from the speaker itself, with only the LLM/TTS calls leaving the device (through your own VPN).
- Custom firmware
- Alpha
- High brick risk
- Reversible
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
Before you start
- How hard is it?
- HardUses the command line or developer tools.
- What you need
- Comfort with the command line
- A computer
- Can it break my device?
- Could leave your device unusable. It may void your warranty.
- Can I undo it?
- Yes. You can go back to the official software.
Did it work for you?
Did Yandex-Claude-Assistant work on your Yandex Station?
No reports yet.
One-tap reports from owners. Bricked reports are checked before they count.
Compatibility
Devices: Yandex Station.
No compatibility information yet.
Getting started
From the project's README ("Install (on-device layout)"):
/bkupgrade/data/ai/ claude-ask claude-say # Rust helper binaries key.txt elkey.txt # YOUR API keys (chmod 600) — never in git /bkupgrade/data/stt/ klod # the assistant libvosk.so model-ru/ # Vosk runtime + model /data/xray/ xray config.json # VPN core + YOUR vless config — never in git /etc/init.d/ S02zram S98xray S99klod # autostart (see device/init.d/)
Keys & secrets
No keys, tokens or VPN configs are committed to this repo, and you must supply your own:
- key.txt — Anthropic API key (sk-ant-...)
- elkey.txt — ElevenLabs API key
- /data/xray/config.json — your Xray/Reality (vless://) outbound
Keep them chmod 600 on the device. They are listed in .gitignore.
Risk and recovery
- Brick risk
- High
- Reversible
- Yes
- Voids the warranty
- Yes
- Requires opening the device
- No
From the project's README ("Notable hacks"):
- Amp master-clock fix. After stripping the stock Yandex userspace, the speaker played everything 3× too slow with an 8 kHz "telephone" sound. The vendor audio driver programs the TDM correctly for 48 kHz but ends up selecting an MPLL that is 3× too low, so the real mclkb is 4.096 MHz instead of 12.288 MHz. The fix pins EEAUDIO MCLKBCTRL (0xFF642008) to 0x83000001 (mux = mpll3 ÷2) via /dev/mem. It is not persistent (a reboot reverts it) and the driver rewrites it on every stream open, so a small holder thread keeps it correct during playback. See voiced/clkhold/ and docs/.
- zram swap. The Vosk model needs ~157 MB peak at load; on a 240 MB / 0-swap box that OOMs. S02zram brings up a 160 MB compressed swap device so it fits.
- Program-only rollback. bootswitch + a minimal Alpine rescue rootfs give a one-shot dual-boot with watchdog/panic safety nets — no UART needed.
Credits, license and support
- License
- MIT