roboomp
ed6300b35e
Keep-alive subagents are handed to AgentLifecycleManager.adopt, which stores their reviver closure in the process-global #adopted map. The closure is defined inside runSubagent's scope, which also captures the live AgentSession (extension-runner callbacks, buildSubagentSessionOptions), so its lexical environment pins the whole session graph. park() disposes and detaches the session but leaves the adoption record indefinitely, and #doDispose never dropped the in-memory transcript, session-manager entries, or the raw-SSE debug buffer (whose trimmed records retain slice() views of full wire frames), so every completed subagent's heavy state leaked for the process lifetime. dispose() is terminal and every revival path reopens from disk, so #doDispose now sheds retained conversation memory via agent.reset(), RawSseDebugBuffer.clear(), and SessionManager.releaseRetainedEntries(). The adoption record can still reference the session, but only as a husk. Fixes #8003
@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.