Wolfgang Schoenberger
6a55205b68
prepareCompaction keeps the most-recent turn verbatim (findCutPoint never cuts at tool results), so when that single turn already exceeds the compaction threshold the rewritten context stays above threshold. The context-full / snapcompact auto-compaction success tail scheduled the agent-authored auto-continue (and the overflow/incomplete retry) unconditionally, so the next agent_end re-entered #checkCompaction over the same oversized tail and re-fired forever. This is the residual loop left after #3247 capped snapcompact's own frame projection: once #computeSnapcompactMaxFrames drops the frame cap below one frame, snapcompact is skipped and the context-full summarizer path still creates no headroom, so the loop persists on that path. - #runAutoCompaction now gates the continuation and the overflow/ incomplete retry on a post-maintenance headroom check (#compactionCreatedHeadroom), reusing the shake recovery-band hysteresis from #2275 (consolidated as the shared COMPACTION_RECOVERY_BAND). When a pass frees too little it pauses automatic maintenance and emits a single warning instead of looping. - The post-turn threshold check ignores an assistant's stale pre-compaction usage so the scheduled auto-continue can't re-trip on the kept assistant's old high token count. Adds a regression test covering the no-headroom (pause + warn, no continuation) and headroom (auto-continue, no warn) paths; both assertions are mutation-verified against the guard. (cherry picked from commit 6fcbbe2b3075827ee621acaee8efa2c586eedd3e)
@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.