TreeMap
무료 오픈소스 디스크 사용량 시각화 도구로, 사각형 트리맵·중복 파일 탐색·디스크 가득 예측·정리 시 파일을 휴지통으로만 이동한다
Your AI recorder is already on your wrist.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Your AI recorder is already on your wrist.
A Plaud-style AI notetaker, running on the watch and phone you already own. Your Drive keeps the audio, your own key transcribes it, your own AI writes the notes.README 전문 보기 ↗Your AI recorder is already on your wrist.
A Plaud-style AI notetaker, running on the watch and phone you already own.Your Drive keeps the audio, your own key transcribes it, your own AI writes the notes.
App Store · Google Play · Mac & Windows · Automatic minutes · Install guide · FAQ · Privacy · Issues · 한국어
A Plaud or a NotePin sells you three things: a recorder, transcription, and AI notes. You already wear the recorder, and you already pay for the AI. Recly supplies the one piece you are missing, transcription on a supported device or with your own API key, and keeps the original audio in your Google Drive, iCloud or a folder you pick. There is no Recly server, no bot joining your call, and no monthly fee.
Stop recording, and your ChatGPT agent writes the minutes by itself, usually within a minute. Every
new transcript becomes an MCP event: recly-events, a small program you run on your
own computer, sends recording.transcribed to your agent, a dot or a Work chat, and the agent reads the
transcript and does what you asked for every recording: minutes, decisions and action items, a
follow-up email to draft.
recording.transcribed
reaches ChatGPT signed, and every new transcript starts a run of your agent.get_transcript; ChatGPT needs no Google Drive app.Set it up: run recly-events yourself on a Mac, Linux or Windows computer, or a server. You need recordings stored in Google Drive; a ChatGPT dot (at the time of writing, ChatGPT Business Premium, or ChatGPT Pro outside the EEA, Switzerland and the UK) or a Work chat on ChatGPT web; an OpenAI Platform account for the tunnel and its key; and a computer that stays on.
recly/memo/2026-10/ in your own Google
Drive, through drive.file, the narrowest permission Google offers; or to your iCloud on iPhone
and Mac; or to a local folder you pick, such as an Obsidian vault. The original is never deleted
before the upload is confirmed, and Recly has no server that could see your files..txt, .md,
.srt or .vtt and the audio as .m4a.
A vocabulary of names and terms helps them come out spelled right, and audio or video files from
elsewhere can be imported as recordings.| Step | Where it happens | What leaves your device |
|---|---|---|
| Recording | Your watch, phone or desktop | Nothing. A watch hands the audio to your paired phone, and only there. |
| Storage | Your Google Drive (or your iCloud on iPhone and Mac, or a local folder you pick on iPhone, Mac, Windows and Android) | To Google Drive or iCloud: the audio parts and a small metadata file, to your own account. A local folder: nothing leaves the device. |
| Transcription | On device, or a provider you chose with your own key | On device: no audio goes to a speech service. External: the joined audio goes to the provider you selected, with your vocabulary if you set one. Results are written next to the recording. |
| Notes | Your own AI agent (Claude, ChatGPT, Codex, ...) | The agent reads the transcript from your storage and writes the notes wherever you keep them (Notion, in the example skills). If you run recly-events for automatic minutes, it tells your ChatGPT agent about each new transcript through OpenAI: the recording's name, title and Drive links, and the transcript when the agent asks for it; never the audio. |
| Notes in the app (optional) | Your ChatGPT plan, once you sign in with ChatGPT and agree to organizing, and when you choose Organize on a recording | The transcript text — while you record and after you stop — with what you wrote in Settings → Notes, to OpenAI, with phone numbers, emails and long numbers replaced first; never the audio. Ask about this recording sends the transcript and About you with your question. The notes, which you can edit, are kept with the recording in Drive or iCloud for your other devices, or on the device with a local folder. |
| Processing settings and API keys | Your device | Nothing is synced. Settings file → Export settings moves configuration only; enter keys separately on each device. |
The full list of every network path, with nothing left out, is in the privacy policy.
| Platform | Requires | On-device transcription | Get it |
|---|---|---|---|
| Android phone | Android 14+ | 64-bit, 6 GiB+ reported memory (an 8 GB device in practice), ~1 GB one-time download | Google Play |
| Galaxy Watch | Wear OS 5+ | — (the phone transcribes) | Google Play, with the Android phone app |
| iPhone | iOS 17+ | iOS 26+ | App Store |
| Apple Watch | watchOS 10+ | — (the iPhone transcribes) | Comes with the iPhone app from the App Store |
| macOS | macOS 14.4+, Apple Silicon | macOS 26+ | Notarized DMG from Releases |
| Windows | Windows 11, x64 | 64-bit, 6 GiB+ reported memory (an 8 GB device in practice), ~1 GB one-time download | MSI from Releases (beta, unsigned: see the guide) |
Devices without on-device transcription use an external provider with your own key, or record without transcription.
The install guide has the steps for each platform, including sideloading the phone and watch APKs that each release carries and getting past the Windows SmartScreen warning. Building from source is in docs/development.md.
Next: set it up (storage and transcription), then, if you like, automatic minutes with a ChatGPT agent. Questions: FAQ.
Beta. The Windows app is built and tested in CI but has not yet been checked on a real Windows PC. Please report what you find in Issues.
New installs transcribe on the device where it can: with Apple's speech recognizer on iPhone and Mac, and with the open-source Qwen3-ASR 0.6B model on Android and Windows, a one-time download of about 1 GB that starts only when you ask. The requirements are in the table above. Elsewhere transcription starts off; choose an external provider with your own key. On-device transcription separates speakers too, with models bundled in the iPhone and Mac apps and, on Android and Windows, about 41 MB more in the same download (there, sentence by sentence). It never falls back to a cloud service.
The interface supports English, Korean, Japanese, Simplified and Traditional Chinese, Spanish, French, German, Brazilian and European Portuguese, Arabic, Hindi, Russian, Italian, Polish, Turkish, Filipino, Bengali, Urdu, Swahili, Vietnamese, Persian and Thai. Transcription offers 20 language choices, filtered by the provider or the device's speech engine. Desktop recordings always use meeting mode (microphone plus system audio), with automatic microphone selection.
Settings and transcript formats are documented in spec/.
Recly's pipeline ends at the transcript on purpose. Turning it into notes is something your existing AI subscription already does well, so instead of a metered feature Recly hands the transcript to your agent: on its own, the moment the transcript lands, or whenever you ask.
For notes in another format, notes kept outside ChatGPT, or questions across past recordings, Recly ships two example skills for any agent: Claude, ChatGPT, Codex and others. Use them as they are, change them, or write your own for your format and notes app. The agent only reads the recordings; in the examples, the notes live in your Notion.
| Example skill | What it does |
|---|---|
recly-notes | Finds a recording (the latest, or the one you name), reads its transcript and writes minutes, a decision log, interview or lecture notes, or a memo |
recly-notion | Keeps those notes in a "Recly Recordings" database in your Notion, one page per recording, and finds them again later |
npx skills add rokrokss/recly # any agent that supports Agent Skills
# or, inside Claude Code:
/plugin marketplace add rokrokss/recly
/plugin install recly@recly
The plugin registers Notion's hosted MCP server; run /mcp once to sign in. In the Claude app,
upload recly-notes.zip and recly-notion.zip from the
latest release as skills. In the ChatGPT app,
unzip them and upload the five files inside to a project. Setup for each is in
skills/README.md.
Then ask: "Make minutes from the latest recording and put them in Notion" or "What did we decide about pricing last week?". Want another format, or notes somewhere other than Notion? Edit a skill, or copy one and write your own. That is the point.
Recordings in a local folder, or in iCloud on a Mac: recly-events mcp gives Claude Desktop, Claude
Code or Codex on the same computer tools to list, search and read them, with no sign-in and no
network. Setup: Local MCP server.
| Client | Built with | What it does |
|---|---|---|
| Galaxy Watch (Wear OS) | Kotlin · Wear Compose | Record, hand off to the Android phone |
| Android phone | Kotlin · Compose | Record, configure processing, Google sign-in |
| Apple Watch | SwiftUI | Record, hand off to the iPhone |
| iPhone | SwiftUI | Record, configure processing, Google sign-in |
| macOS | SwiftUI menu-bar app | Meeting capture (mic + system audio), process recordings |
| Windows | Compose Desktop + Rust capture helper | Meeting capture, process recordings |
All six share one Kotlin Multiplatform core: the fixed recording flow, resumable Drive uploads, transcription adapters and the job queue.
Recly has no server. Data goes only to the storage you choose (your Google Drive, your iCloud on iPhone and Mac, or a local folder that stays on your device), to the transcription provider you chose with your own key, between your own paired watch and phone, and, if you set up automatic minutes, to your ChatGPT agent through OpenAI: the recording's name, title and Drive links, and its transcript when the agent asks for it; never the audio. The privacy policy lists every one of those paths, and docs/recly.md §15 is the engineering contract behind it: any change that adds a network call must update that section first.
core/ Kotlin Multiplatform shared core (:core)
android/ :app (phone), :wear (Galaxy Watch), :recording (shared recorder), :datalayer (phone↔watch contract)
apple/ Rec.xcworkspace — RecKit (Swift package) + RecPhone / RecWatch / RecMac
windows/ app/ (Compose Desktop) + capture-helper/ (Rust, WASAPI)
spec/ JSON Schema + examples — the contract every client honors
skills/ example agent skills (the `recly` plugin) — recly-notes (transcript → notes) · recly-notion (notes ↔ Notion)
events/ recly-events — optional program that tells a ChatGPT agent about new transcripts (MCP events) and serves local recordings over MCP
scripts/ icon rendering
docs/ recly.md (the design source of truth) + user guides (install, setup, agent, recly-events, faq) + development.md + policy/
| Document | Contents |
|---|---|
| docs/development.md | Build and test every client, values filled in locally (OAuth client IDs), cutting a release |
| docs/recly.md | The design source of truth. Architecture, the internal step model, recording and retention, processing settings and secrets, auth, transcription, per-platform notes, privacy, open decisions. Its section numbers are a contract: code comments cite them as docs/NN "…" |
| docs/install.md · setup.md · agent.md · recly-events.md · faq.md | The user guides, also at recly.dev |
| spec/ | Machine-readable contract: recording-settings.schema.json, recording.meta.schema.json, transcript.schema.json, examples/ |
| events/README.md | The recly-events reference: commands, configuration, the event and its tools, building it |
| skills/README.md | The recly plugin: what the two example skills do, how to set them up in Claude Code, the Claude app and ChatGPT, and how to write your own |
| AGENTS.md | Orientation for coding agents working in this repository |