Install with an agent

Paste one prompt into Claude Code, Codex or any agent that can run terminal commands. The agent installs Voisu, starts it and checks it. You type your API keys and approve the desktop's prompts yourself.

Your API keys never go in the chat. The agent won't ask for them. When it's time, you type them into Voisu's own setup: voisu setup in a terminal of your own on Linux, or the settings window on Windows. If you paste a key into an agent chat by mistake, revoke it in the provider's console and create a new one.

The prompt

This one works on any supported system. The agent detects your OS and distribution first.

Paste into Claude Code, Codex, Cursor or another terminal agent

Install Voisu on this computer: read https://anuraj-dev.github.io/voisu/agent-install.md and follow it step by step. Never ask me for API keys in this chat; I'll type them into Voisu's own setup.

Before you start, create an API key at Groq and one at Deepgram. Providers & API keys explains why Voisu uses both.

A prompt for your system

If you'd rather skip detection, use the prompt for your system. Each one points the agent at that system's section of the same guide.

Fedora

Fedora · KDE Plasma or GNOME on Wayland · COPR

Install Voisu on this Fedora computer: read https://anuraj-dev.github.io/voisu/agent-install.md and follow the Fedora section step by step. Show me each sudo command before you run it. Never ask me for API keys in this chat; when the guide says so, I'll run voisu setup in my own terminal.

Expect to approve: sudo for the package install, then your desktop's shortcut dialog when the daemon first starts.

Arch

Arch Linux · AUR

Install Voisu on this Arch computer: read https://anuraj-dev.github.io/voisu/agent-install.md and follow the Arch section step by step. Ask me before installing anything that isn't in the guide. Never ask me for API keys in this chat; when the guide says so, I'll run voisu setup in my own terminal.

Expect to approve: the AUR install, then voisu setup. On Hyprland, setup also binds your Trigger Key.

Debian / Ubuntu

Ubuntu 26.04 LTS · GNOME Wayland · amd64

Install Voisu on this Debian/Ubuntu computer: read https://anuraj-dev.github.io/voisu/agent-install.md and follow the Debian / Ubuntu section step by step. Check the signing key fingerprint before adding the repository, and show me each sudo command before you run it. Never ask me for API keys in this chat; when the guide says so, I'll run voisu setup in my own terminal.

Expect to approve: sudo for the repository and package, then voisu setup. Setup may ask you to log out and back in.

Windows

Windows 10 / 11 · x64 · PowerShell

Install Voisu on this Windows computer: read https://anuraj-dev.github.io/voisu/agent-install.md and follow the Windows section step by step using PowerShell. Never ask me for API keys in this chat; I'll type them into Voisu's settings window.

Expect to approve: SmartScreen's More info → Run anyway (the installer isn't code-signed yet), then the installer itself. No admin rights are needed.

What the agent does, what you do

StepAgentYou
DetectReads your OS, distribution and desktop session.Nothing.
InstallRuns the package commands, or downloads the Windows installer and starts it.Approve sudo, or click through SmartScreen and the installer.
StartEnables Voisu's user service on Linux.Pick your Trigger Key if your desktop shows a shortcut dialog.
KeysTells you when it's time. Never sees them.Run voisu setup in your own terminal, or use the Windows settings window.
CheckRuns voisu doctor and checks both keys with their providers.Make one Recording and confirm the words landed.

Run voisu setup in a separate terminal window, not through the agent. It opens Voisu's setup screens, which hide your keys as you type and need a real terminal. Afterwards, voisu shows whether Voisu is ready.

The guide the agent follows

Every prompt points to one plain-text file: agent-install.md. It lists the exact commands for each system, the checks that prove the install worked, and the points where the agent must stop and hand over to you. Read it before you paste the prompt. An agent will run what that file says.

For tools that index sites for language models, llms.txt lists these docs and the guide.

If the agent gets stuck, it should stop and show you the error. Troubleshooting and voisu doctor --verbose cover the usual causes.