Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/minutes/issues.md or /mcp/minutes/issues.json, or Pod over MCP.

Reported issues for minutes

Pod holds 14 of 14 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to minutes.

Most discussed

Extension MCP server still captures silence (v0.9.4)

Summary

The v0.9.4 fix for #65 (removing detached: true / setsid()) resolved the silence bug when running minutes-mcp as a standalone process, but the Claude Desktop extension (local.mcpb.mat-silverstein.minutes) still captures pure silence.

Environment

Reproduction

  1. Install Minutes via Claude Desktop extension…

Read the thread · 2026-04-06 · closed · external user · 8 comments

MCP tools blocked with "readiness could not be verified safely" — qmd cleanup fails because qmd is unavailable and persistence is disabled anyway

Environment

Minutes desktop app: v0.25.1 Minutes CLI: v0.25.1 (symlinked to the app-bundled binary at /Applications/Minutes.app/Contents/MacOS/minutes) macOS, Apple Silicon (M-series MacBook Air) Claude Desktop, connected via the minutes-mcp MCP server

What happened

Almost every MCP tool call (list_meetings, search_meetings, get_meeting_insights, track_commitments, list_processing_jobs, etc.) fails with:

Run minutes qmd cleanup, repair or reinstall qmd if requested, then restart…

Read the thread · 2026-08-18 · closed · external user · 7 comments

minutes-mcp: 15 s corpus-lease budget denies every query on a real corpus, and it cannot be configured

Summary

On a real corpus (3.8k markdown files on a spinning disk, Windows 11, minutes 0.25.6) every content tool of minutes-mcp is denied with Access denied: stable meeting corpus authorization failed, because DEFAULT_AUTHORIZATION_TIMEOUT_MS = 15_000 in crates/mcp/src/corpus-lease.ts is smaller than the time the CLI itself needs. The cap is deliberately not overridable in production (resolveAuthorizationTimeoutMs only honours MINUTES_CORPUS_AUTH_TIMEOUT_MS under NODE_ENV=test

Read the thread · 2026-09-04 · closed · external user · 4 comments

minutes-mcp 0.25.3: startup auto-setup silently resets the configured transcription model to "tiny" on every server spawn

Environment

Symptom

Since updating to 0.25.3, [transcription] model in config.toml keeps reverting from "medium" to "tiny" many times per day, with no Settings interaction. Meetings silently transcribe on tiny (mangled numbers, destroyed participant…

Read the thread · 2026-08-27 · closed · outside contributor · 4 comments

process_audio hangs / times out unconditionally on Windows - independent of audio duration, no error, no log trace

Summary

On Windows, every call to the MCP tool process_audio fails with a request timeout (MCP error -32001: Request timed out), regardless of the input audio file's duration. The failure is identical whether the file is 41 minutes or 10 seconds long, which rules out a duration-based timeout. No error, job record, or diagnostic trace of any kind is produced anywhere in Minutes' own state.

Environment

OS: Windows 11 Install: Claude Desktop MCP extension (ant.dir.gh.silverstein.minutes),…

Read the thread · 2026-07-06 · open · external user · 3 comments

v0.9.3 Claude Desktop extension ships incomplete yaml package

Summary

The v0.9.3 .mcpb extension bundle ships an incomplete yaml package in crates/mcp/node_modules/yaml. The schema/yaml-1.1/ directory (including merge.js) is missing, causing the MCP server to crash immediately after responding to initialize.

Environment

Symptoms

In Claude Desktop logs, the server starts, receives…

Read the thread · 2026-04-16 · closed · external user · 3 comments

get_meeting tool fails — ${HOME} not expanded in path validation

When calling the get_meeting tool via the Claude MCP connector, it returns an access denied error even when the path is valid:

Could not read: Access denied: path must be within /${HOME}/meetings

The list_meetings tool correctly returns file paths like: /Users/ramgopal/meetings/2026-03-28-meeting-title.md

But when that exact path is passed to get_meeting, the connector rejects it because it's comparing against the literal string ${HOME}/meetings instead of expanding it to the actual home…

Read the thread · 2026-03-28 · closed · external user · 3 comments

In-app Recall / AI Assistant + live Context/Recall (Slice C) — deferred from the trust landing

Context

The conversation-trust privacy landing (Slice A + B) ships sealed audio, restricted-meeting policy, egress controls, audit, and PARA. The in-app Recall / AI Assistant — the native chat panel and the developer/terminal "Discuss with AI" Recall — is deferred (Slice C's live Context/Recall orchestration) and ships fail-closed / temporarily unavailable in this landing.

What still works (not deferred)

The MCP path stays fully functional and policy-enforced: Claude…

Read the thread · 2026-07-21 · open · 2 comments

Most recent

# Minutes — four defects found on a clean Windows 11 install (v0.25.1 / v0.25.2)

Minutes — four defects found on a clean Windows 11 install (v0.25.1 / v0.25.2)

Reporter environment

OS Windows 11 x64
CPU Intel Core Ultra 7 255H (Arrow Lake-H, 16 cores) — no AVX-512
Host Claude Desktop 1.34493.1 (Electron 42.9.2, Node 24.18.1)
Extension ant.dir.gh.silverstein.minutes manifest v0.25.1
Engine tested against both v0.25.1 and v0.25.2 prebuilt minutes-windows-x64
Install state fresh — no prior meetings, no…

Read the thread · 2026-08-23 · closed · external user · 1 comment

Claude Desktop widget: "tool _Meeting_Memory_for_AI__list_meetings not found" — em dash in display name breaks tool-name resolution

Environment: Claude Desktop / Cowork on Windows 11, Minutes installed as a Desktop Extension (.mcpb). Observed 2026-07-14.

Symptom: Opening the Minutes dashboard widget shows a toast: tool _Meeting_Memory_for_AI__list_meetings not found. The MCP tools themselves are fine — calling mcp__Minutes___Meeting_Memory_for_AI__list_meetings from chat returns normally ({"meetings":[],"actions":[],"view":"dashboard"}).

Likely cause (inferred from the error shape, not traced in code):

Read the thread · 2026-07-14 · closed · external user · 1 comment

MCP get_meeting returns envelope-only on Tauri-bundled native-call recordings (v0.17.3, v0.18.0)

Summary

The get_meeting MCP tool returns an envelope without the transcript body, summary, decisions, action items, or commitments — only path, view, speaker_map, and overlay_applied. Reproduced on both v0.17.3 (sideloaded .mcpb) and v0.18.0 (Anthropic directory Connector "Minutes — Meeting Memory for AI") against the same Tauri-bundled native-call meeting recording.

Environment

Read the thread · 2026-05-25 · closed · outside contributor · 2 comments

Windows .mcpb: missing yaml/dist/schema/ directory causes MCP server to crash on startup

Summary

On a fresh Windows install of the Minutes extension (v0.10.0 manifest, v0.13.3 release) via Claude Code's Settings → Extensions → Install, the MCP server fails to start because the bundled yaml npm package is incomplete — the entire dist/schema/ subtree is missing from node_modules/yaml/.

Claude Code reports:

MCP Minutes — Meeting Memory for AI: Server disconnected. Could not attach to MCP server Minutes — Meeting Memory for AI

Environment

Read the thread · 2026-04-22 · closed · external user · 1 comment

server doesn't handle the MCP protocol version (2025-11-25) that the current Claude Desktop ships with - handshake issue

mcp-server-Minutes — Meeting Memory for AI.log

Claude Version 1.3109.0 (35cbf6) and installed the minutes extension. minutes-mcp@0.13.0

The key lines from the log: server starts, receives initialize with protocolVersion: "2025-11-25", crashes ~160ms later The fact that npx minutes-mcp runs fine manually — confirming it's the handshake, not the installation.

Seemingly, minutes hasn't kept pace…

Read the thread · 2026-04-18 · closed · external user · 1 comment

MCP-spawned recordings capture silence (-91 dB); same binary works from Terminal

Summary

minutes record spawned by the MCP server captures pure silence (-91 dB). The exact same binary run directly from Terminal captures audio perfectly (peak level 1). This has been broken since March 31 on my setup.

Reproducible A/B test (April 2, 2026)

Same machine, same mic permissions, same binary, ~10 minutes apart:

How started Audio level Words Job ID
Terminal: minutes record peak 1 (max) 58 job-20260402102929978
MCP:…

Read the thread · 2026-04-02 · closed · external user · 2 comments

The remaining reports are on the project's issue tracker.