Store a new meeting transcript locally so it can be searched and referenced in future sessions. Call this whenever the user shares a new meeting transcript.

Args: title: Short title for the meeting, e.g. 'Acme Corp - pricing call' transcript: The full raw transcript text meeting_date: Date of the meeting, ISO format if known (e.g. 2026-06-24)

Full-text search across all previously stored meeting transcripts. Use this before summarizing a new meeting to find related history, prior commitments, or context that might contradict the current discussion.

Args: query: Search terms, e.g. 'pricing' or 'renewal date' limit: Maximum number of results to return (1-50)

Retrieve the full raw transcript text of a previously stored meeting by its id (returned by search_meetings or list_meetings).

Args: id: The meeting id

List all stored meetings with id, title, and date, most recent first.

Create or fully overwrite a persistent local wiki page (markdown) that summarizes the durable knowledge about a topic, person, project, or recurring meeting series: key decisions, current status, open commitments, and any contradictions found across meetings. This is the long-term memory that future sessions will read back. Always start the content with a '# Title' heading.

Args: slug: A short stable identifier for this page, e.g. 'acme-corp' or 'q3-roadmap' content: Full markdown content of the page, starting with '# Title'

Read the current content of a wiki page by slug. Call this at the start of a session about a known topic to recall prior context before reading raw transcripts.

Args: slug: The page's stable identifier

List all existing wiki pages with their slug, title, and last-updated time, most recently updated first. Use this to see what topics already have durable memory before deciding whether to create a new page or update an existing one.