What if the best interface for AI agents was the one billions of people already know how to use?
That's the bet behind MetaCells, an open-source project that turns a spreadsheet into a full runtime for AI workflows. Instead of bouncing between prompt playgrounds, Python scripts, and automation platforms like Zapier, you build everything inside cells - formulas, AI prompts, file processing, API calls, and messaging actions all living in the same grid.
The syntax is dead simple. Type 'Write 3 launch taglines for @idea in a cell, and it sends that prompt to your AI provider, pulling in the value from the cell named "idea" as context. Use #compare @product with competitors;4;6 to generate a comparison table that spills across 4 columns and 6 rows. Prefix a cell with /tg to fire off a Telegram message. Upload a PDF and reference it with File:@policy to give any cell access to that document's contents.
The Reactive Model
The real trick is reactivity. Cells reference each other with @cell syntax, and when upstream data changes, everything downstream recalculates automatically - including AI calls. The computation chain runs: data to formulas to prompts to AI output to new data to actions. It's essentially a DAG (directed acyclic graph - a fancy way of saying "things run in dependency order") that happens to look like a spreadsheet.
Broad Provider Support, MIT License
MetaCells connects to OpenAI, Groq, DeepSeek, OpenRouter, Ollama, LM Studio, Together, Fireworks, and xAI. Running local models through Ollama means you can keep everything on your own hardware. The whole thing is MIT-licensed, built on Node.js and Meteor, and ships with Docker Compose for quick deployment.
The project positions itself as "forkable infrastructure" - organizations are meant to clone it and bolt on their own custom formulas, connectors, and AI providers. That makes it more of a foundation for internal tools than a polished end-user product.
Spreadsheets have a genuine advantage here that most AI workflow builders miss: transparency. Every intermediate step is visible in a cell you can inspect, edit, or override. No black-box orchestration layers, no hidden state. For teams that want AI automation but don't trust invisible pipelines, that tradeoff - less polish, more visibility - might be exactly right.