Nicolò Boschi
6f2799569f
* docs: link every integration changelog from its doc page The release script has written a changelog page per integration since 0.4.20 (src/pages/changelog/integrations/<slug>.md), but nothing reliably linked them: 16 of 61 doc pages carried a "View Changelog" link, and the only index was a hand-written table at the bottom of /changelog listing 6 of the 48 pages, stale since the release that introduced them. coding-agents was one of the 31 pages with a changelog nobody could reach except by guessing the URL. Adds the link to the 30 pages missing one, plus a third invariant in check-integrations.mjs so the next one can't ship unlinked: every changelog page whose integration has a gallery entry must be linked from its doc page. coding-agents.md is generated, so its link goes in the README as an absolute hindsight.vectorize.io URL — the sync script rewrites our own absolute URLs to site-relative, so it resolves on npm, GitHub and the docs site. It sits outside the skill:begin regions, so SKILL.md is unchanged. Claude-Session: https://claude.ai/code/session_01DNWFQn8AUN6SApcswHG3aN * docs(integrations): compact grouped gallery with Docs/Changelog buttons The Integrations Hub listed 60 three-line cards with a repeated "Hindsight Team" byline and an OFFICIAL badge on 52 of them, running 6092px tall — scanning it meant scrolling past what you came for. Cards are now a compact row (icon, name, two-line description) grouped by category, with the featured three using the same row tinted rather than a second card design: 4352px, and the shape of the catalogue is visible at a glance. Each card carries Docs and Changelog buttons. Which integrations have a changelog comes from a new build-time plugin that indexes src/pages/changelog/integrations/*.md and joins integrations.json on the link slug (vercel-ai-sdk -> /sdks/integrations/ai-sdk -> ai-sdk.md), so an integration grows the button on its first release with nothing to update by hand. The card is a <div> now — nested anchors are invalid — so the name and the pills are the links, not the whole card. /changelog's first line points here instead of carrying its own listing. Also drops the 14 CSS classes the old card owned, and shares CATEGORY_LABELS / groupByCategory from src/lib/integrations.ts so the taxonomy has one definition. Claude-Session: https://claude.ai/code/session_01DNWFQn8AUN6SApcswHG3aN
3.7 KiB
sidebar_position, title, description
| sidebar_position | title | description |
|---|---|---|
| 33 | Dify Persistent Memory with Hindsight | Integration | Add persistent long-term memory to any Dify workflow with Hindsight. A plugin provides Retain, Recall, and Reflect tools — drop them into any chatflow or workflow alongside your other LLM, search, and tool nodes. |
Dify
Persistent memory for Dify workflows via Hindsight. The Hindsight Dify plugin adds three tools — Retain, Recall, Reflect — that work alongside any other Dify node in workflows, chatflows, and agent apps.
Why this matters
Dify is one of the most popular open-source LLM app platforms — visual workflow builder, prompt management, and a growing tool/plugin ecosystem. Until now, Dify workflows have been stateless across runs. With Hindsight tools you can:
- Retain every closed support ticket, sales-call transcript, or form submission into a memory bank
- Recall relevant context before an LLM step so the model sees prior history
- Reflect to ask synthesizing questions ("What do we know about this customer?") inside a workflow
Installation
In your Dify dashboard go to Plugins → Install Plugin, then choose one of:
- Marketplace — search for
Hindsight(once published) - GitHub — install from
vectorize-io/hindsight(pathhindsight-integrations/dify) - Local — upload the
.difypkgarchive
After install, the Hindsight plugin appears under Tools in the workflow editor.
Setup
:::tip Recommended: Hindsight Cloud Sign up free and grab an API key — no self-hosting required. :::
- Sign up at Hindsight Cloud (free tier) or self-host
- Get an API key from the Hindsight dashboard
- In Dify, open the Hindsight plugin and add credentials:
- API URL — defaults to
https://api.hindsight.vectorize.io(Cloud); change for self-hosted - API Key — your
hsk_...key (optional for self-hosted unauthenticated instances)
- API URL — defaults to
Tools
Retain
Store content in a bank. Hindsight extracts facts asynchronously after the call returns.
| Field | Description |
|---|---|
| Bank ID | Memory bank to store in (auto-created on first use) |
| Content | Free-text content to retain |
| Tags | Optional comma-separated tags |
Recall
Search a bank for memories relevant to a query. Returns a results array.
| Field | Description |
|---|---|
| Bank ID | Memory bank to search |
| Query | Natural-language query |
| Budget | low / mid / high |
| Max Tokens | Cap on returned tokens |
| Tags | Optional tag filter (comma-separated) |
Reflect
Get an LLM-synthesized answer over the bank. Returns text.
| Field | Description |
|---|---|
| Bank ID | Memory bank |
| Query | Question to answer |
| Budget | low / mid / high |
Example workflows
Customer-support assistant — every closed Zendesk ticket retains the resolution. Every new ticket starts with a Recall against the bank to surface similar past issues, then passes that context to OpenAI/Anthropic to draft the first reply.
Sales-call coach — Gong webhook → Hindsight Retain (call summary). Before each next prep call, Recall on the prospect's name to pull every prior touchpoint, then format into the daily prep doc.
Knowledge-base agent — every uploaded document is chunked and retained. The Dify chatflow uses Recall instead of vector-DB-only retrieval, getting fact-extracted, deduplicated, time-aware results.
Source
- GitHub:
hindsight-integrations/dify