Reported issues for Monet

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 Monet.

Most discussed

memory_declare writes a declared principle into an ARCHIVED circle with no disclosure — the row lands outside store-wide recall

External contributor report (monet-e2e RE-55, verified 2026-08-30 on @team-monet/monet 1.9.1).

When a rule/principle is declared via memory_declare into an archived circle, the write succeeds but the receipt carries no archived/guidance/landedInArchivedCircle signal — unlike memory_store (#78) and memory_checkpoint (#101), which now disclose an archived landing.

Reproduction (isolated store): anchor circle → archive it → memory_declare{species: principle} → receipt keys are only {`action

Read the thread · 2026-08-30 · open · external user · 0 comments

slow-queries.jsonl is write-only — no doctor/CLI/MCP surface reads the slow log

Summary

livingModelCard discards the ranking score + per-signal breakdown, returning only {id,title,kind,confidence,supportCount}. The ordering is opaque — a caller sees a concept ranks high but not why (recency vs usefulness vs arousal). Demonstrated: a 4x-fetched concept (usefulness signal) ranked LAST with no numeric signal to explain it.

Reproduction

XFAIL test: monet-e2e tests/test32_re32_living_model_score_opacity.py (exit 2).
memory_overview → livingModel cards carr

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

slow-queries.jsonl is write-only — no doctor/CLI/MCP surface reads the slow log

Summary

gate_events has no retention/pruning. Each stage_lookup call (recognized matcher) writes one gate_events row — including misses — and no surface (gate/doctor/status/resegment/--help or the 23 MCP tools) reports or prunes them. The table grows with agent activity and will become the largest table in the store.

Reproduction

XFAIL test: monet-e2e tests/test29_re26_gate_events_retention.py (exit 2).
Declare a stage + domain advisory rule, fire 130 `stage_lo

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

Fallback caller identity makes source invisibility undiscoverable — source_list returns [] with no signal

Summary

When MONET_CALLER_ID/MONET_PROJECT_ID are unset, monet start derives a fallback identity (local-agent / <basename>-<sha8>). As a result source_list silently returns [] and source_status/source_path/source_sync return the non-disclosing "source is unavailable" — the identity mismatch is not discoverable (a caller sees a clean "no sources" state).

Reproduction

XFAIL test: monet-e2e tests/test26_re23_source_identity_discoverability.py (exit 2).
CONTROL

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

agents/stig.md omits the memory_checkpoint / memory_workstreams tool names — agents never discover them

Why

with-monet#68 (closed today) carried the workstream capture model onto agents/stig.md's # Work section — the "session's working state" line — but deliberately omitted tool names: "no procedure text — the tool descriptions carry the how." That premise only holds once the agent has found the tool. A persona that names a concept but not the tool gives the agent no reason to read that tool's schema.

Evidence (live failure, 2026-08-12)

A downstream agent (Hermes/Coda) upgraded

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

memory_store ignores explicit circle param, writes to session circle instead

Describe the bug

memory_store ignores the explicit circle parameter and always writes to the Hermes session circle (e.g., hermes-agent-6018c90a) instead.

Steps to reproduce

Call mcp_monet_memory_store with circle="coda" and any content
The observation is written to hermes-agent-<random-session-id> circle, not coda

mcp_monet_memory_store({
  content: "test observation",
  circle: "coda",       // ← ignored
  kind: "fact"
})
// Result: circle = "hermes-agent-601

[Read the thread](https://github.com/team-monet/monet/issues/1) · 2026-06-23 · closed · external user · 1 comment

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/team-monet/monet/issues).