Call.md Meeting Assistant: License, Privacy and Platform Limits
By Matt Cullerton, founder of Mavric and Apso
Call.md is an Electron desktop app from VideoDB that records meetings, transcribes them live and runs AI features before, during and after each call. The source is public on GitHub, but the repository has no LICENSE file, the audio is sent to VideoDB's servers for transcription, and the only platform with a ready installer is macOS.
What is Call.md?
A TikTok from @saf3synt describes Call.md as "an open-source desktop app that runs AI intelligence through your meetings in real-time" that "records and transcribes calls as they happen, then runs agent loops before, during, and after each meeting." The clip is a scroll through the GitHub README and never shows the app running.
The repository is video-db/call.md, created 2026-02-25 and written in TypeScript. Its description reads "Turn meetings into live agent loops. Record, transcribe, and analyze meetings with real-time AI intelligence." VideoDB's documentation calls it an "AI meeting assistant, live during every call."
Who makes Call.md?
VideoDB, the company whose paid API it runs on. The repo sits in the video-db organization, package.json lists the author as VideoDB with support@videodb.io, and the README ends "Made with ❤️ by the VideoDB team". Call.md is a first-party client for VideoDB's commercial API.
The project has changed names twice. The commit history shows "init: meeting copilot" on 2026-02-26, a rename to Notter on 2026-03-24, and a rename to call.md the next day.
Is Call.md open source?
The source is public, but the license is incomplete. The README shows a "LICENSE MIT" badge, yet the repository root has no LICENSE, LICENSE.md or COPYING file. GitHub's license endpoint for the repo returns HTTP 404, and the repository object reports license: null.
The badge is a static shields.io image with "MIT" written into its URL, defined at README line 440. It does not read anything from the repo. The only machine-readable MIT declaration is the "license": "MIT" field in package.json, which is npm metadata. MIT requires the license text to be included in all copies, and that text is missing. Anyone forking it today has the publisher's stated intent and no license file.
Does Call.md transcribe locally?
No. The README says the app "Captures dual-channel audio (you vs them) and sends to VideoDB for real-time transcription via WebSocket". Its Security section is direct: "The application database, settings, and logs stay on your machine. Recording, transcription, and AI inputs are sent to VideoDB when those features are used."
Language model calls go the same way. The Tech Stack lists "OpenAI SDK (6.19.0) - LLM calls via VideoDB's OpenAI-compatible API."
Storage is local. Settings, meeting history, transcripts and generated metadata live in a local SQLite database. The record of your meetings stays on disk, while the raw audio leaves the machine.
Do you need a VideoDB API key?
Yes. The README lists a VideoDB API key from console.videodb.io as a prerequisite, and step 2 of setup is "Launch the app and enter your VideoDB API key". The docs page says a free tier is available. VideoDB's pricing page showed only a contact form, so the cost of heavy use is unknown.
What does Call.md do before, during and after a meeting?
"Live agent loops" is the project's own tagline, which the video reads back. The features behind it are specific:
- Before: a Meeting Setup Wizard that writes "AI-generated probing questions based on meeting description", a Dynamic Checklist, and Google Calendar sync.
- During: Live Assist, Conversation Metrics ("talk ratio, speaking pace (WPM), questions asked, monologue detection"), Coaching Nudges, MCP Auto-Triggering that calls your MCP tools when the conversation needs information, and bookmarking.
- After: a summary with a narrative overview, key points and action items, delivery to "workflow automation platforms (n8n, Zapier, CRMs)", and markdown export.
The core orchestrator file is named sales-copilot.service.ts, which hints at the intended user.
Which platforms does Call.md support?
Recording works without compiling only on macOS. GitHub shows "No releases published" and zero tags. You install with a script from VideoDB's server: curl -fsSL https://artifacts.videodb.io/call.md/install | bash.
The README's Platform Support table lists:
- macOS 12+ (Apple Silicon and Intel): supported through the install script.
- Windows x64: "Recording supported; no hosted installer yet", so you build it with
npm run dist:win. - Windows ARM64: "Recording not supported".
- Linux: "App features available; recording not supported", build from source.
Recordings also stop after 2 hours of active recording time, with a warning 5 minutes before.
Is Call.md good for teams?
The video says it is "Great for teams and researchers who want more than just a transcript." Nothing in the README supports that. There is no shared workspace, multi-user account, seat model or sync of meeting history between machines. Everything sits in one SQLite database per computer, and sharing happens through markdown export or webhooks. The word "researchers" does not appear in the README or the docs page.
Is Call.md still maintained?
The latest commit on main is "Merge pull request #33 from Nischay-VideoDB/agent/fix-main-qa-findings", dated 2026-08-19. The repo had not changed for five weeks when the video was posted on 2026-09-27. As of 2026-10-27, GitHub reported 1,878 stars and 222 forks.
The opening shot of the video uses an older README screenshot showing "STARS 23" and "ELECTRON 34". The Electron badge changed to 42 on 2026-08-18, so that footage predates the post by months.
Bottom line
Call.md is a real, readable meeting assistant from VideoDB with a detailed feature set. It has no LICENSE file despite its MIT badge, sends meeting audio and AI requests to VideoDB, needs a VideoDB API key, and only installs without a build step on macOS. Nothing in it supports team use.
Sources
- video-db/call.md on GitHub: the repository.
- call.md README.md: features, platform table, privacy and install details.
- Repository object, GitHub API: creation date,
license: null, star and fork counts. - call.md package.json: version, license field and VideoDB author.
- License endpoint, GitHub API: returns 404.
- README commit history: renames and badge changes.
- Root contents, GitHub API: no LICENSE file in the root.
- README at commit 0d8eb3a: the older Electron 34 badge.
- Releases list, GitHub API: no releases published.
- Call.md on VideoDB docs: VideoDB's description and API key requirement.
- Contributors list, GitHub API: contributor accounts and commit counts.
Published September 27, 2026. Based on a TikTok by @saf3synt. Full video notes (markdown)