roboomp
dd8b50649a
`finalizeSubprocessOutput` always spliced collected `report_finding` entries onto a top-level `findings` array regardless of the active output schema. A caller-supplied schema with `additionalProperties: false` and no `findings` property would accept the raw payload in-tool (via the `yield` validator, which only sees the pre-injection data) but then fail post-mortem validation — emitting `schema_violation: findings: must not be present` and propagating as a fatal `RuntimeError` through `agent-bridge.ts` and the eval Python/JS preludes, collapsing the entire workflow cell along with any prior successful subagent work. `normalizeCompleteData` now takes the resolved validator and only performs the injection when the augmented candidate validates. When the schema rejects it, the raw payload is returned instead — which the in- tool yield validator already accepted, so the lockstep guarantee documented at the top of `output-schema-validator.ts` is honored. Findings remain visible via the agent progress stream and JSONL artifact, so no information is dropped when injection is suppressed. Both finalize call paths (yield-success and no-yield fallback) now share the single validator build instead of constructing it twice, and the yield-path schema_violation branch is now reached only via the explicit malformed-schema check, never via spurious findings rejection. Fixes #2070
@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.