Diogo Soares Rodriguesandcan1357
6254b6e81b
Every native `pi_edit` failed after a session switched onto Cursor. The replace-mode `edit` instance the frame needs was built only for sessions CREATED on Cursor, and the tool roster is built once, at creation - a session that started elsewhere kept its configured-mode `edit` in the registry, which `executeTool` resolves before its fallback, so the frame's `old_text`/`new_text` pairs failed validation against a `hashline` schema. The instance is now built from the `edit` grant regardless of the initial provider, lazily so a session that never reaches Cursor never constructs one, and `pi_edit` asks for it through a dedicated `getEditReplaceTool` accessor rather than relying on Cursor sessions having deleted `edit` from the registry. A session that was never granted `edit` is still refused. That accessor also closes an escalation the previous wiring opened up. The session's device resolver is handed to the bridge as `getTool` and installed as the agent loop's `resolveFallbackTool`, which runs for ANY call outside the advertised set - so serving `edit` from it let a hallucinated call, or one naming a tool the session deselected after startup, execute a replace-mode edit the model was never offered. It is device-only again. Regressions cover both directions at the SDK level, driving a real unadvertised `edit` through the loop and asserting the surfaced `Tool edit not found`: an unchanged file alone would also pass if the fallback had resolved the tool and the edit then failed validation. (cherry picked from commit 11a28dcf7b995a9e94913269733b3199d6f4790d)
@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.