Getting Discord into the headset.
HUD-off driving works best when the useful information reaches the same place as the engine sound. Depending on the headset, Android speech and console audio do not simply mix themselves. That is why the optional Discord route matters.
LapMind uses your own bot in your private voice channel. There is no hosted LapMind voice service in the middle. The one-time setup is real work, so the instructions need to be ordinary instructions—not a collection of hints for someone who already knows Discord.
There are now two native guides in the app: Discord beginner guide and PS5 / PS5 Pro Discord guide. The first covers the application, bot, token and destination. The second covers linking the personal Discord account to PlayStation, joining the channel and checking the headset path.
Beta37 gives those guides a compact home on the Companion screen instead of repeating a five-step Quick Start beside them.
The important order is simple: connect the bot, join the same voice channel with your normal Discord account, then choose Test voice in LapMind. Confirm that you actually hear: “Discord connected. Voice test successful. Hopefully.”
Connected describes a software state. It is not a microphone check, an audio-mixing guarantee or proof that a person heard anything. LapMind does not request microphone access. Local Android speech remains independent.
The Discord route has worked in previous physical use. The exact current candidate still needs its PS5 / PS5 Pro end-to-end recheck. I am keeping that distinction instead of borrowing certainty from an older build.