roboomp
c7d9abbcfd
The first pass only enumerated non-wildcard `exports` entries, so patterns like pi-ai's `./oauth/*` left every concrete target (`@oh-my-pi/pi-ai/oauth/anthropic` and friends) outside the bundled registry. Compiled-mode resolution then fell back through `Bun.resolveSync` → original peer specifier → missing peer dep, reproducing the original `Cannot find module` failure for any plugin that imports a wildcard-only subpath (e.g. `@mariozechner/pi-ai/utils/oauth/anthropic`, remapped via PI_SUBPATH_REMAPS). The generator now runs a second pass over wildcard exports, parses each single-asterisk pattern into prefix/suffix halves, globs the matching source directory, and emits a registry entry per concrete `.ts` file. Root catch-all wildcards (`./*` / `./*.js`) are skipped on purpose — they'd static-import top-level files like the coding-agent's own `cli.ts` and explode the bundle through the binary entry's transitive graph. Test, `.d`, `.generated`, `.bench` files and `index` basenames are filtered out so the registry stays focused on importable surfaces. A new test case in test/extensibility/legacy-pi-bundled-subpath-overrides.test.ts asserts the reviewer's cited `@oh-my-pi/pi-ai/oauth/anthropic` key now routes through the virtual namespace and that root catch-all wildcards remain unbundled. Fixes #3442
@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; writesmemory_summary.mdand 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 exposesretain,recall, andreflect.
Hindsight quickstart
- Run a Hindsight server (Cloud or
docker run -p 8888:8888 ghcr.io/vectorize-io/hindsight:latest). - Set
memory.backend = "hindsight"andhindsight.apiUrl = "http://localhost:8888"(or your Cloud URL). - Optional environment overrides (env wins over settings):
HINDSIGHT_API_URL,HINDSIGHT_API_TOKEN— connectionHINDSIGHT_BANK_ID,HINDSIGHT_DYNAMIC_BANK_ID,HINDSIGHT_AGENT_NAME— bank addressingHINDSIGHT_AUTO_RECALL,HINDSIGHT_AUTO_RETAIN,HINDSIGHT_RETAIN_MODE— lifecycleHINDSIGHT_RECALL_BUDGET,HINDSIGHT_RECALL_MAX_TOKENS— recall sizingHINDSIGHT_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.