Skip to content

blog: four things to build with Vercel Eve and Hindsight - #5699

Merged
benfrank241 merged 4 commits into
mainfrom
blog-eve-memory-provider
Oct 16, 2026
Merged

benfrank241 merged 4 commits into
mainfrom
blog-eve-memory-provider

Conversation

@benfrank241

@benfrank241 benfrank241 commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

A use-case post rather than a release note.

Eve's own tutorial teaches the analytics agent the team's metric glossary using defineState, which their doc describes as surviving "across step and turn boundaries within a session." Right instinct, container one size too small — the glossary is a fact about the team, not the conversation. The post opens there and covers four things that change once the memory outlives the session:

  1. A glossary that outlives the session — scope a slot to the team, so house definitions are learned once by whoever says them first.
  2. One customer, every channel — memory follows the authenticated principal across Slack, Telegram, Twilio and the rest. States the caveat plainly: byPrincipal keys on principal type, authenticator, issuer and ID, so two channels share memory only when one identity provider says they are the same person.
  3. Tenant isolation that is not a filter — scope resolved from verified session auth, never the model; one bank per locked scope, so a semantic search never ranks globally and filters after.
  4. The memory your stack already wrote — point a slot at a bank the team's coding agents already fill. Notes that a string bankId pins every scope to one bank, which is right for an internal agent and wrong for a customer-facing one.

Scope, visibility and null-resolver behaviour are taken from docs/patterns/multi-tenant-memory.md and docs/memory/overview.mdx on vercel/eve@main; byPrincipal's key composition from packages/eve/src/shared/principal-scope.ts. Our own behaviour is verified against origin/main, and the quick-start was built end to end on eve 0.80.1 + hindsight-eve 0.3.1.

Cover pairs eve's own mark from vercel/eve .github/assets/eve.svg with the Hindsight glyph.

Two files: post + cover.

🤖 Generated with Claude Code

hindsight-eve v0.3 is built on eve's memory provider contract, which closes
the two gaps the July v0.2 post documented: recall now runs on the live user
message instead of a fixed broad query, and every locked scope gets its own
bank instead of one bank for everyone. One authored file replaces two.

Cover pairs eve's own mark (.github/assets/eve.svg) with the Hindsight glyph.
Same release, different angle. Instead of a changelog of what v0.3 changed,
teach the contract itself — recall / capture / tools, the locked scope key,
the operation id — with the Hindsight provider as the worked example.

Covers the three rules that are easy to get wrong: partition inside the
query rather than filtering after, treat operationId as an idempotency key,
and never let recall throw, since a throwing recall fails the turn before
the model call.
@benfrank241 benfrank241 changed the title blog: Hindsight is now a memory provider for Vercel Eve blog: write a memory provider for Vercel Eve Oct 16, 2026
Open on the gap in eve's own tutorial — it stores the team's metric glossary
in defineState, which lives for one session — then four things that change
when the memory outlives it: a team-scoped glossary, one customer across
every channel, tenant isolation that is a scope rather than a filter, and
pointing a slot at a bank the team's coding agents already wrote.
@benfrank241 benfrank241 changed the title blog: write a memory provider for Vercel Eve blog: four things to build with Vercel Eve and Hindsight Oct 16, 2026
Review feedback: the preamble assumed you had read eve's tutorial, so the
first four sentences critiqued a doc the reader cannot picture, introduced
defineState unexplained, and never said what the post was about.

Opens on the concrete situation instead. The defineState observation moves
into use case 1, where it has context and reads as evidence rather than as
the premise.
@benfrank241
benfrank241 merged commit 5331da2 into main Oct 16, 2026
100 checks passed
@benfrank241
benfrank241 deleted the blog-eve-memory-provider branch October 16, 2026 19:58
@nicoloboschi nicoloboschi mentioned this pull request Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant