Open source is evidence, not a magic label
Source access lets you inspect what a meeting app records, where it stores the result, which hosts it contacts, and what changes when you enable an optional service. It does not automatically prove that a particular downloadable build matches the repository, or that every dependency is harmless. Treat the code as an unusually strong verification tool, then check the actual release and runtime behavior too.
Start with the license
LokalBot is released under GPLv3. Code in the Autocomplete engine that was ported from Cotabby stays under AGPLv3, and other third-party components and models retain their own licenses; see the third-party notices. You can read, modify, and build the code, and distributed derivative versions must preserve the license obligations. That differs from “source available” products whose licenses restrict commercial use, redistribution, or forks. The repository's license files are the authoritative text.
Trace the meeting data path
For a private notetaker, follow the recording from capture to deletion:
- The microphone and the meeting audio produce two local audio tracks. On a Mac the second track is the selected meeting app; on Windows and Linux it is the meeting app where it can be separated, and otherwise everything the computer plays.
- A downloaded speech engine creates the transcript on your computer.
- The built-in llama.cpp backend can generate a summary locally.
- SQLite stores the library and full-text search index.
- Day tracking starts activity-only: app names and window titles. Visible text and encrypted screenshots are opt-in, permission-gated, and deleted after 14 days by default.
Then identify the exceptions. LokalBot connects to download models and updates, to set up optional Agent Mode, and to call any non-loopback inference origin you explicitly approve. On Windows and Linux it also downloads a pinned llama.cpp runtime from GitHub once. That distinction is more useful than an absolute “never connects” claim.
Check account and telemetry requirements
An app can be open source while its useful features depend on a hosted account. LokalBot has no account, subscription, analytics service, advertising SDK, or telemetry backend. Its public issue tracker provides community support, and the security policy points vulnerability reports to a private channel.
Build it yourself
The repository has build instructions for both apps: an XcodeGen project for the Mac app, and a Rust workspace you build with cargo for the Windows and Linux app. A source build is the strongest way to connect the code you inspected with the binary you run. It also makes the trade-off explicit: local-first software still relies on operating-system frameworks and bundled or downloaded model runtimes, so dependency review remains part of a serious audit.
$ git clone https://github.com/stevyhacker/lokalbot.git $ cd lokalbot # Mac $ mkdir -p Vendor/llama-cpp Vendor/sherpa-onnx $ Scripts/build/build-sync-xcframework.sh $ xcodegen generate && open LokalBot.xcodeproj # Windows and Linux $ cd LinuxWindows $ cargo run -p lokalbot-app
The Rust build needs the toolchain pinned in the repository, plus system libraries on Linux and the Visual Studio 2022 Build Tools and CMake on Windows. The Windows and Linux README lists them.
A five-question evaluation
- Can the core workflow run with the network disconnected?
- Does the license actually grant the freedoms you expect?
- Are remote endpoints opt-in, visible, and scoped?
- Can you delete the library without asking a vendor?
- Are releases, update metadata, and security reporting public?