enieuwy
a93a53185b
Review of the previous commit found the same defect in four more places, each a variant of one mistake: the unproven-model gate was expressed as "a retry fallback is armed and has not served", so it only protected the one swap path that arms a chain. - The cooldown-expiry restore to the primary deletes the fallback record before swapping, so the gate vanished with it and an unproven, just- restored primary was credited immediately. - A session's first-ever fallback arm constructs the record only after the swap, so there was nothing to mark and the guard was a no-op. - The Fireworks Fast degrade swaps models without arming a chain at all, so a live row showed the degraded base model as the configured primary. - The fresh-versus-resumed heuristic read the message list, which compaction collapses, so a resumed-and-compacted session seeded its startup candidate as already proven. Attribution now names the last model that settled a turn here, full stop. A switch of any kind — into a candidate, back to a restored primary, or a capability degrade — moves it only once the new model answers. Before anything has served there is no earlier work to miscredit, so the configured model is both the only answer and a safe one. Fallback routing is tracked as its own flag rather than inferred from the chain record, because the degrade path routes without a chain, and it is set before each swap so the synchronous `model_changed` fan-out cannot observe a model mid-relabel. The resumed-session heuristic is gone: it was only needed to decide whether an unserved candidate could be trusted, and nothing is trusted before it serves.
@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 immediately replaces the live backend, memory tools, listeners, and system-prompt context. Existing users with memories.enabled = true|false are migrated to memory.backend = "local"|"off" exactly once on first launch; afterward, memory.backend is the sole runtime selector.