roboomp
337ec0d16c
Idle recap crashed with `TypeError: undefined is not an object (evaluating 'H.content.filter')` when the reporter's session_stop block-decision extension poisoned the transcript with eight persisted `session-stop-continuation` custom entries. The primary block-reason continuation flow was intact — the custom message correctly renders as a `role: "developer"` LLM message — but the follow-on idle recap fired 4 minutes later, and the side-channel provider stream handed back a `done` event whose `message.content` had been dropped. `runEphemeralTurn`'s sanitize step at `assistantMessage.content.filter(block => block.type !== "toolCall")` then tripped the TypeError, propagated as "Idle recap turn failed" in the debug log while silently muting the session. - Normalized the provider "done" event's `message.content` to `[]` when the shape is not an array, so a wrapper stream that drops content surfaces as an empty recap reply instead of an unrecoverable side-channel crash. - Guarded `#buildEphemeralSnapshot`'s in-flight-assistant preservation branch with `Array.isArray(streaming.content)` for the same reason. - Added a regression test that seeds the reporter's transcript shape (one real turn, eight persisted `session-stop-continuation` customs carrying a multi-line block reason with U+2717 glyphs) and drives a recap through a side stream that returns `content: undefined` on `done`. The test fails on the pre-fix tree with the exact reporter TypeError and passes after the guard lands. Fixes #4323
@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.