chan1103
4b136b0710
beautiful-mermaid@1.1.3 measures label width in UTF-16 code units, but terminals render East Asian characters (Hangul/CJK/kana) and emoji 2 columns wide, so fenced mermaid blocks in assistant messages and render_mermaid tool output had misaligned box borders for non-Latin labels (upstream: lukilabs/beautiful-mermaid#119, #122). Adds a patchedDependencies entry rebuilding the ASCII renderer to measure terminal display columns: grapheme-cluster segmentation (Intl.Segmenter), wcwidth-style policy (East Asian Wide + emoji presentation + ZWJ/VS16/flag sequences = 2 columns; text-presentation symbols like the renderer's own arrowheads stay narrow), and atomic wide-glyph cell pairs so label collisions cannot shift row widths. The patch modifies only existing files (bun cannot patch in new files, and the exports "bun" condition loads src/ directly, so both src and dist are patched). It mirrors the upstream PR and should be dropped once the fix ships in a beautiful-mermaid release; a new CJK alignment regression test keeps that transition honest. Verified: bun test packages/coding-agent/test/modes/components/ assistant-message-mermaid.test.ts (8 pass, incl. new display-column alignment regression test); bun test packages/utils (154 pass); Korean flowchart renders with uniform display-column row widths through the patched package.
@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.