Vois v1.4.1: Export credits, CLI and Skills for AI agents, and the stubborn Windows bug

v1.4.1 is out. Here's what shipped and what broke along the way.

The headline feature: Vois CLI and AI agent automation

This one is for the developers and automation folks. Vois now ships a CLI binary inside the app installer. AI agents (Claude Code, Claude Desktop, ChatGPT Desktop, Codex, Cursor, Gemini) can drive it directly.

We host skill files at vois.so/skills that teach agents the full command set: create projects, write scripts, assign voices, generate audio, export with mastering profiles. An agent reads the skill file and knows how to run your entire voice production pipeline from the terminal.

Wrote a longer post about how it works: How AI Agents Control Your Voice Studio

Export credits

The most common question from free-tier users was "I generated this audio and it sounds great, but I can't get it out of the app without subscribing?" Fair point.

So we added export credits. One-time purchases, not subscriptions. One credit equals one export. They never expire.

The subscription still gives you unlimited exports with no credits needed.
Checkout Vois credits pricing.

Better free tier

Free users used to exist in a weird limbo on older versions: local-only state, no way to recover your account on a new machine, and confusing error messages when things went wrong.

Now free users get a proper account. Real license key emailed to you for recovery or second-device activation. If something goes wrong during signup, you'll see a real error message instead of nothing happening. And your account activates automatically, no manual key entry.

We also added a clear lock icon when you hit the free tier project limit, instead of a generic error that left people guessing.

The Windows bug

This one was humbling. We bundle an audio processing tool as part of the export pipeline. On macOS it worked perfectly. On Windows, every export failed.

Turns out: our build system was packaging a 63KB shell script instead of the actual 12MB binary. The real file was sitting in a subdirectory that the build script didn't know about. Outside the build environment, Windows couldn't do anything with a shell script pretending to be an executable.

Then we needed to track down 14 additional library files the binary depends on. Our collection script was looking for file paths in the wrong format. Six commits and a lot of cross-platform debugging later, Windows exports work.

Also fixed: Command Prompt windows flashing whenever you export or process audio on Windows. Small thing, but it made the app feel broken.

Other fixes

• macOS home screen buttons not responding to clicks

• Export success screen replaced with a "Show in Folder" button

• App could freeze on the home page under certain conditions

If you've been trying the free tier or the CLI, what's your experience been?