Local-first 🧠memory for Hermes Agent that lives in your Obsidian vault and remembers project context. Nightly 😴 dream passes turn repeat corrections into confirmed preferences with measurable confidence. Adapters ship for Claude Code, Codex, and OpenClaw, with an MCP server for anything else.
TypeScript
Configurable default_scope for feedback signals implementation plan
Branch: feat/default-scope-feedback
Design: docs/brainstorm/default-scope-feedback/design.md
t_d8a58683 - [upstream:mnemosyne] feat(hermes): configurable default_scope for remember()/feedback calls
Files
src/core/brain/types.tssrc/core/brain/policy.tssrc/core/brain/signal.tssrc/mcp/brain/feedback-tools.tssrc/cli/brain/verbs/feedback.ts- Existing focused tests for Brain config validation, signal writing, CLI feedback, and MCP feedback, with new tests added where coverage is missing
docs/cli-reference.mddocs/mcp.mdCHANGELOG.md
Acceptance
A focused test suite passes that proves:
- With no
feedback.default_scopeand no explicitscope, signal output remains unchanged and omitsscopefrontmatter. - With
feedback.default_scope: codingand no explicitscope, bothbrain_feedbackando2b brain feedbackwrite signals withscope: codingand the normal scope tag behavior. - With
feedback.default_scope: codingand explicitscope: docs, the explicit scope wins for both CLI and MCP paths. - Invalid configured defaults are rejected or surfaced through normal config validation/doctor behavior rather than silently ignored.
- Force-confirmed preference creation uses the same effective scope as the signal when a default applies.
Suggested verification command for the worker:
bun test <focused config test> <focused signal test> <focused CLI feedback test> <focused MCP feedback test>
bun run typecheck
Depends on
No sibling card needs to land first. This is the only in-scope implementation card for the patch release and should be driven on feat/default-scope-feedback under TDD.