Files

T

can1357androboomp 48877de084 fix(coding-agent): restored profile keybinding inheritance

Named profiles loaded keybindings only from their own agent dir
(~/.omp/profiles/<name>/agent), silently dropping user-level bindings
from ~/.omp/agent/keybindings.* — e.g. Backspace remaps under
tmux/QTerminal. KeybindingsManager.create now merges the default
profile's keybindings under the active profile's, with the profile file
overriding per binding. The inherited file is loaded read-only so a
named-profile run never writes migration output into the default
profile's dir. Documented the exception in docs/config-usage.md.

Adopted from PR #4869 (dropped its unrelated workflow-notice.md churn,
added the read-only inherited load and its regression test).

Fixes #4867

Co-authored-by: roboomp <omp@can.ac>

2026-07-09 18:27:22 +02:00

bench

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

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

examples

…

scripts

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

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

src

fix(coding-agent): restored profile keybinding inheritance

2026-07-09 18:27:22 +02:00

test

fix(coding-agent): restored profile keybinding inheritance

2026-07-09 18:27:22 +02:00

CHANGELOG.md

fix(coding-agent): restored profile keybinding inheritance

2026-07-09 18:27:22 +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.12

2026-07-08 19:40:13 +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.