Three pieces, all on your computer
An agent can only answer “what did we decide about the launch date?” if it can reach the conversation. The usual route is a cloud notetaker: a bot or app sends the audio to a vendor, and the vendor's connector hands transcripts to the agent. A local setup replaces each step:
- Capture without a bot. LokalBot records your microphone and the meeting app's audio on separate tracks. Nothing joins the call.
- Transcribe and index on-device. Speech recognition, summaries, and the search index run on your computer and stay in a local library.
- Open it read-only. The bundled
lokalbot-cliis both a command-line tool and an MCP server that your agent starts on your computer over stdio. It is off until you turn it on.
Set it up
- Install LokalBot, let the models download, and record a short test meeting.
- On a Mac, in Settings → External Agents, turn on Allow external agents to read your LokalBot data and keep Meetings ticked. On Windows and Linux, turn on Allow external agents to read your meeting library in Settings → Privacy & Data.
- In Settings → External Agents → Agent CLI on a Mac, or Settings → Advanced → Agent CLI on Windows and Linux, choose Install for your coding agent…. It installs a skill that explains the commands to agents and puts
lokalbot-cliin~/.local/binon a Mac or Linux. On Windows it goes in%LOCALAPPDATA%\Programs\LokalBot\bin; add that folder to your PATH. - Register the MCP server with your agent:
# Claude Code $ claude mcp add lokalbot -- lokalbot-cli mcp # Codex $ codex mcp add lokalbot -- lokalbot-cli mcp
These commands work on Mac, Windows, and Linux once lokalbot-cli is on your PATH. Otherwise, use its full path, such as /Applications/LokalBot.app/Contents/Helpers/lokalbot-cli on a Mac. The Windows and Linux versions (alpha) have the same MCP tools as the Mac.
Claude Code and Codex can also install the LokalBot plugin, which adds a catch-up brief, recall with citations, and guided setup. The plugin doesn't start the MCP server, so keep the command above for screen memory. Other MCP clients that can start a local command, such as Cursor, use the same lokalbot-cli mcp.
What the agent can do
- Find meetings.
list_meetingsfilters by date and title, andsearch_meetingssearches titles, summaries, and transcripts by word. - Read one.
get_meetingreturns a meeting's metadata, summary, or transcript as Markdown, so the agent can ask for just the summary. - Ask a question.
ask_libraryhas LokalBot's local model answer from your library, with meeting citations. The agent gets the answer instead of raw transcripts, which also keeps long calls out of its context window. The LokalBot app must be running, and the first answer can take up to a minute while the model loads. - Follow up.
get_action_itemslists open actions with your corrections applied, andlist_peopleshows who you meet, by name only. Email addresses are never returned.
An agent without MCP can run the same commands in a shell. For example, lokalbot-cli search "pricing decision" prints matching meetings as JSON.
Screen memory has its own permission: on a Mac, the Screen memory box under the same switch; on Windows and Linux, a second toggle, Allow external agents to read screen memory. It grants today, the last seven days, or all retained history. Those tools return captured text and metadata, never screenshot pixels.
The Files box on a Mac, or Allow external agents to search your files on Windows and Linux, lets the agent search the folders you chose under Files with search_files, by their words. It gets each matching file's path, a short excerpt, and the passage that matched. LokalBot never changes the files.
Where your meetings go once an agent reads them
LokalBot doesn't upload your library, and its agent tools only read it, so the agent can't change or delete meetings. Changing LokalBot's settings is a separate switch, Allow external agents to change LokalBot settings, and anything that widens what LokalBot captures waits for your approval in the app. But whatever a tool returns becomes part of the agent's conversation, and Claude Code and Codex send that conversation to Anthropic or OpenAI under their own terms. Treat it like pasting the text in yourself:
- Prefer
search_meetingsandask_libraryto pulling whole transcripts. - Turn access on only for agents you trust with that content, tick only what they need, and turn the switch off to cut access again.
- The switch controls LokalBot's CLI and MCP server. An agent that can run shell commands as you can also read any file your account can, so use the agent's own permission settings to limit file access.