@zanii/langchain
v0.1.2
Published
Receipt every tool call in a LangChain or LangGraph run with one callback handler - no changes to your tools. Signed, verifiable Zanii proofs across the whole chain.
Readme
@zanii/langchain
Receipt every tool call in a LangChain or LangGraph run with one callback handler — no changes to your tools. Every tool start/end/error across the whole chain (or graph — LangGraph reuses the same callback bus) becomes a signed, verifiable Zanii receipt.
npm install @zanii/langchain @zanii/sdk @langchain/coreUsage
import { ZaniiCallbackHandler, withZaniiConfig } from '@zanii/langchain';
import { ZaniiAgent } from '@zanii/sdk';
const agent = new ZaniiAgent({ /* … */ });
const zanii = new ZaniiCallbackHandler({ agent });
// attach once — every tool call in the run is now receipted:
await chain.invoke(input, { callbacks: [zanii] });
// LangGraph (same handler works):
await graph.invoke(input, withZaniiConfig(config, agent));Each receipt targets tools.<toolName> (override with { prefix }) and carries
the tool's input and output — or the error, on failure. Concurrent tool calls are
correlated independently by run_id, so a fan-out node produces one clean receipt
per tool.
The handler is duck-typed against LangChain's callback interface, so it adds no
LangChain dependency of its own — @langchain/core is an optional peer you already
have.
Changelog
- 0.1.2: A failed receipt upload no longer affects the tool or graph outcome; handlers log a sanitized warning instead of the error message.
- 0.1.1 —
ZaniiGraphHandler: graph node transitions chained by state hash, retrieved documents and model usage, optional run ids for cross-linking;recordCheckpoint/verifyResume,recordInterrupt, apolicyGatenode andrecordMemoryWrite. Still zero dependencies. - 0.1.0 — initial release:
ZaniiCallbackHandler,zaniiCallbacks,withZaniiConfig.
License
Apache-2.0.
