roboomp
efaad3ffb5
/quit and /exit hung for many seconds because AgentSession.dispose() awaited MnemopiSessionState.dispose() unconditionally, and that path runs consolidate() (state.ts:421) which fires a fresh LLM fact extraction for the just-retained transcript and then awaits flushExtractions() per owned bank. One LLM round-trip per shutdown, no upper bound, no visible status. - Add a timeoutMs option to MnemopiSessionState.dispose. When the cap fires the in-flight consolidate is detached to the background and the SQLite handles close once it settles, so writes never race a closed handle. - AgentSession.dispose passes SHUTDOWN_CONSOLIDATE_BUDGET_MS = 1_500 on the user-visible shutdown path. Per-turn maybeRetainOnAgentEnd has already retained earlier turns, so the worst case is losing episodic promotion for the last few turns. State-replacement disposes (mnemopiBackend.start) stay unbounded. - InteractiveMode.shutdown surfaces a 'Closing session…' status before dispose runs so the brief pause is explained rather than mysterious. Two regression tests in memory-tools.test.ts cover (1) dispose returns within the budget when flushExtractions stalls and the deferred close still runs once consolidate settles, and (2) unbounded dispose still runs the full #2320 consolidate-then-close pipeline. Fixes #3641
@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.