omp integration

Recall’s native omp extension captures the active conversation into SQLite after each completed main-agent turn. It uses package.json#omp.extensions, not Pi compatibility loading or a second marketplace bundle.

Install from this checkout

Requires Bun, npm, and omp on PATH, plus an initialized Recall database. Capture was verified with omp 18.1.21; the strengthened E2E assertions were also verified with omp 18.2.0.

Build a clean package before linking. Linking the repository root would also expose development-only configuration, such as its .mcp.json, to omp.

bun install
bun run build
bun dist/index.js init
mkdir -p "$HOME/.agents/Recall/omp-package"
archive=$(npm pack --pack-destination "$HOME/.agents/Recall/omp-package" --ignore-scripts)
tar -xzf "$HOME/.agents/Recall/omp-package/$archive" -C "$HOME/.agents/Recall/omp-package"
omp plugin link "$HOME/.agents/Recall/omp-package/package"

Restart omp after linking. /reload-plugins does not reload extension modules. Keep the extracted directory in place for the lifetime of the link. To update a development install, rebuild and repeat the pack/extract steps, then restart omp.

Do not install the npm package named recall-memory; that name is an unrelated project (#312). Keep using the packed checkout above.

Capture contract

The awaited session_stop event runs after the main agent and its background work settle. omp does not emit it for task/subagent sessions.
The extension reads ctx.sessionManager.getBranch() and sends ordered user/assistant text to its package-local dist/index.js capture (stdin JSON, contract 1, harness omp, event turn_end). No global recall executable is required. Door: Capture adapter.
Tool calls/results, thinking, images, developer/system instructions, and custom/summary entries are excluded before that call.
The extension scrubs secrets before sizing and trimming. Core scrubs again, tags the row automatic-capture,omp, and stores it at importance 6. This is not a model-backed extraction or a curated fabric call.
The database defaults to ~/.agents/Recall/recall.db; RECALL_DB_PATH retains its existing override.

This is turn-completion capture, not crash recovery. An interrupted turn before session_stop is not guaranteed captured. Shutdown and pre-compaction hooks are not installed. The active branch is read again on the next stop after a failure.

After a successful capture, the extension opens the database read-only to check curation freshness. It detaches the package-local recall loa omp-end <sessionId> worker when the session has published lifecycle messages and its Curated entry is missing or its source pins differ from those messages, provided no worker holds the session lock. Revisiting an earlier snapshot also triggers curation. The worker releases its lock and checks again before finishing so a capture that deferred to it is still covered.

The worker uses the configured Curated Extractor, Fabric by default, and creates one separate entry tagged curated,omp. Later successful extracts replace that entry’s body, source pins, message count, and snapshot cursor while retaining its ID. Only the session’s ordered published lifecycle messages are extracted; explicit dumps on the same session stay separate. A changed extract invalidates the entry’s old embedding; this worker does not generate a replacement embedding. Extraction failure leaves the basic summary and any previous Curated entry unchanged; a later successful capture can retry curation. Basic capture continues to work without Fabric.

Capture bounds its CLI child to 30 seconds and its serialized JSON payload to 25 MiB, including metadata, escaping, and the truncation marker. Excluded content does not count toward this limit. When the scrubbed text would exceed the limit, capture allocates 60% of the remaining JSON-escaped byte budget to the beginning and 40% to the end of the text, separated by [Recall omp capture truncated]; a warning reports the UTF-8 bytes dropped from the scrubbed text. Malformed branches are rejected before starting the child; malformed branches, cancellations, and child failures warn without stopping omp.

Explicit dump: `recall_dump` tool

The extension also registers a recall_dump tool (title, optional project, tags, continues, skip_fabric). It reads the live branch and session id from omp, so it dumps this conversation on any profile or branch, and sends it to the package-local dist/index.js dump --stdin. The tool asks you to confirm in the omp UI before writing anything and refuses in headless sessions. Without --stdin, recall dump run from a shell inside omp (OMPCODE=1) refuses and points to the tool: native transcript discovery cannot identify the live omp conversation.

Dump payloads are limited to 25 MiB, and the CLI child has a five-minute timeout. skip_fabric defaults to false; set it to true for a basic summary. Shared message scrubbing and default project attribution follow the Session Dump contract.

Skills and MCP remain separate

recall install still links the nine canonical do-recall-* skills into ~/.omp/agent/skills/ when omp is detected. It does not activate this extension. The native package does not duplicate those skills, register MCP, or inject session-start memory; recall_dump is its only tool. Existing manual MCP configuration remains untouched.

Verify and remove

omp plugin list
bun run test:e2e:omp
omp plugin uninstall recall-memory

The runtime check packs the distributable, links it into a disposable omp home, and uses the packaged CLI for initialization, capture, and search. A deterministic localhost model drives real headless omp turns. The check compares exact ordered roles and text, preserves earlier message IDs and native keys across resume, and verifies search results. After uninstall, it requires a third model request and the expected assistant answer before checking that the complete captured snapshot remains unchanged.

During the script, before-and-after checks compare existence, size, modification time, and inode for the default production database, its WAL and SHM files, and the default omp plugin lockfile. These checks do not prove byte-identical preservation of all live state, cover nondefault production locations, or cover the preceding build. Test children receive disposable configuration and database paths, not live model credentials. Executables still resolve through inherited PATH; this is not a network or filesystem sandbox.

This verifies the packed local-link integration in headless text mode. It does not exercise npm registry installation, real model providers, interactive sessions, compaction, subagents, or failure recovery.

Restart omp after uninstalling. Saved Recall memory remains. recall uninstall removes installer-owned skills, not the separately managed omp plugin; uninstall the plugin through omp before removing Recall’s runtime.

If capture warns, check bun is available to omp, run bun dist/index.js init from the linked checkout, and check RECALL_DB_PATH permissions. An omp process started before the extension was refreshed keeps the old code until it restarts: older versions measured the whole raw branch and warned payload exceeds 25MiB on long tool-heavy sessions. See the capture contract for current payload limits and trimming behavior.