Skip to content

Integrations

One call. Every framework. Same memory.

Pick your stack — the exact Lore calls, the install, and the three steps to wire it in.

Install npm
npm i @loregpt/sdk

One reality across nodes

Every node reads the same consolidated state — no more passing the whole message history through the graph.

Read-your-writes

Pass the writer node the seq from the researcher; its pack is guaranteed to reflect it.

A smaller token bill

Budget-fit, deterministic packs replace ballooning graph state — prompt caching compounds.

langgraph.ts
Ready
import { StateGraph } from "@langchain/langgraph";
import { LoreClient } from "@loregpt/sdk";

const lore = new LoreClient({ apiKey });

// a node writes what it learned — nothing blocks
async function researcher(state) {
  const { seq } = await lore.write({
    runId: state.runId, agentId: "researcher",
    content: "Auth flow moved to v2 — PR #42 merged",
  });
  return { ...state, seq };
}

// a later node reads a pack that is guaranteed to contain it
async function writer(state) {
  const pack = await lore.pack({
    query: "current state of auth work",
    scopes: { team: "platform" },
    minSeq: state.seq,          // read-your-writes
    tokenBudget: 2000,
  });
  // pack.coveredSeq >= state.seq  → the write is in there, guaranteed
  return { ...state, context: pack.text };
}
main UTF-8 · LF · TypeScript

On the roadmap

Vercel AI SDKsoon LlamaIndexsoon Mastrasoon

Working with something else? Lore speaks MCP — any MCP-capable client gets shared memory as tools, no SDK required. Pick the MCP tab above to see it.

Everything falls into one shared reality.

Lore

Join the waitlist

Early access + design-partner slots. No spam — just the first ping when it opens.