Skip to content

pi-observational-memory-jev

Pi observational memory where Jev answers keep/kind questions on history chunks, building a verbatim ledger and topic files.

ProjectbetaMIT

Overview

pi-observational-memory-jev keeps evidence that long Pi sessions otherwise lose, such as user constraints, errors that already happened and decisions that replaced earlier ones, without lossy summaries. It cuts history into chunks and asks Jev only keep and kind questions for each candidate line, storing the original line in a ledger; consolidation asks whether to promote an item into a durable topic file. Compaction is then a deterministic render of the ledger plus topic files, with no model writing text, and the transcript is never rewritten.

It follows the commands, clocks, ledger, footer gauges and .memory layout of Alvar's original observational memory extension but replaces the chat-model observer with TypeSafe Jev called directly at /v1/systemone; the two should not be installed together. It is off by default and toggled with /om on, with settings for chunk size, pool targets, compaction trigger, tail tokens, observer concurrency and Jev thresholds. MIT licensed.

What the decision model decides

TypeQuestionAnswers
Yes / noKeep this candidate line?yes · no
ChoiceWhat kind of item is it (constraint, error, decision, etc.)?—
Yes / noPromote this item into a durable topic file?yes · no

How it works

  1. Chunk session history.
  2. Ask Jev keep and kind per candidate; store originals in a ledger.
  3. Consolidate by asking whether to promote into topic files.
  4. Compact by rendering the ledger deterministically.

Strengths

  • No lossy summaries; original lines preserved.
  • Durable topic files across sessions.
  • Model-free compaction render.

Caveats

  • Conflicts with the original /om extension.
  • Requires a TypeSafe key.

Getting started

export TYPESAFE_API_KEY, pi install git:github.com/willfish/pi-observational-memory-jev, then /om on.

At a glance

Type
Project
Status
beta
Language
TypeScript
Runtime
Pi extension
Has code
yes
License
MIT

Use cases and integrations

How curated lists describe it

Frequently asked questions

Does Jev write summaries?

No, it only answers keep, kind and promote questions.

Can I use it with the original /om extension?

No, the commands collide.

Is it on by default?

No, enable it with /om on or enabledByDefault.

Related projects

  • Codex plugin that builds handoff packets by asking Jev whether each old read-only tool record should stay, keeping retained text verbatim.

    ProjectbetaJavaScript
  • Pi extension where Jev judges each completed tool call and result before compaction, keeping key evidence verbatim in the summary.

    PluginbetaTypeScript
  • OMP extension keeping one endless chat as a summary tree, with five Jev judge gates for rules, prefetch, compression, tools and recall.

    PluginprototypeTypeScript
  • Claude Code plugin and npm library that replaces the compaction summary with Jev keep, truncate or drop scores for every tool call.

    PluginbetaTypeScript
  • Cursor CLI plugin that asks Jev keep-or-drop nouls for each tool call and result, then re-injects kept facts after compaction.

    CLIbetaTypeScript
  • DeepSeek Harness plugin that asks Jev which tool results can be pruned early, delaying or avoiding lossy compaction.

    ProjectbetaTypeScript