pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for mindmap-mcp-server

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to mindmap-mcp-server.

Most discussed

Project/workspace-aware resume (pick the right folder for a topic)

Idea: When you resume a topic, Mind Map should also infer which workspace/project folder the discussion belongs to, so you continue in the right directory — not just with the right context.

Why: With cluster-resume, you describe a topic and get the merged thread. The natural next step is: "…and this lived in ~/code/commerce-grid — continue there?"

Sketch:

  • Store the project root path (cwd) on memories at capture + import (today we keep only the project name via tags/

Read the thread · 2026-06-29 · closed · 0 comments

Persona conflict resolution + tool scope

Problem: Today global + project persona facts both surface with no conflict resolution; only project scope exists, not tool scope.

Proposal: (1) Project overrides global on a genuine conflict. (2) Add a tool: scope (e.g. terse for terminal, verbose for email) on top of global/project.

Why: Surfaced in r/mcp feedback (NovaAgent2026 — terminal-vs-email; persona conflict question). Promised on-thread.

Acceptance: renderPersona resolves conflicts (tool > project > global); tool

Read the thread · 2026-06-13 · open · 0 comments

Provenance-first-class retrieval ('what did I figure out in the previous tool')

Proposal: Make 'what did I figure out in the previous tool' a first-class retrieval mode, not just a source filter — e.g. on tool switch, surface fresh memories from the prior tool.

Why: Provenance helps decide what's still relevant when switching tools. Surfaced in r/mcp feedback (NovaAgent2026).

Acceptance: retrieval mode/tool ranking by source + freshness; tests. (Effort: M)

Read the thread · 2026-06-13 · open · 0 comments

Trust label: stale-since-capture detection (files changed)

Proposal: For code-linked memories, detect whether referenced files changed since capture and flag the memory as potentially stale.

Why: Knowing files changed since capture helps decide whether a note is still current (trust labels). Surfaced in r/mcp feedback (Conscious_Chapter_93).

Acceptance: record file refs/timestamps at capture; compare on read; surface staleness; tests. (Effort: M)

Read the thread · 2026-06-13 · open · 0 comments

Capture next-steps / open work (better handoff)

Problem: Capture records the discussion but not what's unfinished. On resume, the most useful thing is 'where did I stop / what's left.'

Proposal: Optional nextSteps / openQuestions on capture (nudge the model + brainstorm skill to fill it); surface prominently on resume.

Why: Directly strengthens the core capture→resume handoff.

Acceptance: capture accepts next-steps; resume surfaces them; tests. (Effort: S)

Read the thread · 2026-06-13 · closed · 0 comments

Redaction / secret-scan on capture & import

Problem: Captured and imported memories are stored verbatim in ~/.mindmap (plaintext). Imports especially can drag in secrets (API keys, tokens) pasted into past sessions.

Proposal: A local, no-LLM scan at capture/import that detects common secret patterns (sk-…, AKIA…, ghp_…, github_pat_…, bearer tokens) and masks them or flags the memory (redacted: true).

Why: Reinforces the trust story; makes importing real history safe. Surfaced in r/mcp feedback (Conscious_Chapter_

Read the thread · 2026-06-13 · closed · 0 comments

Most recent

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