Nice! I am surprised it's not more common, but part of it is possibly that for the industries that use spreadsheets the most, copilot+excel does the trick.
This is a fascinating approach. Turning spreadsheet cells into agent terminals bridges the gap between structured data and fluid LLM workflows in a very intuitive way. I especially like how the MCP server binds everything together. Out of curiosity, how do you handle state consistency when multiple cells are interacting or modifying shared contexts asynchronously?
On reads, an agent gets a history of old and new values since it started running. For writes, unfortunately, for now it's just last write wins (though there are some guards, like if the user verifies a value an agent writes then it's locked from being re-written).
Interesting approach. One thing that always bites spreadsheet-centric
tools: cell references survive insertion/deletion in weird ways
(formulas don't, LLM "cell pointers" definitely won't).
If a cell's agent output lives at A3 and someone inserts a row above,
is the agent now watching A4? The naive answer is yes, but then
re-running the agent might produce different output than what's
displayed in the referenced range elsewhere. Spreadsheet users are
very used to this working magically for formulas — if agents break
the invariant, it'll feel broken even when nothing technically is.
I punt on this a little bit, in that to make it easier I don't allow actions that would cause issues with this when an agent is still running (insert, delete, sort rows etc...) because it's tough to handle for mid-execution.
However, in the other cases, references get rewritten the same way everywhere (whether it's a formula, or an agent's watch list), so {A3} becomes {A4} etc... everywhere with the same process. Also in that case, it doesn't get marked for needing to be "re-run" because it checks value itself is unchanged, even if the cell being referred to changed.
I've tested it quite a bit. Given all of the moving parts in a spreadsheet app there's still the possibility that given enough usage someone encounters some combination of moves where this fails, but I think if that does happen it should be a fixable bug.
I also provide a backup solution with "Named cells", basically off sheet cells that can be used for constants and such and referenced by name instead of by cell, if needed.
That's a good point. I can keep it separate from user named cells, but make sure everything has a unique identifier I track. Even a million cell workbook would really only add about 50mb of memory, so should be doable.
The passage-level citations are the part I'd use most. What happens to them when the board leaves recalc? Most sheets I make end up with someone who only has Excel or Google Sheets, and if export flattens everything to values, the thing that made the answer trustworthy is gone. Is export planned, and does the citation travel with the cell?
Export does exist, and the citation does travel with the cell as a cell comment (should show up as a red triangle in the corner of the cell in Excel). This feature does need more testing.
As an alternative, I can provide a checkbox on export to have a "sources" sheet created in the workbook with references back to the cell if that works better.
If you do decide to use it, I'm happy to work with you to make sure the export works reliably. I haven't had a good test user for this yet.
Thanks! I do have some videos in the repo demonstrating what it can do; however, if from your experience building fluxcut you have some suggestions on what would make them more useful to people I'm happy to take them!
Another direction I would consider for someone who needs this approach is Grist's MCP integration and a local agent harness.
What have your use cases for it been so far?
If a cell's agent output lives at A3 and someone inserts a row above, is the agent now watching A4? The naive answer is yes, but then re-running the agent might produce different output than what's displayed in the referenced range elsewhere. Spreadsheet users are very used to this working magically for formulas — if agents break the invariant, it'll feel broken even when nothing technically is.
How are you handling that?
However, in the other cases, references get rewritten the same way everywhere (whether it's a formula, or an agent's watch list), so {A3} becomes {A4} etc... everywhere with the same process. Also in that case, it doesn't get marked for needing to be "re-run" because it checks value itself is unchanged, even if the cell being referred to changed.
I've tested it quite a bit. Given all of the moving parts in a spreadsheet app there's still the possibility that given enough usage someone encounters some combination of moves where this fails, but I think if that does happen it should be a fixable bug.
I also provide a backup solution with "Named cells", basically off sheet cells that can be used for constants and such and referenced by name instead of by cell, if needed.
The named cell can have a trivial `=SheetName!a3`. Those will be automatically updated with insert and delete just like any other formula.
They can be referenced directly for reading, and for writing you can do a quick parse and find the original.
I'll play around with this, thanks for the idea!
As an alternative, I can provide a checkbox on export to have a "sources" sheet created in the workbook with references back to the cell if that works better.
If you do decide to use it, I'm happy to work with you to make sure the export works reliably. I haven't had a good test user for this yet.