{"repo":"HomenShum/NodeBenchAI","free":true,"listed":false,"github":"https://github.com/HomenShum/NodeBenchAI","clone":"git clone https://github.com/HomenShum/NodeBenchAI.git","description":"Entity intelligence for any company, market, or question — not a chatbot that answers once, but a system that synthesizes with sources, turns each run into a reusable artifact, and watches for change later. Five-surface app + deep-work Workspace, Convex state, and a hosted public research MCP (npx nodebench-mcp).","language":"TypeScript","stars":14,"topics":["convex","mcp","agents","ai","entity-intelligence","research","typescript","workspace","context-packs","nextjs"],"license":"MIT","category":"ai-agents","readme_excerpt":"NodeBench AI Entity intelligence for any company, market, or question. Live: nodebenchai.com npm: npx nodebench-mcp / npx nodebench-mcp-power / npx nodebench-mcp-admin GitHub: HomenShum/nodebench-ai New to this codebase? Read docs/START HERE.md — it follows one user's question through the code in the order it actually runs, then .tours/ walks the same path inside the live source in VS Code (CodeTour extension). docs/codebase/ has the stack, structure, conventions, integrations, testing and the honest list of known problems. docs/SIMPLIFICATION REPORT.md records what was measured and removed, with the command for every number. Recorded from demo/graph-rail/ replaying a committed eval transcript (persona-episode pack, 2026-01-05) through session.observe() — recorded events replayed, not re-verified; every label is a literal fixture substring, edges are traversal history, never evidence. Regenerate: node scripts/record-graph-rail-clip.mjs . Product NodeBench is a research and reporting product built around five user-facing surfaces: - Home = start quickly - Reports = reusable memory - Chat = do the work - Inbox = captures, nudges, alerts, automations, and unassigned review - Me = operator context and control Deep research opens in the separate Workspace surface at nodebench.workspace ; it is not a sixth tab in the operating app. The core idea is simple: users do not just need a chatbot that answers once. They need a system that can: - take a question, file, URL, or prior thread ","default_branch":null,"files":null,"tree":[],"storefront":"/r/HomenShum","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/HomenShum/NodeBenchAI/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}