Files

T

roboomp 9abce6e974 fix(update): pinned npm registry and bypassed bun cache for omp update

omp resolves the update target by querying https://registry.npmjs.org/ directly, but `bun install -g pkg@<version>` would then consult bun's on-disk manifest snapshot AND honour the user's npm-mirror configuration (corporate proxy, Taobao, …). Either source can lag the upstream registry by minutes-to-hours, in which case bun rejects the version with `No version matching "X" found for specifier "@oh-my-pi/pi-coding-agent" (but package exists)` even though the registry omp just queried is serving it.

The bun install step now runs with both `--no-cache` (skip the manifest snapshot) and `--registry=https://registry.npmjs.org/` (pin the official catalog regardless of bunfig/.npmrc) so the install observes the same registry state the version check used. The registry URL is centralised in an `NPM_REGISTRY` constant shared by `getLatestRelease` and `buildBunInstallArgs`.

Fixes #1686

2026-06-02 06:18:54 +00:00

bench

perf(coding-agent): dedupe buildSessionContext walk on session-tree navigation

2026-04-27 03:55:14 +00:00

examples

feat(coding-agent): add assistant thinking renderers

2026-05-31 20:44:02 +08:00

scripts

fix(tiny): isolated tiny model worker in subprocess to skip onnxruntime napi crash

2026-05-31 21:02:25 +00:00

src

fix(update): pinned npm registry and bypassed bun cache for omp update

2026-06-02 06:18:54 +00:00

test

fix(update): pinned npm registry and bypassed bun cache for omp update

2026-06-02 06:18:54 +00:00

.gitignore

refactor: extract local:// URL normalization to shared utility

2026-04-18 22:40:07 +02:00

CHANGELOG.md

fix(update): pinned npm registry and bypassed bun cache for omp update

2026-06-02 06:18:54 +00:00

DEVELOPMENT.md

fix(history-storage): restored session_id column and prompt-history ranking

2026-06-02 05:15:56 +02:00

package.json

chore: bump version to 15.7.6

2026-06-01 19:24:27 +02:00

README.md

docs: clarify RenderMermaid usage

2026-05-09 03:11:18 +02:00

tsconfig.examples.json

refactor: restructured monorepo TypeScript config and build tasks for unified setup

2026-04-08 17:05:20 +02:00

tsconfig.json

refactor: restructured monorepo TypeScript config and build tasks for unified setup

2026-04-08 17:05:20 +02:00

tsconfig.publish.json

chore(config): organized publish type mapping from src to dist/types

2026-05-15 23:46:23 +02:00

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.