Mathews-Tom
f9e481baad
AgentSession defers and coalesces the wire-level agent_end while a prompt is in flight (#emitSessionEvent), so a multi-attempt retry saga often surfaces only ONE agent_end to EventController — which can be the final settle, not an intermediate attempt. Consuming #retryPending against whichever agent_end arrived first (previous commit) could therefore discard the real final failure notification. Switch to gating purely on the retry lifecycle: #retryPending is set by auto_retry_start and cleared only by auto_retry_end (both outcomes), never consumed by sendErrorNotification itself. Those lifecycle events are never deferred, so they reliably bracket the window a retry is actually outstanding regardless of how agent_end coalescing lands. Close the residual gap this creates: #handleRetryableError's classifier-refusal and Fireworks-fallback-ineligible branches could short-circuit a saga that already announced auto_retry_start without ever emitting auto_retry_end, latching #retryPending open forever. Both branches now emit a final auto_retry_end(false) when a prior attempt already started the saga. #handleAgentStart also clears #retryPending defensively so a saga that still somehow never resolves cannot suppress a later, unrelated turn's notification.
@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.