Free Plaud Alternative Runs Local Transcription Skill

A developer on r/openclaw built a free replacement for the subscription tier of the Plaud recording device. The setup is three parts: an app, a skill, and a cron job — all written in a few hours with Sonnet 5.5, and all running against local models instead of the paid cloud service.

What It Replaces

Plaud's subscription runs $239.99 per year. The author's goal was to replicate the download-and-transcription pipeline (presumably: pull recordings off the device, transcribe them, store the results) without paying that fee. The key constraint: all local models, no cloud inference.

The Three Components

App — handles the download and transcription flow.
Skill — the agent-facing piece, so the coding agent can invoke the pipeline.
Cron job — runs on a schedule so new recordings get processed automatically without the user kicking it off manually.

That's the whole design. No fine-tuning, no custom model, just orchestration of existing local models plus a scheduler.

The Useful Part: Local Transcripts Are Queryable

The output is the interesting bit. Transcripts land directly on the local machine as files:

"Transcripts save to my local machine. I can query the folder to search across all past meetings for whatever I want to find."

That means one grep-style search across the transcript directory covers every past meeting — no vendor UI, no per-query cost, no data leaving the machine. This is the standard argument for local transcription pipelines: once the text is on disk, you own the index and can build whatever retrieval layer you want on top of it.

Build Notes

Built with Sonnet 5.5 in a "vibe coding" style session.
Total effort: a few hours.
Runtime: local models only, no subscription dependency.
Author reports being "happy with the result."

The source post doesn't include the repo or exact model names, so if you want to replicate it, that's the gap to fill. The architecture itself is straightforward enough to rebuild against whatever local ASR model you're already running — the cron job and file-on-disk output are the two decisions that matter most for long-term usefulness.