Find past Meetily discussions, verify them against source excerpts, and open the original meeting.
Meetily Memory reads the local Meetily database, builds a private local index, and never modifies the source database or sends meeting data to a cloud service.
On macOS:
brew tap 0x12th/meetily-memory
brew install meetily-memoryThe CLI is available as mm and meetily-memory.
Initialize the local index:
mm initSearch meeting history:
mm s "migration risk"Each result includes the meeting, matching source excerpt, and command for opening the original:
#10 Meeting 2026-07-06
open: mm open 10
12:56:36 | chunk #3863
If I write to the database, I must also publish to Kafka...
Open the meeting:
mm open 10If Meetily cannot be discovered automatically:
mm doctormm s is the main product interface:
mm s "owner_worker_id"
mm s "what did we decide about migration?"Use --context N when a matching excerpt needs adjacent transcript chunks:
mm s "migration risk" --context 2Refresh the local index after new meetings:
mm refreshAutomatic refresh is optional:
mm autosync start
mm autosync statusUpdate the installed CLI:
mm updateSearch works without manual organization. Add a tag only when several meetings belong to a project or topic that is not named consistently in their transcripts:
mm tag add 10 11 migration
mm s "migration"See the command reference for listing, suggesting, and removing tags.
- Meetily remains the read-only source of truth.
index.sqlitecontains derived data and can be rebuilt.- Explicit user state is kept separately from the disposable index.
- Search and indexing run locally.
Context, topics, semantic search, Obsidian, LLM, MCP, database diagnostics, and source-rebinding commands remain available but are not part of the main workflow. See docs/commands.md and docs/integrations.md.
See docs/development.md.
Licensed under the Apache License 2.0. See LICENSE.