roboomp
70ada531d8
The SlashCommandSpec handle/handleTui signatures and a test `populate` callback relied on `() => void` being assignable to `() => T | undefined`. The repo's own gate uses `tsgo` (@typescript/native-preview) and TypeScript 6.x, both of which accept that coercion, so `bun run check:ts` passed cleanly. TypeScript 5.x does not, so `tsc --noEmit -p packages/coding-agent/tsconfig.json` under 5.9.3 produced 56 errors (`builtin-registry.ts` x46 TS2322, `agent-session-openai-responses-replay.test.ts` x10 TS2345). Expressed the slot as a union of two function types — one returning `SlashCommandResult`, one returning `void` — so the same handler bodies typecheck under both compilers. `T | void` in a single function-return position also trips Biome's `noConfusingVoidType`; the siblings-of-function-types shape avoids that. Verified: - TypeScript 5.9.3: 0 errors (was 56) - tsgo: 0 errors - bun run check:ts: 0 errors workspace-wide - packages/coding-agent test/slash-commands + agent-session-openai-responses-replay: 50/50 pass The issue's other two categories (telemetry-export.ts x2, tui virtual-terminal.ts x1) did not reproduce on this checkout — the catalog declares @opentelemetry/exporter-trace-otlp-proto, @opentelemetry/sdk-trace-node, and ghostty-web and they install cleanly. Fixes #1821
@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.