can1357andCan Bölük
fcd38b7143
Three independent lsp fixes that share the action dispatcher and import graph in lsp/index.ts: - symbol-required: project-aware references/rename/definition now reject an omitted symbol with a structured error pointing at symbol=<name> (and symbol#N for repeats). resolveSymbolColumn used to fall back to the first non-whitespace column and the server happily answered for whatever identifier sat there. findSymbolMatchIndexes also enforces word boundaries for bare identifiers. - timeout-distinguish: the outer catch around dispatched LSP actions rethrew new ToolAbortError() for both an internal timeoutSignal abort and a caller signal abort, so callers got an opaque "Operation aborted". Timeouts now map to a ToolError that names the action and the elapsed budget; caller cancels stay ToolAbortError. - edit-coalesce: rename and rename_file collected edits from every project-aware server and applied them sequentially, but each server computed positions against pre-edit text. Once server A wrote, server B's edits had stale offsets and produced malformed imports. Merge per-uri edits across servers, sort by descending position, and throw on overlap so the model retries instead of silently corrupting.
@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:
- CHANGELOG
- MCP configuration guide
- MCP runtime lifecycle
- MCP server/tool authoring
- DEVELOPMENT
- RenderMermaid guide
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.