The agent supports three mutually-exclusive memory backends, selected via the memory.backend setting (Settings → Memory tab, or ~/.jwc/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). Hindsight uses private backend lifecycle hooks to retain transcripts and recall context; compatibility-only internals remain for legacy backend calls, but GJC does not expose public coding-harness memory tools such as retain, recall, or 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.

Abyss Bite TUI theme

The interactive TUI defaults to the bundled abyss-bite theme for dark terminals and the bundled abyss-bite-light theme for light-appearance terminals. Explicit user theme settings still win; set theme.dark: abyss-bite and theme.light: abyss-bite-light in ~/.jwc/agent/config.yml to pin them.