omp-optchat
OMP extension keeping one endless chat as a summary tree, with five Jev judge gates for rules, prefetch, compression, tools and recall.
Overview
OMP OptChat implements Victor Taelin's OptChat specification for Oh My Pi: one durable chat whose every message, tool call and subagent report is appended to a local fsynced log, a binary tree of contextual summaries, and a fresh model context each turn. The model sees a fixed-size view of one-line summaries and navigates to originals with zoom, chat_search, date and work tools, so long chats stop growing the context while nothing is deleted.
Five small System One gates run through OMP's judge role (Jev): keeping standing rules across turns, prefetching relevant history before a turn, hinting the compressor about what matters, screening risky tool calls, and powering chat_recall, which walks the summary tree by picking a branch at each level. Each gate has its own opt-out flag, and omp --no-optchat runs a plain session. The list summary notes the gates send judged text to the judge's provider and that there is no licence file.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Which branch of the summary tree leads to the answer to this question? | — |
| Yes / no | Is this tool call risky?(inferred) | yes · no |
| Yes / no | Is this standing rule relevant to the current turn?(inferred) | yes · no |
How it works
- Append every event to the local log.
- Build a fixed-size summary view for each turn.
- Run judge gates for rules, prefetch, compression hints and tool screening.
- Use zoom, search or judged recall to retrieve originals.
Strengths
- Bounded context for arbitrarily long chats.
- Nothing is lost; originals remain retrievable.
- Each gate can be disabled individually.
Caveats
- Extra compressor and judge calls per message.
- Judged text is sent to the judge provider.
- No licence file.
Getting started
Install the extension into OMP; run omp --no-optchat to disable it for a session.At a glance
- Type
- Plugin
- Status
- prototype
- Language
- TypeScript
- Runtime
- Oh My Pi extension
- Has code
- yes
Use cases and integrations
How curated lists describe it
OMP plugin for one endless chat kept in a binary tree of summaries, with five Jev gates through OMP's `judge` role: standing rules, history prefetch, compression hints, tool-call screening and recall. The gates send judged text to the judge's provider. No licence file.
MrJev/awesome-jev
Frequently asked questions
What do the Jev gates do?
Keep standing rules, prefetch history, guide compression, screen risky tool calls and drive recall through the summary tree.
Is any history deleted?
No, the log is append-only and originals are retrievable.
Can I turn it off?
Yes, per gate, or entirely with omp --no-optchat.
Related projects
Codex plugin that builds handoff packets by asking Jev whether each old read-only tool record should stay, keeping retained text verbatim.
ProjectbetaJavaScriptPi extension where Jev judges each completed tool call and result before compaction, keeping key evidence verbatim in the summary.
PluginbetaTypeScriptPi observational memory where Jev answers keep/kind questions on history chunks, building a verbatim ledger and topic files.
ProjectbetaTypeScript- mu★ 504
Pi-based coding agent where a small judge (Jev by default) answers yes/no, choice and score questions at 38 decision points per turn.
CLIprototypeTypeScript - fast-jev-compaction★ 7,616
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