Skip to content

T-34: Memory governance and Hindsight exploration surface - #116

Merged
jaesbit merged 1 commit into
develfrom
auto-work/t34-manage-autonomous-omp-memory-deck
Jul 16, 2026
Merged

T-34: Memory governance and Hindsight exploration surface#116
jaesbit merged 1 commit into
develfrom
auto-work/t34-manage-autonomous-omp-memory-deck

Conversation

@jaesbit

@jaesbit jaesbit commented Jul 16, 2026

Copy link
Copy Markdown
Owner

What

Governance + exploration for OMP's own session-memory subsystem (Hindsight
remote / Mnemopi local SQLite / local rollout summaries) — distinct from the
deck's KB (/kb, hand-tended long-term knowledge).

  • Settings governance (GET/PATCH /api/memory/settings, MemorySettingsSection):
    a curated, credential-free whitelist (backend select, auto-recall,
    auto-retain, scoping, Hindsight API URL/bank) projected from OMP's own
    settings store — same pattern as delegation governance (T-28). Credential
    fields (hindsight.apiToken, mnemopi.llmApiKey, mnemopi.embeddingApiKey)
    are excluded outright, never read or written through this surface.
  • Hindsight explorer (apps/server/src/hindsight-explorer.ts,
    routes-memory.ts): the only memory backend with a credential-safe HTTP API
    that works without a live agent session. Per-project bank scope is resolved
    server-side from cwd (never client-supplied), gated on memory.backend
    actually being "hindsight" so a switched-off backend can't be browsed or
    mutated. Covers recall traceability, memory/document browsing, document tag
    edit/delete, and mental model create/refresh/delete.
  • Mnemopi / local: reported as configured-but-not-explorable with an
    explanatory message — their read/write surface (MemoryBackend.status/search/save,
    MnemopiSessionState.editScopedMemory) is wired to a live AgentSession's
    in-memory state in the SDK, with no sessionless seam to fabricate safely.
  • New standalone /memory view + nav entry, deliberately separate from /kb.

Verification

  • bun test — server 885/885, web 190/190 (24 new in routes-memory.test.ts).
  • tsc --noEmit — clean on all touched files (server + web), only
    pre-existing baseline diagnostics remain elsewhere (session-monitor.*,
    engine.test.ts).
  • vite build — clean.
  • E2E smoke against an isolated scratch instance (own port/HOME/DB, headless
    Chromium via CDP): Memory nav entry renders distinct from Knowledge,
    backend switch persists and live-refreshes the scope card, Hindsight
    explorer renders and a real recall call against an unreachable Hindsight
    server surfaces a clean 502 (no crash, no leaked internals), Mnemopi
    correctly reports non-explorable.

Task: T-34

Governs OMP's own session-memory subsystem (backend select, auto-recall,
auto-retain, scoping) via a curated, credential-free settings whitelist
projected from OMP's own settings store — same pattern as delegation
governance (T-28). Adds a sessionless Hindsight explorer (the only memory
backend with a credential-safe HTTP API outside a live agent session):
per-project bank scope resolution, recall traceability, memory/document
browsing, document tag edit/delete, and mental model create/refresh/delete.

Mnemopi (local SQLite) and the local summary pipeline have no sessionless
read/write seam in the SDK — the deck reports them as configured-but-not-
explorable rather than fabricating a fake session to reach them.

New standalone /memory view and nav entry, distinct from /kb.
@jaesbit
jaesbit merged commit fb3a3bb into devel Jul 16, 2026
@jaesbit
jaesbit deleted the auto-work/t34-manage-autonomous-omp-memory-deck branch July 16, 2026 10:24
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.

1 participant