jeopi

Core implementation package for the jeopi coding agent in the jeopi monorepo.

For installation, setup, provider configuration, model roles, slash commands, and full CLI reference, see:

• Monorepo README (local)
• Monorepo README (GitHub)

Package-specific references:

• CHANGELOG
• MCP configuration guide
• MCP runtime lifecycle
• MCP server/tool authoring
• DEVELOPMENT

Memory backends

The agent supports three mutually-exclusive memory backends, selected via the memory.backend setting (Settings → Memory tab, or ~/.jeopi/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

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