Files
oh-my-pi/packages/coding-agent
Mathews-Tom c1ea6ca7dc test: fix azure msg-id preservation and retry-diagnostics log shape
Second upstream merge (upstream/main advanced 24 more commits) pulled
in two independent behavior changes that broke tests I'd already
touched or that existed:

- packages/ai: commits cda6df81d/d7f070d44 added
  preserveAssistantMessageIds for Azure specifically (azure sets it
  true), so the earlier fix stripping msg ids in
  azure-openai-responses-stream.test.ts is now wrong for Azure — it
  should preserve them, unlike the plain OpenAI path. Restored the
  id/phase assertions and renamed both tests to describe the
  preserve-not-omit contract.

- packages/coding-agent: commit 0e2feab74 (refactor: reduced session
  log footprint) deleted the
  '#agentContinueState'/'agent.continue failed state after
  scheduling' debug diagnostics and changed
  'agent active context assistant removal' to fire only on a miss,
  renamed to 'agent active context assistant removal missed' with a
  smaller payload (no more removed/beforeLength/afterLength/etc).
  agent-session-retry-diagnostics.test.ts still asserted the old
  shape and waited on a debug call that no longer exists, so it hung
  for the full 5s timeout. Updated to match the new log name/payload
  and dropped the removed diagnostic assertion; the retry-recovery
  behavior itself is unchanged and still exercised end to end.
2026-07-02 06:46:17 +05:30
..
2026-07-01 20:03:42 +02:00

@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; writes memory_summary.md and 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 exposes retain, recall, and reflect.

Hindsight quickstart

  1. Run a Hindsight server (Cloud or docker run -p 8888:8888 ghcr.io/vectorize-io/hindsight:latest).
  2. Set memory.backend = "hindsight" and hindsight.apiUrl = "http://localhost:8888" (or your Cloud URL).
  3. Optional environment overrides (env wins over settings):
    • HINDSIGHT_API_URL, HINDSIGHT_API_TOKEN — connection
    • HINDSIGHT_BANK_ID, HINDSIGHT_DYNAMIC_BANK_ID, HINDSIGHT_AGENT_NAME — bank addressing
    • HINDSIGHT_AUTO_RECALL, HINDSIGHT_AUTO_RETAIN, HINDSIGHT_RETAIN_MODE — lifecycle
    • HINDSIGHT_RECALL_BUDGET, HINDSIGHT_RECALL_MAX_TOKENS — recall sizing
    • HINDSIGHT_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.