WeSearch

Same agent tasks, 76% fewer LLM calls – we moved semantic cache inside the graph

·9 min read · 0 reactions · 0 comments · 2 views
#same#agent#tasks#fewer#calls
Same agent tasks, 76% fewer LLM calls – we moved semantic cache inside the graph
TL;DR · WeSearch summary

ChorusGraph = native engine + Prism stack · LangGraph = optional baseline for A/B comparison only (docs/TERMINOLOGY.md) What is ChorusGraph? It ships a native BSP graph engine (chorusgraph.core.Graph) with the Prism product stack attached by default: semantic cache, L2 retrieval, L3 memory, Route Ledger, checkpoints, and observability. You define nodes, edges, and conditional routing on the native engine.

Key facts
Original article
GitHub
Read full at GitHub →
Opening excerpt (first ~120 words) tap to expand

ChorusGraph Native agent runtime with semantic cache, swappable retrieval (PrismRAG), auditable memory, and enterprise hardening — one pip install, five plug-in ports. pip install "chorusgraph==1.1.0" chorusgraph-demo Interactive demo (Product Hunt / launch): insightitsGit.github.io/ChorusGraph/demo.html — click-through walkthrough, no API key for steps 1–3. ChorusGraph = native engine + Prism stack · LangGraph = optional baseline for A/B comparison only (docs/TERMINOLOGY.md) What is ChorusGraph? ChorusGraph is not a LangGraph wrapper. It ships a native BSP graph engine (chorusgraph.core.Graph) with the Prism product stack attached by default: semantic cache, L2 retrieval, L3 memory, Route Ledger, checkpoints, and observability.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub