pod
Other formats agents might prefer:
markdownjsonllms.txt

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

Reported issues for basic-memory

Pod holds 23 of 102 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 basic-memory.

Most discussed

Retrieval inspector — expose chunks, scores, and match provenance ("chunk viewer")

Feature Description

A read-only inspection surface for the retrieval layer: view any note as the index sees it, view any query as the complete search pipeline answered it, and view a chunk's nearest neighbors in embedding space.

The inspector exposes chunking, vector retrieval, FTS, hybrid fusion, thresholding, and optional reranking without changing any of those behaviors.

Dependencies and Sequencing

This feature spans two retrieval changes currently in flight:

  • **#1141 — pluggable

Read the thread · 2026-07-26 · closed · external user · 6 comments

[BUG] MCP background basic-memory process utilizing CPU even as idle

Bug Description

Not sure it is a bug, but definitely a defect or at least a subtle issue. Basic-memory is used as a mcp tool to gemini-cli in my setup. I noticed that it would constantly utilize quite a lot of CPU resources even when there is no input from gemini. I also use other MCP tools, and none of them have such a behavior.

One can find it out by looking at the htop screen.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Install version '0.16.2'
  2. Setup basic-memory as a

Read the thread · 2025-12-03 · closed · external user · 8 comments

[BUG] read_note doesn't normalize underscored folder names in permalinks

Bug Description

read_note fails to find notes when given permalinks from underscored folder names (e.g., _archive/, _drafts/), even though the permalink is copied directly from the note's YAML frontmatter. This issue was partially fixed in PR #329 for build_context, but read_note still exhibits the same behavior.

Steps To Reproduce

  1. Create a note in a folder that starts with underscore: _archive/articles/example-note.md
  2. Basic Memory generates YAML frontmatter with permali

Read the thread · 2025-11-05 · closed · external user · 9 comments

[BUG] build_context fails schema validation in MCP client (missing fields / date-time format)

Bug Description

Calling basic-memory.build_context with a valid memory://… URI fails schema validation in an MCP client. Other endpoints (search_notes, read_note) work as expected.

Steps To Reproduce

  1. Resolve a note:

    • Title: Techniques Elsa Can't Use
    • URI returned by search_notes: memory://conversations/20250429-Techniques_Elsa_Cant_Use

  2. Call:

    {"url":"memory://conversations/20250429-Techniques_Elsa_Cant_Use"}

via basic-memory.build_cont

Read the thread · 2025-08-21 · closed · external user · 11 comments

[BUG] BM loses track of note after editing it with vim

When I create a note in BM, edit it with vim (don't have to even change anything), BM cannot find it anymore. Running bm sync fixes this, but it isn't synced automatically.

Steps To Reproduce

bm tool write-note --title test --folder '' --content 'hello'
bm tool read-note test # works
vim test.md # don't change anything, just :wq
bm tool read-note test # doesn't find the note

Environment

  • OS: Debian GNU/Linux 12 (bookworm) podman container inside NixOS 25.05 (Warbler)
  • Python ve

Read the thread · 2025-08-07 · closed · external user · 8 comments

[BUG] Case sensitivity? Project switching fails due to inconsistent project name casing

Bug Description (Written by Claude)

Case sensitivity bug in project name handling where projects are stored with one case (lowercase "minerva") but displayed with different case (capitalized "Minerva"), causing project switching to fail because neither the displayed name nor the stored name work correctly. This prevents access to project content and breaks core functionality.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Start session with multiple projects available ("Minerv

Read the thread · 2025-06-11 · closed · external user · 8 comments

Add flag to disable project switching

Bug Description

The --project flag seems to be ignored when running certain commands. This is a problem especially when trying to run scoped MCP server with uvx basic-memory --project=... mcp.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Install version 0.12.3
  2. Run command bm project add work ~/basic-memory/work
  3. Use tool/feature bm --project=work project info or bm --project=work sync
  4. See that both commands don't apply to the work project, but to the defaul

Read the thread · 2025-05-08 · closed · external user · 10 comments

[BUG] Error status with Roo Code MCP.

Although it is green light but it reported error as below:

Processing request of type server.py:534 ListToolsRequest Processing request of type server.py:534 ListResourcesRequest Processing request of type server.py:534 ListResourceTemplatesRequest

Read the thread · 2025-04-03 · closed · external user · 8 comments

Most recent

Agents report saving to Basic Memory when no write happened (OpenClaw and Hermes)

Summary

In both the OpenClaw and Hermes integrations, the agent reported that it had saved something to Basic Memory when no write occurred. Two different harnesses, two different models, same failure: a confident success message with nothing behind it.

For a memory product this is close to the worst failure mode — the user believes the fact is captured and only finds out otherwise much later, if ever.

Case 1 — OpenClaw declined to write, then cited a file that doesn't exist

`/remember

Read the thread · 2026-08-27 · open · outside contributor · 3 comments

[BUG] bm schema validate <type> prints its result then never exits — interpreter shutdown blocks on a lingering thread

Bug Description

bm schema validate <note_type> never returns on the CLI. The server answers the underlying request in about 0.2 s (visible in basic-memory.log), and the CLI prints the Rich table header — then stalls indefinitely with the table half-drawn. The equivalent tool-path command, bm tool schema-validate --project main, validates every schema-covered note (499 notes) and returns JSON in 4 s, so this is specific to the bm schema validate command's output path, not to validatio

Read the thread · 2026-08-25 · closed · external user · 3 comments

write_note creates case-duplicate folders (schemas/ beside existing Schemas/)

Summary

When an AI assistant writes a note via MCP write_note with a directory that differs from an existing folder only by case, Basic Memory silently creates a case-duplicate folder instead of resolving to the existing one. A workspace ends up with both Schemas/ and schemas/ side by side.

Repro (happened in real use, 2026-08-25)

  1. Project my-team-4/lighthouse has an existing folder Schemas/ (containing Call.md, Client.md, Task.md — schema notes).
  2. User asks Clau

Read the thread · 2026-08-25 · closed · outside contributor · 1 comment

bm reindex --full completes its work but never exits, pinning one CPU core

Summary

bm reindex --full finishes all of its work but never exits. The process stays alive and pins exactly one CPU core indefinitely, doing zero syscalls. It has to be killed manually.

Environment

  • Basic Memory 0.23.0 (ghcr.io/basicmachines-co/basic-memory:latest, FastMCP 4.0.0b1)
  • Docker, SQLite backend
  • Semantic search enabled: fastembed / bge-small-en-v1.5, sqlite-vec vector index
  • Corpus: 573 markdown files (3.6 MB), 575 entities, 174 observations, 994 relations, 1

Read the thread · 2026-08-25 · open · external user · 1 comment

[BUG] Assistant-authored suggestions render but expose no accept/reject controls; only self-authored suggestions are actionable

Summary

Suggestions I create myself in the web app work correctly — they render in the review rail with working accept/reject. Suggestions originating from a connected assistant render in the note but expose no accept/reject affordance, so they can never be resolved.

This blocks the workflow the docs describe on the comments-and-suggestions page: "a connected assistant can review a note without immediately rewriting it," with the suggested prompt *"Review this note with comments and s

Read the thread · 2026-08-25 · closed · external user · 0 comments

[BUG] Case-only renames on macOS (case-insensitive APFS) fail via move_note and create duplicate index entries

Note: This issue was written with AI assistance, based on a real usage session.

Bug Description

On macOS with the default case-insensitive APFS volume, renaming notes or folders so that only the letter case changes misbehaves when done through the MCP tools. Several distinct problems: a case-only file rename is rejected, a case-only folder rename silently doesn't change the folder's case on disk, directory moves leave empty orphan directories behind, and case-only renames lea

Read the thread · 2026-08-19 · closed · external user · 2 comments

Document query/passage prefixes for asymmetric FastEmbed models

Thanks for basic-memory — it is the retrieval backbone of my lab's bilingual (EN/JP) research knowledge base, queried daily by both humans and agents, and the local-first design is exactly why we can run it on real research notes at all.

While tuning multilingual retrieval I found a small but consequential gap in the FastEmbed path, with a fix that looks well-contained. Details and measurements below.

Environment

  • basic-memory v0.22.1, sqlite backend
  • Embedding provider: FastEmbed (local

Read the thread · 2026-08-16 · closed · external user · 4 comments

Claude Code plugin hooks silently no-op on current release: hook CLI verb only exists on main (not in 0.22.1)

Summary — The marketplace plugin (installed per the plugin README) wires SessionStart/PreCompact hooks that exec basic-memory hook <event>. That hook verb was added to main around Jul 20 (PR #1070, SPEC-55) and is still in the CHANGELOG "Unreleased" section, while the latest release on both GitHub and PyPI is v0.22.1 (Jun 13). Since every failure path deliberately exits 0, both hooks silently never run — no briefing, no compaction checkpoint, no error.

Repro — Windows 11, basic-

Read the thread · 2026-08-07 · closed · external user · 3 comments

[BUG] write_note lowercases note_type while type matching stays case-sensitive, splitting one logical type into two populations

Bug Description

write_note(note_type="Task") stores type: task (lowercased) in the note's frontmatter, but type matching in schema_validate and search_notes (note_types=[...]) is case-sensitive. Notes whose frontmatter says type: Task (hand-written or migrated) and notes created through write_note end up as two separate populations that no single query covers, so type-wide validation silently reports only partial results.

Steps To Reproduce

  1. Install Basic Memory 0.22.1 and

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

Hermes provider inherits PYTHONPATH and fails to start bm MCP with mixed Python versions

Summary

The Hermes Basic Memory provider passes the full Hermes backend environment to the bm mcp subprocess.

Hermes Desktop adds its Python 3.11 site-packages to PYTHONPATH, while the Basic Memory uv tool runs on Python 3.12. The child process therefore imports Hermes's Python 3.11 version of pydantic and fails to start.

Environment

  • macOS
  • Hermes Agent v0.18.2
  • Hermes Python 3.11.15
  • Basic Memory 0.22.1
  • Basic Memory Python 3.12
  • Hermes integration: integrations/hermes

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

[BUG] write_note creates duplicate notes when existing file uses a different filename convention (kebab-case vs Title Case)

Bug Description

write_note silently creates a duplicate note when a note with the same title already exists but its file uses a different naming convention. With kebab_filenames: false, writing a note titled "Site Roadmap" creates Site Roadmap.md alongside an existing site-roadmap.md, instead of updating it.

The conflict detector in EntityService.resolve_permalink actually catches this case, but it only logs a warning and proceeds to create the duplicate anyway. The MCP client nev

Read the thread · 2026-07-16 · closed · external user · 0 comments

[BUG] Large cloud-project deletion errors opaquely; no documented way to purge a removed cloud project's data (hosted-tenant retention gap)

Bug Description

To be clear up front: bm project remove intentionally leaving files on disk is documented and reasonable for local projects — this issue is not asking to change that. It's about two things that follow specifically for cloud / hosted projects, neither of which is by-design:

  1. Opaque failure at scale (a bug). Deleting a large cloud project via delete_project (MCP) or bm project remove --cloud returns an empty, detail-free error, while small projects delet

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

[BUG] integrations/hermes: bm mcp processes leak

Bug Description

Every Hermes Agent session that uses the basic-memory memory provider spawns its own bm mcp subprocess.

In multi-session environments (gateway with slash_worker subprocesses), each worker creates its own agent → loads the basic-memory plugin → calls BasicMemoryProvider.initialize() → creates a new _BmMcpActor → spawns a fresh bm mcp. When workers exit (e.g. SIGTERM during gateway restart), the bm mcp child processes are orphaned and accumulate.

Observed on a pro

Read the thread · 2026-06-24 · closed · external user · 1 comment

[BUG] PermissionError during project scan triggers mass index deletion

Bug Description

When Basic Memory cannot read a project's root directory, a PermissionError is treated as a successful scan of an empty directory. The sync then interprets every indexed path as deleted and removes the entities from the database.

I hit this repeatedly with an Obsidian vault under macOS iCloud Drive. One MCP process was launched by an app that did not have permission to access ~/Library/Mobile Documents. The Markdown source files were not deleted, but the Basic Memory ind

Read the thread · 2026-06-20 · closed · external user · 3 comments

CLI write-note (and other tool subcommands) crash with 'function' object has no attribute 'fn' — no resolvable fastmcp version satisfies the 0.16.2 CLI bridge

Version: basic-memory 0.16.2 (pip), Python 3.13

What happens A fresh pip install basic-memory resolves fastmcp 3.4.2. Any basic-memory tool ... subcommand then fails:

$ echo "hello" | basic-memory tool write-note --title t --folder f
Error during write_note: 'function' object has no attribute 'fn'

The CLI bridge (basic_memory/cli/commands/tool.py) calls mcp_write_note.fn(...) — a fastmcp 2.x API. Under fastmcp 3.x the tool objects have no .fn.

Downgrading does not

Read the thread · 2026-06-10 · closed · external user · 1 comment

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