Agent skill · operations · vectorize-io
hindsight-coding-agent
How this machine's Hindsight coding-agent memory works — the plugin behind the 🧠 banner. Use when the user says "store/remember this in hindsight", asks what the memory/knowledge pages are, wants to configure per-repo memory (disable, rename banks, git depth), or something memory-related looks broken.
Why this skill is useful
Provides specific commands and configurations for managing long-term project memory that the AI wouldn't generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 19,183 stars on the source repository.
What this skill does
<!-- GENERATED from README.md (its skill:begin regions) + skill-src/preamble.md. Edit those, then run: npm run skill:build --> Hindsight Coding-Agent Memory This machine runs the hindsight-coding-agents plugin: long-term project memory for coding sessions, backed by a Hindsight server. You (the agent) are already wired into it — this skill explains what happens automatically, which tools you have, and how to configure or debug it. What happens automatically (no action needed) Per-repo memory bank: each repository resolves to a bank (shown in the session banner: ↳ memory bank “coding-agent::<repo>”). Worktrees share the main repo's bank. Ingestion builds itself: on first open, the bank is seeded from recent commit messages and a read-only codebase survey; every session start, a background engine tops it up (new commits, new conversations) and keeps 5 knowledge pages current. There is NO ingest command to run. Session synthesis: by default, the first prompt of a session triggers one deep memory synthesis (reflect) injected into context. With autoReflect=false, the agent searches the knowledge pages first and reflects only when they are too shallow. Write-back: the session transcript is retained into the bank automatically at session end (per-turn on opencode). The user never needs to "save" a conversation. Storing things deliberately When the user says "store this in hindsight" / "remember this": The current conversation is captured automatically at session end — say so; no tool needed. An external document, notes, or durable findings → hindsightingestdocument(title, content). A new feature/initiative being started → hindsightcaptureinitiative(title, summary), right after the plan is agreed and before code is written. A plan that materially changed (goal, scope, or rationale — including mid-implementation) → call hindsightcaptureinitiative again with relatestopageid set to that initiative's page id, summarising the current intent. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vectorize-io/skill