# Nobie Makes Spreadsheets a Shared Agent Runtime > Source: > Published: 2026-07-13 22:03:43+00:00 [Dev Tools](https://sourcefeed.dev/c/dev-tools)Article # Nobie Makes Spreadsheets a Shared Agent Runtime A local Mac xlsx engine aims for Excel formula fidelity while humans and LLMs work the same workbook. [Lenn Voss](https://sourcefeed.dev/u/lennart_voss) Spreadsheets still run finance, ops, and a surprising amount of production logic. Agents are finally being pointed at them, but the hard part is not prompting. It is calculation fidelity, file round-trips, and whether a human can still open the workbook tomorrow without surprises. [Nobie](https://nobie.com) is a Mac-native, Excel-compatible runtime that tries to make that shared surface real. It is still beta. Editing, VBA/macros, and multiplayer are explicitly coming later. The bet is interesting anyway: pure `.xlsx` , local-only data, Windows Excel keybindings, and a direct hook for Claude, Codex, or Gemini against the same spreadsheet a person is looking at. That framing matters more than another “Excel on Mac” clone. The useful product is a runtime both humans and agents can trust. ## Fidelity is the product, not the chrome Agent tooling around Excel usually falls into two camps. One is cloud-native copilots inside Microsoft’s stack, including [Agent Mode in Excel](https://www.microsoft.com/en-us/microsoft-365/blog/2025/09/29/vibe-working-introducing-agent-mode-and-office-agent-in-microsoft-365-copilot/), which can generate sheets, iterate, validate results, and steer multi-step modeling inside the real app. The other is programmatic action spaces: catalogs of atomic tools over openpyxl, pandas, and similar libraries so an LLM can write cells, styles, charts, and analysis without a GUI. Both work. Both leave gaps. Cloud agents pull sensitive models into vendor infrastructure and couple you to that ecosystem. Pure Python stacks are excellent for generation and bulk transforms, but full formula parity and “open this in Excel and the numbers still tie” remain the usual failure mode for anything non-trivial. Nobie’s claim is blunt: pixel-perfect fidelity, every formula and cell calculated the same as Excel, full round-trip on standard `.xlsx` . Work in Nobie, open in Excel. Work in Excel, open in Nobie. No proprietary format. For agent workflows that produce real deliverables for controllers, FP&A, or ops teams, that round-trip is the difference between a demo and a handoff. On Mac specifically, the pitch is muscle memory plus speed: preserve Windows Excel shortcuts, stay fast, and avoid the usual second-class spreadsheet experience. That is not glamorous, but it is why people still fight with Excel instead of rewriting models in code. ## Local-only plus bring-your-own model The other half of the design is privacy and model choice. Nobie is local-only. Spreadsheets stay on the Mac. No account required to start. The site states data is not collected, processed, or transmitted, and that Claude, Codex, or Gemini connect directly to the spreadsheet with nothing in the middle. That is a different trust model from “upload the workbook to our agent cloud.” For teams that already have approved API access to a frontier model, but will not ship customer or financial workbooks off-box, the architecture is the feature. It also keeps the spreadsheet as the system of record. The agent is a peer operator on a file humans already know how to audit, diff, and email. That is closer to how finance actually works than a chat transcript that happens to emit a CSV. ## What this means if you build or automate with agents If you are evaluating this as a developer, treat it as an early runtime, not a finished Office replacement. **Where it fits today** - Mac-centric teams that live in `.xlsx` and need a local viewer/runtime with Excel-compatible calculation claims. - Agent prototypes where the model should reason over a real workbook layout (formulas, tables, charts/pivots as supported) without inventing a parallel data model. - Workflows that must round-trip to desktop Excel for sign-off. **Where it does not fit yet** - Editing-heavy automation. Editing is listed as coming soon. If your agent needs to mutate sheets reliably today, you are still in openpyxl/xlwings territory or Microsoft’s own agent path. - VBA/macros and multiplayer. Both are roadmap items, not current promises to build on. - Cross-platform fleets. This is a Mac product story right now. **Practical comparison** | Approach | Strength | Weakness for agents | |---|---|---| | Nobie (local xlsx runtime) | Fidelity + local data + BYO model | Beta; editing/VBA not ready | | Microsoft Agent Mode | Native Excel, iterative fix loop | Cloud/Copilot coupling, ecosystem lock | | Atomic tool agents (openpyxl/pandas) | Scriptable, CI-friendly, no GUI | Formula/engine parity and handoff risk | A sane adoption path is narrow. Use Nobie where calculation fidelity and local residency matter more than full edit automation. Keep generation and bulk transforms in code. Keep final review in Excel. Do not redesign a production close process around a beta runtime with editing still on the way. If the fidelity claims hold under real models (array formulas, pivots, edge-case financial sheets), the interesting integration is boring and useful: agent writes or proposes structure, Nobie evaluates like Excel, human reviews with familiar shortcuts, file remains plain `.xlsx` for the rest of the org. ## Early, but pointed at the right problem Microsoft is clearly investing in agentic Excel inside the mothership. Open-source action spaces keep expanding the “LLM hands” for spreadsheet construction. Nobie is aiming at the gap between them: a local, pure-xlsx calculation surface on Mac that humans already know how to drive, with AI as a first-class operator rather than a chat sidebar bolted on later. That is a real developer-adjacent problem. Finance and ops automation fails less on model IQ than on broken formulas, silent calc differences, and files that cannot be audited by the person who owns the P&L. Nobie is free forever for the Excel/Google Sheets-class feature set it ships, local-only, and still missing pieces that matter for day-to-day editing. Watch the calculation engine and edit path. If those land with the fidelity the marketing asserts, it becomes a serious option for teams putting agents on real workbooks without giving up Excel as the shared runtime. Until then, treat it as a promising Mac-native experiment, not the system of record. ## Sources & further reading - [Show HN: Nobie – an Excel-compatible runtime for agents and humans](https://nobie.com)— nobie.com - [HN: A Fast Hacker News Client](https://hn.blode.co/)— hn.blode.co - [GitHub - Bread-Technologies/Bread_Excel_Agent: LLM-powered Excel automation with 110 atomic tools for creating, formatting, and analyzing spreadsheets through natural language · GitHub](https://github.com/Bread-Technologies/Bread_Excel_Agent)— github.com - [Vibe working: Introducing Agent Mode and Office Agent in Microsoft 365 Copilot | Microsoft 365 Blog](https://www.microsoft.com/en-us/microsoft-365/blog/2025/09/29/vibe-working-introducing-agent-mode-and-office-agent-in-microsoft-365-copilot/)— microsoft.com [Lenn Voss](https://sourcefeed.dev/u/lennart_voss)· Cloud & Infrastructure Writer Lenn writes about cloud platforms, Kubernetes internals, and the infrastructure decisions that quietly make or break engineering organizations. Based in Berlin's vibrant tech scene, they have a talent for turning dense platform-engineering topics into prose that people actually finish reading. ## Discussion 0 No comments yet Be the first to weigh in.