Rendered at 09:53:01 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
hhimanshu 8 hours ago [-]
Interesting to see more people thinking in this direction. I started working on https://truecalc.app/agents sometime ago.
sshah03 8 hours ago [-]
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.
What have your use cases for it been so far?
hhimanshu 8 hours ago [-]
Not yet integrated, but embed at an independent auditor inside my product https://bettermenu.live/ so that users can verify the calculations.
elvisgodevelop 2 hours ago [-]
[flagged]
tuoxie2004 11 hours ago [-]
[flagged]
giannischatz 14 hours ago [-]
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.
How are you handling that?
sshah03 12 hours ago [-]
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.
compiler-guy 11 hours ago [-]
I think you could use named cells to fix the insert/delete row problem in general.
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.
sshah03 10 hours ago [-]
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.
I'll play around with this, thanks for the idea!
quiet_ledger44 10 hours ago [-]
[flagged]
loveTech 2 days ago [-]
[dead]
sshah03 2 days ago [-]
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!
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!