can1357
c5e3698f45
Legacy Pi extensions were mirrored module-by-module into a flat temp dir (`omp-legacy-pi-file/entry-<hash>/`) with imports rewritten to absolute URLs. Running from that temp root made `import.meta.url`/`__dirname` resolve to the mirror, so `readFileSync(join(__dirname, "ui.html"))`-style asset loads ENOENT'd — e.g. @plannotator/pi-extension's HTML never loaded and it auto-approved plans (#1674). The standing remedy (#1675) copied ~30MB of .html/.css per startup with a fragile extension whitelist. Bun's runtime plugins don't fire onResolve for transitive imports, which is why the mirror pre-resolved everything. But onLoad does fire transitively for file-namespace modules matching its filter, and a real file import keeps import.meta.url pointing at the source. So: - Load the extension entry in place via `import(pathToFileURL(real))`; realpath first so the path matches what Bun hands onLoad (macOS /var->/private/var, bun link/pnpm symlinks). - Register one Bun.plugin() onLoad per extension *package root* (nearest package.json), filtered to that root's .js/.ts but excluding any node_modules segment, that rewrites only `@(scope)/pi-*` and the bare `@sinclair/typebox` specifier to absolute bundled/shim URLs. - Everything else — relative siblings (incl. ../src), the extension's own node_modules deps (CJS/ESM), and bundled assets — resolves natively. Removes the flat mirror, the temp-dir writes, the asset-copy problem, and the now-dead `omp-legacy-pi-file:` namespace machinery. import.meta.url is the real source file, so assets resolve exactly as under the original Pi runtime. Adds an in-place load regression test covering asset reads, submodule .css siblings, node_modules-excluded native deps, and package-root-scoped ../src rewrites. Fixes #1674.
@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:
- CHANGELOG
- MCP configuration guide
- MCP runtime lifecycle
- MCP server/tool authoring
- DEVELOPMENT
- RenderMermaid guide
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.