Files

T

FND 770147c89e feat(lsp): support ty.toml-only projects and fix changelog placement

Address review feedback on #8186:
- add ty.toml to ty rootMarkers so ty.toml-only projects pass the
  loadConfig marker gate (Codex P2, roboomp should-fix)
- add ty.toml to PYTHON_ROOT_MARKERS so project-local .venv/bin/ty
  resolution runs for ty.toml-only projects (roboomp should-fix)
- add a ty.toml-only regression test covering both the detection
  gate and the local venv bin resolution path
- move the changelog entry from the released [16.3.11] section into
  [Unreleased] (roboomp should-fix)

2026-08-10 23:23:43 +02:00

bench

feat: introduced omptype validation package and migrated workspace dependencies

2026-08-03 21:56:48 +02:00

examples

Merge PR #7735 : fix(coding-agent): return ToolInfo[] from getAllTools extension API (@roboomp)

2026-08-05 22:15:46 +02:00

scripts

fix(natives): make Windows-host builds and addon loading work end to end

2026-08-07 16:54:02 +08:00

src

feat(lsp): support ty.toml-only projects and fix changelog placement

2026-08-10 23:23:43 +02:00

test

feat(lsp): support ty.toml-only projects and fix changelog placement

2026-08-10 23:23:43 +02:00

CHANGELOG.md

feat(lsp): support ty.toml-only projects and fix changelog placement

2026-08-10 23:23:43 +02:00

DEVELOPMENT.md

feat(coding-agent): added opt-in task prewalk and tightened --tools and xdev behavior

2026-07-15 18:39:36 +02:00

package.json

chore: bump version to 17.2.12

2026-08-08 20:57:55 +02:00

README.md

fix(memory): synchronized live backend lifecycle

2026-07-23 19:52:09 +00:00

tsconfig.examples.json

…

tsconfig.json

…

tsconfig.publish.json

…

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 immediately replaces the live backend, memory tools, listeners, and system-prompt context. Existing users with memories.enabled = true|false are migrated to memory.backend = "local"|"off" exactly once on first launch; afterward, memory.backend is the sole runtime selector.