Reported issues for io.github.Abhigyan-Shekhar/Waggle-mcp

Pod holds 22 of 45 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 io.github.Abhigyan-Shekhar/Waggle-mcp.

Most discussed

[feature] Add memory export preview before saving to JSON/Markdown

Problem or use case

Currently, users can export stored memory, but there is no preview of the content before the export is written to disk. A preview would help users verify the data and avoid exporting unnecessary or sensitive information.

Problem

Users cannot inspect exported content beforehand.
Accidental export of unwanted memory entries is possible.
Large exports are difficult to verify after the file has already been generated.

Proposed solution

Add a --preview fla

Read the thread · 2026-07-18 · closed · external user · 4 comments

Add memory usage statistics to the waggle-mcp doctor command

Problem or use case

The waggle-mcp doctor command verifies the installation and configuration of Waggle, but it does not provide any information about the current memory database.

Users cannot quickly check how much memory has been stored, how many nodes or edges exist, or which backend and embedding model are currently being used. This makes it harder to verify that Waggle is actively storing and retrieving memory.

Proposed solution

Extend the waggle-mcp doctor command to includ

Read the thread · 2026-07-11 · open · external user · 4 comments

[Feature Request]: Add a doctor --json mode for structured diagnostics

Problem or use case

Currently, the waggle-mcp doctor command is incredibly useful for human users to troubleshoot their configuration and setup. However, the output is formatted as plain text, making it difficult for automation scripts, issue templates, or other tooling to parse the diagnostic results reliably.

Proposed solution

Add a --json flag to the waggle-mcp doctor command. When this flag is passed, the tool should output the diagnostic results as a structured, machine-rea

Read the thread · 2026-06-12 · closed · outside contributor · 4 comments

[bug] : Malformed numeric environment variables bypass configuration validation and crash startup

Summary

Malformed numeric environment variables cause startup failure during configuration loading. AppConfig.from_env() performs direct int() and float() conversions on environment variables before configuration validation is executed.

As a result, invalid values such as:

$env:WAGGLE_RATE_LIMIT_RPM="abc"

$env:WAGGLE_HYBRID_VECTOR_WEIGHT="abc"

cause raw Python ValueError exceptions during startup instead of being surfaced through Waggle's

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

bug(networking): socket_recv assumes recv(4) returns the full TCP length header

Summary

socket_recv() assumes that a single recv(4) call will always return the complete 4-byte TCP length header. TCP does not guarantee this behavior, and fragmented reads can cause struct.unpack() to fail when fewer than 4 bytes are returned.

Steps to reproduce

Open src/rlm/core/comms_utils.py
Locate socket_recv()
Observe that the length header is read using:

raw_len = sock.recv(4)
length = struct.unpack(">I", raw_

[Read the thread](https://github.com/Abhigyan-Shekhar/Waggle-mcp/issues/269) · 2026-06-06 · open · external user · 5 comments

### perf(graph): dedup_candidates is quadratic over all candidate pairs

File: src/waggle/graph.py:6979-7025

dedup_candidates() builds every compatible node pair in a nested loop and computes cosine similarity for each pair. That is O(N^2) over the filtered node set, so the cost grows rapidly as tenant history grows.

Impact: the duplicate-review endpoint becomes CPU-bound on large tenants and can dominate request latency long before the graph is truly massive. A surgical fix would need an index or approximate candidate pruning step before pairwise comparison.

[Read the thread](https://github.com/Abhigyan-Shekhar/Waggle-mcp/issues/197) · 2026-06-01 · open · outside contributor · 4 comments

### docs: add requirements.txt so contributors can install dependencies easily

### Documentation gap

This project does not have a `requirements.txt` file. The README itself.
acknowledges this in saying:
No requirements.txt file provided; please install the 
core libraries by hand.”
This creates friction for new contributors and users that 
First time cloning the repo.
_

### Relevant page or file

_No response_

### Proposed improvement

Create a `requirements.txt` file in the root of the repo
with the following content:
discord.py>=2.0.0
python-dotenv>=1.0.0
And update t

[Read the thread](https://github.com/Abhigyan-Shekhar/Waggle-mcp/issues/184) · 2026-06-01 · closed · external user · 6 comments

### [bug]: graph_delete_edge uses graph:read instead of graph:write scope

### Summary

The `graph_delete_edge` endpoint currently authorizes requests using:

```python
_require_http_scope(request, "graph:read")

However, edge deletion is a graph mutation operation, and other graph mutation endpoints require graph:write.

This creates an authorization scope mismatch and may allow clients with read-only permissions to delete graph edges.

For consistency with other graph mutation endpoints, graph_delete_edge should require graph:write permissions.

Steps

Read the thread · 2026-05-29 · closed · external user · 4 comments

Most recent

[bug] ImportError: cannot import name 'request_ctx' from mcp.server.lowlevel.server on fresh install (waggle-mcp 0.0.1, mcp 2.1.1)

Summary

Running waggle --help immediately after a fresh pip install crashes with an ImportError. waggle/server.py imports request_ctx from mcp.server.lowlevel.server, but this name does not exist in mcp 2.1.1, the version currently resolved by pip when installing waggle-mcp. The CLI is completely unusable out of the box for new users.

Steps to reproduce

pip install waggle-mcp
waggle --help
Observe ImportError instead of the expected help output

Expected behavior

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

[Feature] Add a Scroll-to-Top button for improved navigation

Problem or use case

Users reading long documentation pages or navigating through the website need to manually scroll back to the top after reaching the bottom. This can become inconvenient as more content is added and affects the overall browsing experience.

A built-in scroll-to-top button would provide quicker navigation and improve usability.

Proposed solution

Add a floating "Scroll-to-Top" button that appears once the user scrolls beyond a certain distance.

Expected behavior

Read the thread · 2026-07-14 · closed · outside contributor · 2 comments

[bug] Neo4j _next_transcript_turn_index ignores project/agent_id — turn-index collisions across scopes

Summary

The Neo4j backend computes the next transcript turn_index from only tenant_id + session_id, while the SQLite backend also scopes by project and agent_id. When the same session_id is reused across different projects/agents within a tenant, Neo4j assigns colliding turn_index values, whereas SQLite keeps per-(session, project, agent) sequences.