Diogo Soares Rodrigues
ab7b457af0
Two truncation records exist locally. `read`/`grep` set `details.truncation` (`TruncationResult`), which carries an explicit `truncated` boolean. `bash` sets `details.meta.truncation` (`TruncationMeta`), which has no such flag — its presence is the signal. `piTruncation` read only the first and required the boolean, so every real Bash truncation was dropped: Cursor got clipped output with no indication it was clipped. Both shapes now translate; `TruncationResult` stays authoritative when present so an explicit `false` still suppresses. Also drops the legacy pi shim's copies of the regex-literal escaper and the path/glob join. Both were verbatim duplicates of the modern bridge's helpers, which is the drift the shared translation exists to prevent. Verified producer-to-consumer, not against a hand-built bag: the test runs a real `BashTool`, asserts its output has no top-level `truncation` and no `truncated` flag under `meta`, then feeds those exact details to `piTruncation`. Typed against the producer's own `TruncationMeta`, so a renamed field fails compilation rather than silently reverting the bug. Mutation-checked: reverting to the top-level lookup, restoring the flag requirement, or dropping the null guard each fails a test. (cherry picked from commit 6699672d52061b832677dd45315f4aba8d330db1)
@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.