Márton Danóczy
0ca0739eeb
Zed (and any other ACP client) never learned about a model switch that happened from inside the agent loop — prewalk hand-offs, retry-fallback, model cycling — because #pushConfigOptionUpdate was only ever wired to the client-initiated setSessionConfigOption/setSessionMode RPCs and to the thinking_level_changed lifetime event. The model itself did switch correctly (subsequent requests used the new model), but the client's model picker/status bar kept showing the session's starting model. #handleLifetimeEvent now also reacts to the model_changed event added in the previous commit and re-pushes config_option_update. Extend the existing thinking-only subscription dedupe in setSessionConfigOption to cover the model config id too, so a client-initiated model change still produces exactly one notification once the lifetime subscription is installed. Regression tests mirror the existing thinking-level coverage: - 'pushes config_option_update when the model changes internally' - 'emits a single config_option_update per setSessionConfigOption(model) call' Verified: bun test test/acp-agent.test.ts (57/57), plus agent-session-prewalk.test.ts, agent-session-retry-fallback.test.ts, retry-fallback.test.ts, model-resolver.test.ts, and the other acp-*.test.ts files all still pass; tsgo --noEmit and biome check clean. (cherry picked from commit f5c5081088e8cbac2650a9de89049731de1b2777)
@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.