roboomp
e8e7cefe20
On a long subagent-heavy run the TUI thought stream froze for 1.5–4 s at a time, with the loop watchdog blaming `subagent:*` phases and the log carrying ~1,255 `Skipping mid-run compaction because turn persistence is out of order` debug lines per session (issue #3629). `#persistTurnMessagesForMidRunCompaction` and the persistence-check helpers it calls were doing two O(n²) things per `onTurnEnd`: 1. Every call rebuilt the branch path via `SessionManager.getBranch()` (O(branchSize) `unshift` per call), once per turn message twice (once in `#sessionMessageAlreadyPersisted`, once in `#hasPersistedLaterTurnMessage`). 2. Every pairwise message comparison serialized full message content through `#messageValueSignature` (=`JSON.stringify`), even though the content was almost always orthogonal to the identity decision. Replace the structural comparator with a stable persistence key (timestamp + role-specific discriminators) extracted to a sibling module `session/turn-persistence.ts` and drive the planner off one snapshot of the branch built per `onTurnEnd`. Content equality is retained as the slow-path tiebreaker for the rare case where two messages collide on the cheap key (e.g. two assistant turns at the same millisecond with `undefined` responseId — the shape the test harness emits). The new helpers (`sessionMessagePersistenceKey`, `planTurnPersistence`, `sameMessageContent`) are pure functions covered by direct unit tests in `test/turn-persistence.test.ts`; the existing mid-run / eager compaction integration tests prove the end-to-end behavior is preserved. Fixes #3629
@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.