roboomp
336b993126
On kitty (Linux/Wayland) and any terminal supporting OSC 5522 enhanced paste, the /login API-key prompt for OpenCode Zen — and any other modal Input prompt (Perplexity OTP, GitHub Enterprise URL, manual OAuth redirect URL, …) — silently dropped pasted content. The user could not paste their API key; on Enter or Esc the key surfaced in the main prompt. Cause: InputController.#setupEnhancedPaste enables kitty's enhanced clipboard protocol on TUI start and consumes the resulting OSC 5522 packets in an addInputListener that runs *before* focus dispatch in tui.#handleInput. The controller's pasteText callback then routed unconditionally to this.ctx.editor.pasteText(text) — the main CustomEditor — even when selector-controller had cleared editorContainer and focused a temporary Input. The text accumulated in the detached editor and only resurfaced when the modal was dismissed. Fix: - TUI.getFocused() exposes the currently focused component. - Input.pasteText(text) mirrors Editor.pasteText so any Input can absorb a payload from a non-bracketed transport. - InputController's enhanced-paste callback consults getFocused() and routes text to the focused component when it exposes pasteText, falling back to the editor only when no modal target is in focus. - Image pastes refuse with a status message when a modal Input is focused, instead of stuffing a binary blob into the hidden editor. Regression tests in packages/tui/test/input.test.ts and packages/coding-agent/test/issue-2127-repro.test.ts pin both the new TUI/Input contract and the InputController routing source. Fixes #2127
@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.