voxd
Voice dictation daemon for Linux. Press keybind, talk, press again. Text goes to clipboard.
Install
pip install voxd
Dependencies:
# X11 (dwm, i3, bspwm, etc)
sudo pacman -S ffmpeg xclip
# Wayland (hyprland, sway, etc)
sudo pacman -S ffmpeg wl-clipboard
Setup
Set your Sarvam AI API key:
voxd config set api_key YOUR_KEY
Optional - set language:
voxd config set language hi-IN # Hindi
voxd config set language en-IN # English (default)
Start daemon
Add to your startup:
dwm/i3/bspwm - ~/.xinitrc:
voxd-daemon &
hyprland - ~/.config/hypr/hyprland.conf:
exec-once = voxd-daemon
Keybind
dwm - config.h:
{ MODKEY, XK_semicolon, spawn, SHCMD("voxd toggle --autostart") },
hyprland - hyprland.conf:
bind = SUPER, semicolon, exec, voxd toggle --autostart
Usage
Press keybind → talk → press keybind → paste (Ctrl+V)
Terminal:
voxd toggle # Start/stop recording
voxd toggle --autostart # Start daemon if needed, then toggle
voxd status # Check if recording
voxd logs # Show recent daemon logs
voxd logs -f # Follow daemon logs
voxd logs --path # Print daemon log path
voxd quit # Kill daemon
Config
voxd config list # Show all settings
voxd config set key value # Change setting
voxd config get key # Get value
Settings:
api_key- Sarvam AI key (required)language- Language code (default: en-IN)model- STT model (default: saaras:v3)
Config stored at ~/.config/voxd/config.json
Advanced
WM-specific commands (if auto-detect fails):
voxd-x11 toggle # Force X11 mode
voxd-wayland toggle # Force Wayland mode
Troubleshooting
Daemon not running:
voxd toggle --autostart
voxd status
voxd logs
If voxd toggle says daemon-not-running, either start voxd-daemon from your WM/session startup or use voxd toggle --autostart in the keybind.
No clipboard:
# Install clipboard tool
sudo pacman -S xclip # X11
sudo pacman -S wl-clipboard # Wayland
Wrong language:
voxd config set language hi-IN
voxd quit && voxd-daemon &
Metadata
Release files for voxd 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| voxd-0.1.4.tar.gz | 12.5 kB | Without provenance | Details for voxd-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| voxd-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for voxd-0.1.4-py3-none-any.whl |
Total release size: 26.2 kB
Release files / voxd-0.1.4.tar.gz
| Download URL | voxd-0.1.4.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2617d587f5f4a273347035ef317223b894170479501387add025ad143c1a3134
|
|
BLAKE2b-256 checksum How to use checksums |
76a42e3d3ab618b653418a4413de5a98eee52bf1cc22e7948947c05e76476a7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Release files / voxd-0.1.4-py3-none-any.whl
| Download URL | voxd-0.1.4-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1488a7334a254b9b65c514fab7c479bc748183534280b479bf3b5273745aa44
|
|
BLAKE2b-256 checksum How to use checksums |
6f9d70f64c57833ea4bb517d45e1f840feb9075254ee3060c40ee1cc8b16108a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for voxd 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.