Files

T

oldschoola f8ec04871f fix: propagate thinking level changes to existing components and use viewSession

Address 4 P2 review comments on PR #3314:

1. effectiveHideThinkingBlock now uses viewSession.thinkingLevel
   instead of session.thinkingLevel — in focused-agent mode, the
   viewed transcript may have a different thinking level than the
   main session.

2. thinking_level_changed handler now iterates existing
   AssistantMessageComponent children and calls setHideThinkingBlock
   with the new effective value, then resetDisplay() to repaint.
   Previously only new/streaming messages got the updated visibility.

3. Changed AssistantMessageComponent import from type-only to value
   import for instanceof check.

4. Agent Hub callback already uses effectiveHideThinkingBlock which
   now reflects viewSession — no separate fix needed.

2026-06-23 16:02:10 -07:00

bench

perf(coding-agent): defer boot work and cut streaming/read CPU

2026-06-09 18:58:22 +09:00

examples

feat: added standalone snapcompact package and model-specific frame shaping

2026-06-10 21:50:03 +02:00

scripts

feat: implemented reparenting for backgrounded wrappers

2026-06-23 08:06:54 +02:00

src

fix: propagate thinking level changes to existing components and use viewSession

2026-06-23 16:02:10 -07:00

test

fix(tui): check thinking level directly instead of effectiveHideThinkingBlock

2026-06-23 16:02:10 -07:00

CHANGELOG.md

fix(tui): auto-hide thinking blocks when thinking level is off

2026-06-23 16:02:10 -07:00

DEVELOPMENT.md

chore: update docs

2026-06-17 04:37:39 +02:00

package.json

chore: bump version to 16.1.16

2026-06-23 08:22:21 +02:00

README.md

feat: removed render_mermaid tool and added width-aware Mermaid clipping

2026-06-16 21:32:39 +02:00

tsconfig.examples.json

…

tsconfig.json

…

tsconfig.publish.json

chore(config): organized publish type mapping from src to dist/types

2026-05-15 23:46:23 +02:00

README.md

@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

Run a Hindsight server (Cloud or docker run -p 8888:8888 ghcr.io/vectorize-io/hindsight:latest).
Set memory.backend = "hindsight" and hindsight.apiUrl = "http://localhost:8888" (or your Cloud URL).
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.