roboomp
482091dc73
The replan-driven title refresh (title.refreshOnReplan, fired after a `todo init`) called `generateSessionTitle()` without the user's `TITLE_SYSTEM.md` override, silently falling back to the bundled `prompts/system/title-system.md` and overwriting auto titles with the default policy. The override was only ever discovered by main.ts and passed into the first-input title path on InteractiveMode, never into `AgentSession.#refreshTitleAfterReplan`. Most visible in Plan Mode, which initializes todos early. `AgentSession` now owns the resolved title prompt: - New `CreateAgentSessionOptions.titleSystemPrompt` threaded by `createAgentSession()` into the constructor. - New `AgentSessionConfig.titleSystemPrompt` stored on `#titleSystemPrompt` with a `get titleSystemPrompt` / `setTitleSystemPrompt(...)` pair. - `#refreshTitleAfterReplan` passes `#titleSystemPrompt` as `customSystemPrompt` to `generateSessionTitle()`. - `input-controller.ts` reads from `session.titleSystemPrompt`, and the duplicate `InteractiveMode.titleSystemPrompt` field / constructor arg / `InteractiveModeContext` field / `runInteractiveMode` parameter are removed. `InteractiveMode.refreshTitleSystemPrompt` now calls `session.setTitleSystemPrompt(...)` so a `/move`-style cwd change keeps the override in sync. Regression test asserts the prompt handed to `completeSimple()` from `#refreshTitleAfterReplan` is the configured override, not the bundled `title-system.md`. Fixes #3734
@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; 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.