meetily
Privacy first, AI meeting assistant with 4x faster Parakeet/Whisper live transcription, speaker diarization, and Ollama summarization built on Rust. 100% local processing. no cloud required. Meetily (Meetly Ai - https://meetily.ai) is the #1 Self-hosted, Open-source Ai meeting note taker for macOS & Windows. Understand How to write meeting minutes
Runs with mockssource: GitHubhomepageRustMITcommit 0281737d87d2
Rust, MIT licensed. The project labels itself: ai, ai meeting assistant, llm, local ai, mac, meeting minutes, meeting notes and offline first.
meetily runs, with stand-ins for the services it depends on. An Argusic agent installed it in 58 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Meetily Tauri app builds from source, all Rust (188) and frontend (8) tests pass, and the desktop app launches successfully on Xvfb, initializing all subsystems including Tauri GUI, notification system, database, tray icon, and model managers.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 71 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing system -dev packages for Tauri (glib, gtk, webkit2gtk, pcre2, freetype, harfbuzz, x11, mesa, dbus, atk, alsa, gstreamer, ayatana, dbusmenu, xslt, llvm/clang, libjpeg, libpng, tiff, webp, etc.)32 minutes
- WebKit subprocess path /usr/lib/... is hardcoded and cannot be written10 minutes
- Missing system runtime .so files for webkit2gtk, gstreamer, ayatana, dbusmenu, libxslt, etc.8 minutes
- Next.js frontend build ran out of memory (OOM killed)3 minutes
- Missing Rust toolchain (rustc, cargo)1 minute
- Missing pnpm package manager1 minute
- Install time
- 58 minutes
- Cold machine to finish
- 61 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- Model tokens used
- 834,772
- Exact commit tested
- 0281737d87d2
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms: Session started around 19:55 UTC = 1788638100 Current time = 1788641605 Elapsed minutes = 3505 / 60 exec /bin/sh -lc 'echo "(1788641605 - 1788638100) / 60 = $(((1788641605 - 1788638100) / 60)) minutes"' i… succeeded in 0ms: (1788641605 - 1788638100) / 60 = 58 minutes Let me now produce the final result: tokens used 834,772 Let me now produce the final result:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 58 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 ai projects Argusic has installed and timed, meetily was the 37th fastest to reach a running state, and 30 of 37 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.41 | |
| Argusic Runner | 2/3 | Did not run | 50.00 | 0.19 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.08 |
Topics (from GitHub)
aiai-meeting-assistantllmlocal-aimacmeeting-minutesmeeting-notesoffline-firstollamaparakeetprivacy-focusedprivacy-toolsrustself-hostedsortformerspeech-to-texttranscriptionwhisperwhisper-cppwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/meetily)Questions
- Does meetily run?
- meetily runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 58 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test meetily?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0281737d87d2. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test meetily?
- The run that produced this verdict cost $0.41: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does meetily take to install?
- 58 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does meetily need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing meetily?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does meetily compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, meetily was the 37th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for meetily?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.