Show HN: Sheetgraph, AI agents can understand complex spreadsheets
Hi guys, I built a tool www.lovespreadsheets.com earlier this year and a huge problem we kept running into is processing messy, real-world, complex spreadsheets for AI agents. Even a "medium" sized spreadsheet converts to about 1m+ tokens if read fully, which immediately blows up the current context windows of most models. So I noticed most agents sample data from spreadsheets in chunks instead. So I (& Claude) built this library Sheetgraph, https://github.com/asharma327/sheetgraph
Read original source
Source record
Recorded metrics
points · 1 votes
2026-10-30 15:00:05.255Z
cumulative since publication
Research analysis
Project record
Repository: asharma327/sheetgraph. Source account: Hi guys, I built a tool www.lovespreadsheets.com earlier this year and a huge problem we kept running into is processing messy, real-world, complex spreadsheets for AI agents. Even a "medium" sized spreadsheet converts to about 1m+ tokens if read fully, which immediately blows up the current context windows of most models. So I noticed most agents sample data from spreadsheets in chunks instead. So I (& Claude) built this library Sheetgraph, https://github.com/asharma327/sheetgraph
Observed adoption & comparisons
Source votes: 1 votes (Oct 30, 2026 UTC; cumulative since publication); previous same-scope observation: 1 (Oct 30, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “Show HN: Cerea – yet another self-hosted LLM chat front end” (Show HN, Nov 5, 2026); “Show HN: Lantern Lattice – the call graph from your compiler, for coding agents” (Show HN, Nov 5, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.