# Reported issues for m1nd Pod holds 9 of 9 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 [m1nd](/mcp/m1nd). ## Most discussed ### Test: add an E2E case for `apply`/`apply_batch` with `verify=true` ## Context `apply` and `apply_batch` accept an optional `verify` flag. When `verify=true`, the server re-reads the written file, confirms it round-trips through ingest, and returns a `verify` block with `passed` / `node_delta` / `edge_delta` (single) or `passed` / `files_verified` (batch). This is the guard CI and agent harnesses rely on to catch silent write failures. [`CONTRIBUTING.md`](https://github.com/maxkle1nz/m1nd/blob/main/CONTRIBUTING.md) documents this contract in detail under **"Te [Read the thread](https://github.com/maxkle1nz/m1nd/issues/253) · 2026-07-04 · open · 1 comment ### Probe: does VS Code Copilot surface the MCP `instructions` string to the model? ## Context When a host connects to m1nd over MCP, m1nd sends an `instructions` string (the operating-loop doctrine) in the MCP `initialize` response. Whether a given host actually **surfaces** that `instructions` string to the model varies, and [`docs/HOST-INTEGRATION-MATRIX.md`](https://github.com/maxkle1nz/m1nd/blob/main/docs/HOST-INTEGRATION-MATRIX.md) tracks it per host. For **VS Code Copilot**, the `instructions`-render column is `[unverified]`. From the matrix (line ~114) and the §6c pro [Read the thread](https://github.com/maxkle1nz/m1nd/issues/251) · 2026-07-04 · open · 0 comments ### Verify the grok-cli fork's SessionStart injection field name (additionalContext vs additional_context) ## Context m1nd orients an agent by having a **SessionStart-family hook** emit a `north` packet into the agent's context. Different hosts name the injection field differently, and [`docs/HOST-INTEGRATION-MATRIX.md`](https://github.com/maxkle1nz/m1nd/blob/main/docs/HOST-INTEGRATION-MATRIX.md) tracks the exact field name per host so the shim can emit the right shape. The **grok-cli community fork** (`superagent-ai`) is graded **A (community)** but with an unverified field name. From §3.7 (line ~ [Read the thread](https://github.com/maxkle1nz/m1nd/issues/250) · 2026-07-04 · open · 0 comments ### Probe: does Goose's SessionStart stdout reach model context? (verify B→A promotion) ## Context m1nd integrates with agent hosts through a **SessionStart-family hook** that injects a `north` orientation packet as `additionalContext` before the agent's first turn. The host-capability research in [`docs/HOST-INTEGRATION-MATRIX.md`](https://github.com/maxkle1nz/m1nd/blob/main/docs/HOST-INTEGRATION-MATRIX.md) grades every host **A–D** by how completely it can carry that packet, and every claim is tagged `[verified-hands-on]`, `[verified-docs]`, or `[unverified]` — the tags are neve [Read the thread](https://github.com/maxkle1nz/m1nd/issues/249) · 2026-07-04 · open · 0 comments ### feat: export graph to Neo4j/Cypher format ## Motivation m1nd currently supports Mermaid export (used in the architecture diagram in the README). Adding Cypher export for Neo4j would open several use cases: - **Visual exploration**: Neo4j Browser and Bloom provide richer graph visualization than Mermaid can handle for large graphs - **Cypher queries alongside activation**: teams can run custom path queries (`MATCH (a)-[:CALLS*..3]->(b)`) against the same graph that m1nd activates - **Data engineering integration**: orgs with existing N [Read the thread](https://github.com/maxkle1nz/m1nd/issues/16) · 2026-03-14 · closed · 0 comments ### test: increase coverage for perspective.suggest and perspective.affinity ## Current state `test_perspective_usecases.py` covers the happy path for `perspective.start`, `perspective.follow`, `perspective.back`, and `perspective.peek`. However, `perspective.suggest` and `perspective.affinity` have minimal coverage. Running the test suite with coverage reveals: ``` m1nd-mcp/src/tools/perspective.rs suggest_handler 12.5% line coverage (1 of 8 branches tested) affinity_handler 8.3% line coverage (1 of 12 branches tested) ``` ## Missing test cases ### `p [Read the thread](https://github.com/maxkle1nz/m1nd/issues/13) · 2026-03-14 · closed · 0 comments ### feat: WebSocket transport for real-time graph updates ## Motivation The `m1nd-mcp` server is currently JSON-RPC over stdio only. This works well for MCP clients (Claude Code, Cursor, etc.) but limits what can be built on top of m1nd: - **GUI visualization** (`m1nd-ui`, already scaffolded) needs bidirectional communication - **Real-time plasticity updates**: as agents call `learn`, weight changes could be pushed to a dashboard without polling - **Browser-based tooling**: a web-based graph explorer cannot use stdio ## Proposed solution Add a WebS [Read the thread](https://github.com/maxkle1nz/m1nd/issues/12) · 2026-03-14 · closed · 0 comments ### docs: add video tutorial for first-time setup ## Problem The README has solid text instructions and the wiki has a detailed tool reference, but first-time users frequently ask in issues/DMs how to get from `cargo build --release` to their first useful `activate` result. Text walkthroughs have a high drop-off rate at the MCP config step — people aren't sure if the binary is running correctly before they see output. A video walkthrough would: - Show *exactly* what successful ingest output looks like (with timing) - Clarify the MCP config JS [Read the thread](https://github.com/maxkle1nz/m1nd/issues/11) · 2026-03-14 · closed · 0 comments ## Most recent ### feat: ast-grep pattern integration for scan tool ## Problem The `scan` tool in `m1nd-mcp` identifies suspicious patterns using heuristic regex against node identifiers (function names, file paths, import strings). This approach: - Produces false positives on minified or transpiled code - Cannot express structural patterns like *"all async functions that call X without awaiting"* - Requires maintaining a growing list of regex rules with no grammar awareness ## Proposed solution Integrate [`ast-grep-core`](https://crates.io/crates/ast-grep-c [Read the thread](https://github.com/maxkle1nz/m1nd/issues/8) · 2026-03-14 · closed · 0 comments The remaining reports are on [the project's issue tracker](https://github.com/maxkle1nz/m1nd/issues).