Can tl;dv be vibe coded?

Build brief — a focused alternative to tl;dv

**Verdict:** Partly, if you narrow it · **Buildability:** 53/100 · **Category:** Meeting Notes

**Source:** https://www.canitbevibecoded.com/tldv

Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from tl;dv. Verify current pricing and capabilities before acting.

Context

**tl;dv** — AI meeting recorder with transcripts, summaries, clips, and CRM sync. It currently costs $29/mo.

A DIY app can record, transcribe, summarize, and generate clips, but tl;dv's team library, CRM integrations, and meeting-bot reliability are real work.

This brief describes a focused, single-operator replacement for the part of tl;dv that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

What you are building

Join/record meetings, generate transcript and summary, tag highlights, clip segments, and export notes.

Capture supplied audio, transcribe it, create structured notes, and export them.

A responsive interface with real empty, loading, success, and error states.

Requirements

Functional

Meeting platform integration.

Speech-to-text.

Video storage.

Hosted backend.

Data and integrations

LLM API.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

Non-functional

Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.

Security: server-side secrets, validated input, and no credentials in the client bundle.

Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.

Portability: the operator can export their data and leave without losing it.

Implementation brief

Build me a personal meeting recorder with clips to replace tl;dv. Requirements:

A macOS menu bar app (or a rec start / rec stop CLI, pick the simpler to ship)

that records system audio + mic locally with ffmpeg. No bot joins the call.

On stop: transcribe with whisper.cpp with timestamps, or the Whisper API if a key

is in .env.

Send the transcript to an LLM (key in .env) for a 5-bullet summary and action

items; save everything to ~/Meetings/YYYY-MM-DD-<title>/ as notes.md, the

transcript, and the audio file.

While recording, a global hotkey drops a highlight marker; afterwards each marker

becomes a clip, ffmpeg cutting 30 seconds either side into clips/.

A local library page (Express on localhost:4700): list meetings, full-text search

across transcripts with SQLite FTS5, play recordings and clips inline.

No accounts, no telemetry; nothing leaves my machine except optional API calls.

Out of scope: a bot that auto-joins Zoom/Meet, CRM sync, and a shared team

library. This records what I can hear locally.

README: mic + screen-recording permissions, whisper model download, and a

reminder that recording other people still requires their consent.

Delivery standard

Inspect the repository first, then write a short implementation plan before writing code.

Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.

Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.

Include responsive layouts plus genuine empty, loading, success, validation, and failure states.

Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.

Add structured logs around every external call and return actionable errors without leaking sensitive details.

Write unit tests for the core logic and one automated test of the main user journey.

Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

Acceptance criteria

A clean install starts the app using only the README and .env.example.

The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.

Invalid input, missing configuration, provider failure, and an empty database each have a usable state.

The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.

Tests, type checking, linting, and a production build all pass with no ignored failures.

No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

Non-goals

Do not build these, and do not claim to have replaced them:

Meeting bot upkeep.

Team/shared library.

CRM integrations.

Admin controls.

Permissions, presence, and shared workflows are difficult to simplify.

Connectors, OAuth flows, and vendor API changes require constant upkeep.

What you still own after launch

Secure credentials, rotate secrets, and handle provider rate limits.

Run migrations, backups, restores, and dependency updates.

Test the critical journey after every model, API, or hosting change.

Monitor failures and fix the edge cases a first prompt will miss.

Maintain every third-party integration as APIs and OAuth rules change.

Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.

Prior art

Working open-source software you can read, fork, or borrow from before starting:

[whisper.cpp](https://github.com/ggml-org/whisper.cpp) — Can power the transcription layer for a simpler local clone

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/tldv