Files

T

can1357 0006252d6e test(utils): validated tool error handling and cleanup signal propagation

- Added comprehensive test suite for `postmortem` utility error handling, covering cleanup symbol marking, cause chain depth validation, and process exception suppression.
- Added tests for `browser-run-cancellation` ensuring proper `unhandledRejection` suppression and correct `ToolAbortError` propagation during teardown.
- Implemented `collectUnhandledRejections` helper to verify silence of process-level rejections during async race conditions in browser runs.
- Added integration-style probe tests for `postmortem` to verify that marked cleanup errors allow process survival while unmarked ones remain fatal.

2026-07-06 08:07:25 +02:00

bench

fix(coding-agent): wire reveal bench callbacks correctly

2026-07-01 21:47:54 +02:00

examples

feat: added standalone snapcompact package and model-specific frame shaping

2026-06-10 21:50:03 +02:00

scripts

fix(plugins): drain subprocess pipes concurrently with proc.exited

2026-07-02 08:33:32 +00:00

src

feat(tui): relocated terminal restore registration to tui init

2026-07-06 08:07:24 +02:00

test

test(utils): validated tool error handling and cleanup signal propagation

2026-07-06 08:07:25 +02:00

CHANGELOG.md

feat(coding-agent): constrained nested task rendering to prevent overflow

2026-07-06 08:07:24 +02:00

DEVELOPMENT.md

feat: consolidated and automate changelog management

2026-06-27 03:08:52 +02:00

package.json

chore: bump version to 16.3.9

2026-07-06 04:19:29 +02:00

README.md

feat: removed render_mermaid tool and added width-aware Mermaid clipping

2026-06-16 21:32:39 +02:00

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.