metaphorics
18ee97751a
Add a default-off "auto-learn" loop. When `autolearn.enabled` is set, after the agent stops a session controller nudges it to capture reusable lessons: durable facts go to long-term memory and repeatable procedures become "managed skills" — SKILL.md files written to an isolated ~/.omp/agent/managed-skills directory that is discovered and surfaced like authored skills but never overwrites them. Two tools back this: - `manage_skill` — create/update/delete managed skills. - `learn` — record a lesson, optionally minting/enhancing a managed skill in the same call (requires a hindsight/mnemopi memory backend). The nudge is passive by default (a hidden reminder rides the next turn); `autolearn.autoContinue` instead auto-runs one capture turn at stop, and `autolearn.minToolCalls` (default 5) gates trivial turns. Plan/goal-mode turns and subagents are never nudged, and the controller re-checks the live setting at fire time so a mid-session opt-out takes effect. Isolation & precedence: managed skills are a separate lowest-priority discovery provider, so an authored skill of the same name wins across every provider and custom directory regardless of third-party toggles; a disabled higher-priority authored skill can never hide a managed one, and managed never masks an enabled authored skill. Managed names and descriptions are sanitized on both write and read (control/format chars, angle brackets, and Markdown fences) before they render into the system prompt, and the SKILL.md byte cap is enforced on the final serialized file. Default off → zero footprint when disabled.
@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.