roboomp
2e431c0c21
`restoreQueuedMessagesToEditor` prepended queued text but appended queued images to `pendingImages`. Positional `[Image #N]` lookup at submit time therefore broke whenever the editor draft already held pending image(s): queued markers (numbered 1..K against their own image list) collided with draft markers (1..M) and resolved to the wrong images; queued images landing past slot M were orphaned. Add `shiftImageMarkers(text, offset)` to `image-references.ts` and have `restoreQueuedMessagesToEditor` walk each queued message in order, shifting its markers by the running pending-image count (existing draft images plus images already pulled in from earlier queued messages). Draft markers stay untouched because draft images keep their original slots. Paste markers are left alone — those are owned by the editor's paste store, not the pending-image buffer, and queued message text never carries unmaterialized `[Paste #N]` because the editor expands paste markers in `getExpandedText()` before `onSubmit` fires. Regression test seeds a draft image + a queued image-message in `input-controller-compaction-image.test.ts` (per acceptance) and locks the marker -> image mapping after restore. Unit tests for `shiftImageMarkers` cover the WxH tail, Paste-marker passthrough, and the zero-offset no-op. Fixes #2531
@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.