roboomp
784fd56505
The whole-line editor decorate ran on `displayText` after the editor appended the zero-width CURSOR_MARKER and cursor glyph; both start with ESC, so the magic-keyword regex's right-boundary `(?!\S)` rejected `ultrathink` glued to the marker and dropped the gradient until a trailing character was typed. - `Editor.#decorate` (pi-tui) now splits around CURSOR_MARKER and decorates each user-text segment independently, so word-boundary lookarounds resolve correctly on both sides; the matching comment block is corrected. - `KeywordHighlighter` / `highlightMagicKeywords` gain an optional `phase` in [0, 1) that cyclically rotates the gradient stops. `0` (default) yields the static palette, so sent-bubble rendering is unaffected. - `CustomEditor.decorateText` derives `phase` from `Date.now()` and chains `setTimeout(SHIMMER_FRAME_MS)` ticks while focused, the buffer holds a magic keyword, and `magicKeywords.enabled` is on — the render itself schedules the next frame, so losing focus, deleting the keyword, or flipping the setting stops the animation on its own. `interactive-mode` wires the repaint hook to `requestComponentRender(editor)` on construction and after `setEditorComponent`. - Adds `hasMagicKeyword(text)` (cheap prose-aware probe) and tests for the seam fix, the phase cycle, the gating, and timer cleanup. Fixes #2475
@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.