Files

T

Hugo Lopes d9417927bc fix(compaction): surface the frame rescue as a real compaction to the TUI and extensions

Review follow-ups (Codex on #6362):
- #rescueSnapcompactFrameOverflow now returns the CompactionResult and emits
  session_compact for the rebuilt entry, so extensions see the entry that is
  actually active instead of (only) the one the rescue superseded.
- The no-preparation auto_compaction_end now carries that result instead of
  {result: undefined, skipped: true} when the rescue rewrote history — the
  TUI rebuilds the transcript on result, so a successful rescue is no longer
  presented as a benign no-op.

Claude-Session: https://claude.ai/code/session_014rh4JyWFkxgMhgFaEf8VBY

2026-07-23 12:59:15 +02:00

bench

Merge PR #5947 : perf(session): memoize convertToLlm and estimateTokens over settled history (@roboomp)

2026-07-18 19:42:52 +02:00

examples

refactor(coding-agent): consolidated tool surface onto xd:// devices and hub

2026-07-15 15:16:29 +02:00

scripts

fix(coding-agent): lazily loaded compiled extension modules

2026-07-15 10:54:13 +00:00

src

fix(compaction): surface the frame rescue as a real compaction to the TUI and extensions

2026-07-23 12:59:15 +02:00

test

fix(compaction): surface the frame rescue as a real compaction to the TUI and extensions

2026-07-23 12:59:15 +02:00

CHANGELOG.md

fix(compaction): rescue trailing snapcompact archives past the maintenance threshold

2026-07-23 11:31:00 +02:00

DEVELOPMENT.md

feat(coding-agent): added opt-in task prewalk and tightened --tools and xdev behavior

2026-07-15 18:39:36 +02:00

package.json

feat(diff): implemented native UTF-16 diff processing and removed jsdiff

2026-07-23 01:35:31 +02:00

README.md

…

tsconfig.examples.json

…

tsconfig.json

…

tsconfig.publish.json

…

README.md

@oh-my-pi/pi-coding-agent

Core implementation package for the omp coding agent in the oh-my-pi monorepo.

For installation, setup, provider configuration, model roles, slash commands, and full CLI reference, see:

Package-specific references:

Memory backends

The agent supports three mutually-exclusive memory backends, selected via the memory.backend setting (Settings → Memory tab, or ~/.omp/config.yml):

off (default) — no memory subsystem runs.
local — existing rollout-summarisation pipeline; writes memory_summary.md and consolidated artifacts under the agent dir.
hindsight — talks to a Hindsight server (Cloud or self-hosted Docker), retains transcripts every Nth user turn, recalls memories on the first turn of a session, and exposes retain, recall, and reflect.

Hindsight quickstart

Run a Hindsight server (Cloud or docker run -p 8888:8888 ghcr.io/vectorize-io/hindsight:latest).
Set memory.backend = "hindsight" and hindsight.apiUrl = "http://localhost:8888" (or your Cloud URL).
Optional environment overrides (env wins over settings):
- HINDSIGHT_API_URL, HINDSIGHT_API_TOKEN — connection
- HINDSIGHT_BANK_ID, HINDSIGHT_DYNAMIC_BANK_ID, HINDSIGHT_AGENT_NAME — bank addressing
- HINDSIGHT_AUTO_RECALL, HINDSIGHT_AUTO_RETAIN, HINDSIGHT_RETAIN_MODE — lifecycle
- HINDSIGHT_RECALL_BUDGET, HINDSIGHT_RECALL_MAX_TOKENS — recall sizing
- HINDSIGHT_BANK_MISSION, HINDSIGHT_DEBUG

Switching backends mid-session is honoured on the next system-prompt rebuild and the next /memory slash command. Existing users with memories.enabled = true|false are migrated to memory.backend = "local"|"off" exactly once on first launch.