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
• search and synthesize with sources
• turn the run into a reusable artifact
• watch for meaningful change later
• improve the next run from what it learned

Pending Release Candidate: Runtime-Grounded Control Focus

This candidate is not yet merged or deployed. It narrows the reachable product to controls backed by a real runtime capability and makes unavailable state explicit:

• Agents keeps ask, explicit swarm launch, active work, approvals, sources, traces, receipts, exports, and provenance while removing projected metrics, synthetic fallbacks, duplicate actions, and local-only controls.
• Generated code remains copyable and exportable but never executes inside the signed-in app origin. Runtime cards accept successful structured tool output, not assistant prose, guessed search fields, or incomplete/error states.
• Canonical owner-scoped streaming remains; an unreferenced bearer-stream component and HTTP route were removed instead of retained as a second path.
• Home, Reports, Chat, Inbox, and Me use live runtime data, owner-scoped where private, or honest loading, empty, not-found, and unmeasured states instead of reachable product fixtures. Desktop and mobile now share the same Inbox and Me component trees; duplicate queue/profile renders and their hard-coded plan, usage, connector, and local-draft projections were deleted.
• Pipeline launches and schedules require an authenticated server identity, while guest history, detail, bundle, stream, and evaluation reads require an anonymous-session possession credential. Browser-supplied owner keys are no longer an authority boundary, and trusted cron or MCP work stays on internal contracts.
• Authenticated launches consume durable per-owner admission: four units per ten minutes and thirty per day, with composed runs costing two units.

... View full README on GitHub