litepipe 0.4.1

Fixes two bugs that were in every release since 0.3.0.

Reading a meeting transcript never worked

meeting_transcript asked for three columns that do not exist, so every call failed with no such column: timestamp. The schema that the query tool shows an agent carried the same three wrong names, so writing the SQL by hand failed the same way.

Unnamed voices now come back as speaker N from the id that does exist, rather than one repeated question mark against four different people.

A screen with a lot of text took the whole bridge down

When a result ran past the character cap, the row reader appended a note one column wide. Three of the six tools read a fixed column, so that note crashed the process with Index out of range, and the client lost its connection instead of getting an error back. One screen holding 14476 characters was enough.

frame_context now cuts the text in SQL and says how many characters were left out, so asking for one busy moment returns the moment.

Also

The bridge stops announcing itself as version 0.3.0. The number now comes from the bundle it ships in.

scripts/check-mcp-tools.py calls all six tools against a real archive and fails if any of them errors. A wrong column name in a SQL string compiles cleanly and only fails when an agent calls it, which is how both of these shipped.

litepipe 0.4.0

Superseded by 0.4.1, which fixes the two known issues below. Download that one.

The chat pane is gone

litepipe holds the archive and answers nothing on its own. The pane that suggested otherwise needed the claude command line tool to work at all, so it was inert for most people who opened it.

In its place, Agents is now the first row of the sidebar: connect a client, then ask it something.

Any MCP client, not just Claude

Manual setup covers Claude Code, Codex and raw JSON, so a client without a one click button is no longer a dead end. The Codex line also covers the ChatGPT desktop app and the IDE extension, which read the same config.

The Claude Code command gained --scope user. Without it the server was registered for the current directory only, and a session started anywhere else answered as though the archive did not exist.

The bridge

Connect writes a path that survives the app being moved or a disk image being ejected. docs/MCP.md is the first documentation this bridge has had: the six tools, what it will not do, and how to drive it by hand without a client.

Known issues

meeting_transcript queries columns that do not exist and fails (#15). Codex connects by hand only, because the button writes JSON and Codex reads TOML (#16).

Installing over an existing copy can make macOS drop the screen recording grant (#10). If capture stops, reset the grants and allow them again:

tccutil reset ScreenCapture ai.ottic.litepipe
tccutil reset Accessibility ai.ottic.litepipe

litepipe 0.3.0

Signed and notarized by Apple. Requires macOS on Apple silicon.

The chat pane answers

The MCP bridge now ships inside the app, so the chat pane is wired to a real client instead of only naming one. Connected means the bridge answered, not that a client was detected on the machine. The inspector says plainly which parts of the chat are still unfinished.

Onboarding survives a cold start

Permissions are granted one action per line, and the app restarts itself once the grant lands. The manual restart button is gone, because it now happens on its own. An empty timeline says it is capturing and fills in every few seconds, instead of looking broken.

The archive stays readable

Opening the archive as read only left it unreadable in some cases. Fixed.

Install

Download litepipe.dmg below, or use the install page at https://rafaelpta.github.io/litepipe/install/

For the engine alone, with no app:

curl -fsSL https://raw.githubusercontent.com/Rafaelpta/litepipe/main/headless.sh | bash

litepipe 0.2.1

Fixes a dead end in the 0.2 permission screen.

Granting Accessibility left its row reading as missing, with nothing to click and
no way to finish setting up. macOS decides that permission when the app starts
and does not look again, exactly as it does for Screen Recording, but only Screen
Recording offered to relaunch. Both do now, as a button beside Grant rather than
a grey link under the description.

If you are stuck on that screen in 0.2, quitting litepipe and opening it again is
enough: the permission you already granted takes effect on the next launch.

litepipe 0.2

The app is a window now. The notch is gone.

What changed

An archive you can actually look at. Every screen the engine kept is
browsable: a day at a time, newest first, with the text it read off each one
beside it. Screens older than ten minutes live inside compressed video chunks,
and litepipe now opens them, so the whole archive is visible rather than the
last few minutes of it.

The permission flow moved into the window. All four asks on one screen, with
their state, instead of one at a time in a panel hanging off the menu bar.

The mark and its menu are in the menu bar. Pause and resume capture, see the
last meeting, open the archive, from any screen.

Sections that are not built say so. Agent Memory, Shared Contexts, Firewall
and Workflows are written pages describing what would live there and which file
to open if you want to build it, rather than grids filtered by a proxy.

Still true

Nothing leaves the Mac. The app makes no network calls. The archive is a folder
you can read, back up, or delete.

Notes

Requires macOS 14 or later. On first launch macOS asks for Screen Recording and
Accessibility again, because the binary changed.

litepipe 0.1

First release of litepipe, a local screen and meeting memory for macOS on Apple Silicon.

Everything stays on your machine. The engine makes no outbound calls: telemetry is disabled, update checks are disabled, and no third party analytics keys are embedded in the binary.

The DMG is signed with a Developer ID certificate and notarized by Apple.

Install by opening the DMG and dragging litepipe to Applications, or run the one line installer from the README. The microphone is only used during meetings you approve, and meeting audio is deleted after transcription.