<!-- release-blog: covers 47501678 -->
We added a record button to Docapybara. Click it inside a page, talk for as long as the meeting takes, click stop. The transcript lands in the same page, with speaker labels and a short summary.
That last part is the whole point. The transcript isn't sitting in a separate app you have to copy out of. It's a markdown block, in the page where you were already taking notes — editable like everything else, searchable like everything else, and the AI agent in your vault (Capy) reads across it the same way it reads any other page.
What clicking record actually does
The recording happens in your browser. You give the page mic permission, you talk, and the audio uploads on stop. There's nothing to install — no extension, no desktop app, no calendar bot.
Once the recording's saved, a transcription pass runs. You get speaker labels (so two-person calls don't blur into one wall of text), a draft AI summary, and the original audio still attached if you want to re-listen. The whole thing renders inline as a small audio block. You can keep typing around it.
Two places to record
There are two natural places to start a recording:
- Inside a page. Type
/record (or pick "Record meeting" from the slash menu), give mic permission, and a small recorder appears in the sidebar with a live timer. When you stop, the recording attaches to the page you're working on — and Capy uses that page as context when drafting the summary.
- As its own thing. From the file tree, click "+ New Audio Recording" — this gives you a standalone recording that lives at its own URL. Useful when the meeting hasn't earned a doc yet, or you just want to dump audio quickly and decide later.
Both flows produce the same kind of object. The difference is mostly where the recording shows up in your vault. If you trash a recording before saving, nothing persists — no orphaned files in your tree, no dead transcripts.
What you get back
For each recording, you end up with three things in the same page:
- The audio, replayable inline.
- The transcript, with speaker labels, as plain markdown.
- A short summary, drafted by Capy — what the call was about, decisions, action items if it picked any up.
The summary is a draft. We say "draft" deliberately — AI summarizers still get the subjunctive mood wrong, still occasionally read tentative comments as commitments. You'll want a once-over before you forward it. (We wrote about this category-wide in AI meeting notes: what's actually worth using.)
What Capy can do with the transcript
Because the transcript is a real markdown block in your vault, Capy can search it the same way it searches any other content. Useful prompts:
- "What did the customer say about pricing in last Tuesday's call?"
- "Pull every action item I committed to in the last five meetings."
- "Summarize what we've decided about the migration across all the recorded calls."
If the recording was started inside a page, Capy can also use the page as context when generating the summary — so the summary is grounded in the doc you were working on, not just the bare transcript. (See how to capture action items so they actually get done for the follow-through shape.)
Where it doesn't fit
Honest about the limits:
- No live transcription. The transcript runs after you stop. If you need real-time captions during the call, the bigger meeting-notes products do that and we don't.
- No auto-bot-joining. Docapybara doesn't dial into your Zoom for you. You hit record on your own machine when the call starts.
- Single-user. No shared meeting library; no team channel of recaps. One person, one vault. Always was.
If you want a bot that auto-joins every Zoom and a shared archive your team can browse, the products in AI meeting note taker: which one to actually pick are built for that. If what you actually want is "the transcript, in the doc I was already writing in", that's the gap we built this for.
Try it
Open a page in Docapybara, type /record, and talk for thirty seconds. The transcript and summary will be there when you come back from getting coffee.