Skip to content

v0.1.1 — fix observe capture, add CRUD tools, honest skill gating - #3

Merged
rrader26 merged 4 commits into
mainfrom
fix/observe-raw-persist
Jul 22, 2026
Merged

v0.1.1 — fix observe capture, add CRUD tools, honest skill gating#3
rrader26 merged 4 commits into
mainfrom
fix/observe-raw-persist

Conversation

@rrader26

Copy link
Copy Markdown
Contributor

First patch release. Fixes a silent data-loss bug in observe and aligns the plugin with what the OSS engine actually does.

Fixes

  • observe no longer drops substantive input — the heuristic extractor only matched first-person rules (^I prefer, ^we decided) and silently discarded everything else (third-person statements, emails, most prose). Now, when no structured rule matches, substantive text is persisted verbatim as a raw observation. Smoke test: 1/4 → 4/4 statements captured. Questions/filler/code still filtered. (fix/observe-raw-persist)
  • Commodity CRUD MCP tools — added memory_delete, memory_supersede, memory_stats (OSS MCP surface 7 → 10). Un-breaks the forget/dream/stats/health skills that called them. Prediction / graph-reasoning / build-context remain hosted-only (the moat).
  • Honest skill gatingpredict/behaviors/why/context-loader/graph skills now carry a "requires hosted mode" banner so a local install degrades to search/recall instead of calling a missing tool. Plugin + marketplace descriptions retuned to lead with the local-first memory store.

Verification

  • 13 extraction tests + 21 core/mcp tests green
  • MCP tools/list over real stdio returns all 10 tools
  • observesearch roundtrip confirmed on a fresh DB

🤖 Generated with Claude Code

rrader2890 and others added 4 commits July 22, 2026 17:07
observe() ran only first-person-anchored rules (^i prefer, ^we decided) and
silently discarded everything else — third-person statements, emails, most
natural prose. A local user feeding raw text saw nothing persist, which
defeats the core 'feed it text and it remembers' UX.

Add a fallback in extract(): when no structured rule matches but the input is
substantive prose (not a question, not code, not an ack), persist it verbatim
as a raw 'observation' memory. Structured rules still win when they match;
hosted LLM extraction remains the premium that refines these into typed facts.

Fixes the smoke test: 1/4 -> 4/4 statements captured.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The OSS MCP server exposed 7 tools; the plugin's forget/dream/stats/health
skills call memory_delete / memory_supersede / memory_stats, which only
existed on the proprietary superset — so those skills errored on a local
install. These three are basic hygiene, not moat: the Storage trait already
implements delete/supersede/count_items. Wire them into the MCP surface.

OSS MCP surface: 7 -> 10 tools. Prediction / graph-reasoning / build-context
remain proprietary-only (the actual moat).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The plugin shipped predict/behaviors/why/context-loader/graph skills that call
MCP tools only the hosted engine registers (memory_predict, build_context,
graph_reason, query_graph, prefetch_related). On a local/OSS install they'd
error. Add a 'requires hosted mode' banner to each so the agent degrades to
search/recall instead of calling a missing tool; graph notes that BUILDING the
graph works locally, only reasoning needs hosted.

Retune plugin + marketplace descriptions to lead with the local-first memory
store (the OSS value) and frame prediction/behavior as the hosted upgrade,
rather than advertising moat features a local install can't run.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@rrader26
rrader26 merged commit 90fcb69 into main Jul 22, 2026
1 check failed
@rrader26
rrader26 deleted the fix/observe-raw-persist branch July 22, 2026 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants