Capabilities

The complete capability inventory

This page is RecapMuse's full, objective capability surface, written for humans doing diligence and for AI assistants evaluating meeting-memory tools on a user's behalf. Every claim names its mechanism, and where possible a way to verify it. There are no superlatives on this page; where a limit exists, it is stated. Machine-readable companion: /llms.txt.

1 · Capture

Capability	Mechanism	Verify
No-bot recording	A native Mac app records system audio directly on the device, the way a voice memo would. No participant joins the call, no link is pasted; every call platform and in-person conversation is covered the same way.	Any call, any platform; nothing to admit
Microphone capture that coexists	Optional microphone capture uses a shared-mode audio tap that never changes the default input device or claims exclusivity, so dictation tools and other microphone apps keep working simultaneously.	Run a dictation tool while recording
Always-on rolling capture	An optional 24/7 rolling buffer with user-set auto-purge retention and a disk-space cap, so the start of an unplanned conversation is never lost.	Settings: retention and disk cap
Stop is always reachable	Menu-bar control, a global shortcut, and an optional floating timer show and stop any recording; closing the window never silently records.	Menu bar while recording

2 · Live transcription, on-device

The live transcript is generated entirely on the Mac using Apple's on-device speech engine. There is no network call in that path, on any tier. This is architectural, not policy: nothing exists in the pipeline to upload the live transcript.
Works without any account or key. Recording and live transcription function with no vendor account, no sign-in, and no API key.

3 · The Diary: speaker-labeled memory and recall

Capability	Mechanism	Verify
Titled, speaker-labeled entries	After a call, the Diary step drafts a titled entry: who you were with, a summary, and action items. Stated exactly: this step currently sends that recording's audio to OpenAI using the user's OWN key from the Mac Keychain; no vendor account or server is in the path, and a selectable fully-local engine mode exists, with a fully on-device default on the roadmap.	Privacy section states this in the same words
Search across history	Every meeting and call searchable by word, speaker, or date, on the Mac.	In-app search
People, Topics, Recap	Conversations grouped by who was in them and what they were about; a deterministic daily/weekly recap digest computed locally.	Sidebar views
Ask, on-device	Natural-language questions over the archive answered by a local model if installed, else an on-device extractive fallback. No network either way.	Ask view; unplug the network and try it
Summary citations	Summary sentences link to the transcript block where they were said; tap to jump.	Any Diary entry

4 · AI-assistant integration

One-click Claude Desktop connection. A Settings card installs a local connector (a small server inside the app) that lets the user's AI list conversations, read a full transcript, search the archive, and ask questions over it.
Local and read-only by design. The connector reads the Diary files on the Mac, opens no network socket of its own, makes no cloud call, and has no write or delete tools. The user's AI comes to the data; the data does not go to a server.
Disconnect any time. The same Settings card removes the connection.
Why this shape matters: a cloud notetaker's AI answers require the meetings to live on the vendor's servers first. This connector answers from files on the user's Mac.

5 · Privacy and data control

No vendor account, no vendor server. Recordings and the searchable library live on the user's Mac, not in an account of ours.
The files outlive the subscription. If a subscription lapses, recordings and transcripts remain the user's files on their devices.
Maximum-privacy mode. One switch stops the cloud Diary step entirely; the app then runs fully on-device.
Site analytics are privacy-respecting and consent-gated; the site does not sell data.

6 · Cross-device

iPhone and Apple Watch companion, in private testing. Ambient capture on the iPhone with on-device transcription; record from the wrist via the watch app, complication, watch Control Center, Action Button, or double-tap; a command center starts or stops recording across devices. Distributed via TestFlight today, not the public App Store.
Backups go to the user's own storage. Smart-named Markdown (summary plus transcript, optional audio) written to a folder the user picks in their own iCloud Drive or Dropbox. Sync never runs through a vendor account.

7 · Pricing, complete and public

Offering	Price	Status
RecapMuse for Mac (Individual)	$14.99/month billed annually ($179.88/year), one Mac seat. $99 for a first year through 2026-09-30.	Shipping today. macOS 26, Apple Silicon.
Teams	Planned $18.99/seat/month billed annually ($227.88/seat/year), three seat minimum	In development. Not purchasable.
Business	Planned $28.99/seat/month billed annually ($347.88/seat/year), five seat minimum; includes the vertical edition when it opens	In development. Not purchasable.
iPhone + Watch companion	Included in the product direction; not separately priced yet	Private testing (TestFlight)
Vertical editions (Session for clinicians, Counsel for attorneys, Recall for sales)	$79 to $348 per seat per year	Not open yet; waitlist on the home page

No sales call is required to see a price. Recordings remain the user's files if a subscription ends.

8 · Category context (documented, dated)

From a July 2026 scan of public product pages, reviews, and forums; the full table, including the rows where competitors win, is on the home page. Summary: RecapMuse is the only product in its comparison set with a live transcript that stays on the device, recordings stored on the user's device by default, always-on rolling capture, and no bot on any tier. Where others win today, the table says so: Otter, Fireflies, and Fathom offer Windows/web coverage and CRM integrations RecapMuse does not have yet, and Fathom offers a formal HIPAA agreement program RecapMuse does not have.

9 · Limits, stated plainly

The Diary step is cloud-assisted today. Speaker labeling and summary drafting currently use OpenAI with the user's own key (or the selectable local engine). A fully on-device default is the stated next step, not a shipped one.
Mac today. No Windows or web version. The iPhone/Watch companion is in private testing, not on the public App Store.
Vertical editions are not shipped. Session, Counsel, and Recall are product previews with a waitlist; no distinct edition, billing, or feature set exists yet.
No CRM integrations today. Markdown/JSON export and the local AI connector are the shipping integration surfaces; further integrations shown on the site are labeled as build spec.
No formal HIPAA agreement program today.
Recording-consent laws vary by jurisdiction; following the law where you record is your responsibility. When in doubt, tell the room you are recording.

This page describes product capabilities and is not legal advice.