Patchthrough records your microphone and the other side of the call as two separate tracks. It transcribes the recording on your computer. Then it patches the transcript through to your coding agent, ready in the repository that you discussed.
macOS app available now · Windows installer preview in hardware validation · cross-platform CLI
Patchthrough records the other side of the call. Tell the people in the meeting that you are recording. Local law may require their consent.
The recorders are native to each operating system, while every session uses the same transcript contract. Windows packaging is implemented; automated verification and supported hardware remain the release boundary.
Record your microphone and system audio as separate tracks, transcribe fully on-device, and patch the transcript directly into your agent.
Download for macOS →Microphone capture, WASAPI loopback, local Parakeet and Whisper transcription, the shared session format, a self-contained x64 ZIP, and a per-user installer are implemented. Automated install, run, and uninstall verification now runs on every change. Physical hardware acceptance and publisher signing remain before public release.
Review the Windows preview →Install the transcript client on macOS, Windows, or Linux. Hand files to terminal agents everywhere, with browser handoffs on macOS and Windows.
Install the CLI →Start the recording from the menu bar. Patchthrough records your microphone and all the audio that the Mac plays as two separate tracks. The speech model gets clean single-source audio, and you get me/them speaker labels. "All the audio" is literal: notification sounds and music land in the transcript too.
Click Stop. The transcription starts automatically. Parakeet TDT runs on the Neural Engine through Core ML. One hour of audio takes approximately 20 seconds, fully on your Mac. Parakeet transcribes English only.
In the menu bar, click Patch through to Claude Code, or to a different
destination that Patchthrough finds on your Mac. A terminal opens in your
repository with the agent running and the transcript in context. You
can also use the command line: patchthrough hand claude.
One click takes you from "we agreed on it in the meeting" to "an agent is implementing it".
The agent gets the full transcript, not a summary. A summary can lose requirements. The agent also gets a prompt. The prompt tells the agent to find work items, decisions, and open questions. It tells the agent to ask when a term is not clear. And it tells the agent not to change code until you agree on the plan.
The transcript goes in the .meeting/ directory in your
repository. Patchthrough adds that directory to the local git excludes
of the repository. Meeting content cannot go into a commit by accident.
Patchthrough does not change your .gitignore.
The macOS app finds what is installed on your Mac and groups it the way you think about it. It puts the destinations that you use most at the top of the list.
The transcript stages in the repository you pick, and the agent starts with a prompt pointing at it.
VS Code opens its chat command with the transcript as context. Cursor gets a link. The chat apps open with the transcript ready to attach.
Patchthrough opens a new chat in your browser and attaches the transcript. For Microsoft this is the only way to attach a file at all.
The handoff works the same way everywhere: Patchthrough puts the transcript on your clipboard as a file and pastes it in as an attachment, so the agent gets a document rather than a wall of pasted text. You can also drag that file from the Patchthrough window into any chat input, including apps that Patchthrough has never heard of. One caveat worth knowing: Microsoft copies a file you attach into your work OneDrive, so Patchthrough asks before that handoff, and every other destination keeps the transcript on your Mac.
Your own tools count too. Point Patchthrough at any web app with a chat box and it appears under Custom, on your machine only, through one entry in the config file.
The transcripts of your meetings are sensitive data. Patchthrough pins and verifies its supply chain.
Audio and transcripts stay on your computer. Patchthrough downloads two things: the transcription models, once, and its own updates. It verifies both before it uses them, the models against pinned hashes and an update against Apple's notarization and the same Developer ID that signed the copy you are running.
Patchthrough has no server of its own, so a transcript reaches exactly the destination you pick and nothing else. Every destination keeps the file on your computer, with one exception: Microsoft copies a file you attach into your work OneDrive, and Patchthrough asks you first.
There is no account to sign in to and no server to breach. Sessions
are plain files in ~/Recordings/. You own your data.
Patchthrough pins native dependencies to exact versions. Verification scripts stop the build if a dependency or a model changes. No version range can pull new code into a binary that has microphone access.
The macOS app comes from GitHub Releases. The npm package is a plain JavaScript transcript client with no install scripts or native downloads.
Open the disk image and drag Patchthrough into Applications. Releases are signed and notarized, hosted on GitHub Releases. Patchthrough is open source and not distributed through the Mac App Store. Launch at login is available in Settings.
The npm package handles transcripts, terminal agents, and the web destinations. It has no install scripts and never downloads the native app. It can read sessions from the app. It also accepts any transcript file, or text piped in from another command.
The Windows recorder has an installer preview, not a public download. Automated package verification now passes on every change. Release still requires publisher signing, plus microphone and loopback capture, codecs, model inference, device changes, and recoverable failures to pass on physical Windows hardware. See the acceptance checklist →
Patchthrough requires macOS 15 or later and Apple
Silicon. The transcription models (approximately 600 MB) download one
time, on the first use. Record a short test while you are online before
your first meeting. To build the app yourself, clone the repository and
run ./packaging/make-app.sh.
Every Windows release is built by a public GitHub Actions workflow in the project repository. No release artifact is built or signed on a personal computer. The dependency graph is locked, and the installer compiler is pinned to a verified release.
Windows code signing is provided by SignPath.io, with a certificate from the SignPath Foundation. The certificate belongs to the Foundation, so Windows shows SignPath Foundation as the publisher. Only the project maintainer can approve a signing request, and requests come from the release workflow in this repository and from nowhere else.
The current Windows installer preview is not yet signed. Signing starts with the first release after the certificate is issued. Until then, verify the SHA-256 file published beside every download.
macOS releases are signed with an Apple Developer ID and notarized by Apple.
Patchthrough records audio only when you start a recording. Audio, transcripts, and session files stay on your computer. The program never sends them anywhere.
The program uses the network for two purposes. It downloads a transcription model the first time you need it, and checks each model against a pinned SHA-256 hash before loading it. It also asks GitHub about twice a day whether a newer release exists. That request carries no account and no identifier, nothing installs until you click, and Settings turns the checks off.
Patchthrough collects no telemetry and no personal data. It has no account, and no server to sign in to.