Erik Svilich
d6f887d152
Three issues from an adversarial review, all rooted in the startup argv parse running before extensions load: 1. Flag-looking string values (`--name --print`): the extension-aware reparse consumed the following token as the value, disagreeing with the startup parse that treated `--print` as the built-in flag — so the reparse could silently flip command shape. Extension string flags now consume a following token only in `--flag=value` form or when it is not flag-looking; pass a flag-looking value as `--flag=value`. Keeps both parses consistent. 2. `@file` string values (`--target @notes.md`): file args were processed from the startup parse, which misreads the value as a file and reads it into the prompt. processFileArguments now runs on the extension-aware parse (initialArgs.fileArgs); pipedInput stays early for mode detection. 3. Built-in collisions: an extension flag named like a built-in (e.g. `model`) was consumed by the built-in branch and never delivered to the runner. registerFlag now rejects names in BUILTIN_FLAG_NAMES with a clear error (isolated per-extension by loadExtension's try/catch). Adds tests for all three plus the documented startup-parse misclassification.
@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.