# Cursor: Chat is all you need > Source: > Published: 2026-08-18 17:29:55+00:00 Grok Bot has a single output: a message This might seem backwards. Power-user tools are built on complexity and breadth, right? Chat can’t possibly have my workflow. It’s a special workflow. I’m a developer. But what if "power" comes from the underlying system rather than the interface? Instead of code, we now write prompts. We swapped IDEs for TUIs because the terminal was the real tool - chat is just the interface. We don't need a user interface - at least, not in the traditional sense. We need a computer. And rather than using it ourselves, we can give it to an agent. That's Grok Bot: an agent with a computer. I've been using Grok Bot in 4 different ways, and they're chat, all the way down. Personal software AI lowered the cost of code and unlocked personalized software - some even say 'disposable' software. But what is software? Software is logic, persistent storage, and an interface. Software takes inputs, does stuff with it, then returns outputs. Historically, we've described logic as code. Increasingly, we describe logic through English. Persistent storage used to be hard (databases) but now, persistent storage can really be… anything: A CSV, a repository, a JSON file. Interfaces, however, are notoriously difficult. They're designed around rigid workflows - they need to be opinionated, but malleable. All software comes with a tradeoff between simplicity and scope. What I build starts simple, then quickly becomes difficult to manage. Software exists to make life easier, yet most personal software turns into an unpaid second job.¹ We need something better. From software to chat My most recent bout of personal software was a strength training app. I spent weeks refining the UI, adding a database², building out formulae, and writing tests. I built a full preview deploy system and some nice feedback loops for iterating on my app. There was always a new edge case, a new thing to fix, a new problem. I would write down notes and fire off cloud agents. Slowly, it got better! Still, it breaks. One day I wondered - what if this was just a chat? Talking with Grok Bot, I extracted all of the core logic from my app. I rewrote it as a set of skills and MCP servers.³ I asked Grok to come up with a format for logging my workouts. I decided to use Git as the storage layer. Now, Grok sends me my workout each day. I log each workout with a 30 second voice note. If I want to change an exercise, I ask. If a progression looks off, I ask. If I want to add a feature, I ask. The app is more flexible, simpler, and faster. I can add or delete features with a single message. There is no CI, no preview deploy, and no UI to break. I did this while walking to the gym. I update and refine the app as I go. I eventually wanted to build chat into my fitness app. Now my fitness app is chat. Code "Ok forget this guy - he's writing code with a chatbot." For the six of you that made it this far, hear me out. I'm not replacing the coding harness, I'm calling the coding harness. Some of the best engineers at @SpaceXAI are shipping hundreds of PRs, starting in @Bot. Last week, I sat down with @poteto. She described Grok Bot as the perfect "outer loop:" a place to gather & shape context before handing it off. "Context is precious," she said. Agents work on next token prediction: agent inputs directly influence outputs. Chat, files, what agents search for, what agents read. What agents do access is just as important as what they don't access. Lauren and others use Grok Bot to explore ideas, source information, gather context, then stage prompts to fire off Cloud Agents. That work protects the context of inner loop agents. Rather than mucking up my Cloud Agent with a bunch of exploratory research, I can send them only what's necessary - avoiding context poisoning.⁴ Code is abstracted yet another layer up - from Cloud Agents to "Bots" or agent managers. Luckily, Cursor makes this handoff seamless - agents started by Grok Bot are waiting for me inside my Cursor app. You, the human, chat with the outer loop agent. The outer loop agent kicks off inner loop agents. Coding tools are the inner loop, the outer loop is chat. Workflow automation If software is just logic, persistent storage, and an interface, then a workflow is a form of software. We create workflows, chaining together multiple tools, to achieve outcomes. Those workflows require a human. That's a problem, because humans make mistakes and most UIs are very bad. Accounting, shopping, and banking are painstaking operations. I may be dramatizing, but dealing with these websites introduces a real cognitive load. Have you ever booked the wrong flight? Ordered something to the wrong location? Thought you paid for something but didn't? I have. More than personal ops - we all work in similar tools every day. The promise of AI is not to render us useless⁵, but to eliminate things that distract us from real work and creativity. Workflows and GUIs were meant to augment our craft, but too often they replace it. For many, this is the first time we're free to think, express, and dictate our preferences and have someone else implement them. The same way personal software can collapse into chat, consumer and business workflows can collapse, too. The crazy thing is that we don't need MCPs, hosted markdown, or tools. We just need AI and a computer, with the same software we use. That's what Grok is: AI with a computer. Saved search I buy and sell lots of things online. If you've ever browsed a marketplace, you've likely saved and reused searches: It's a godsend. But saved search is really just pre-applied logic - it's a workflow. After I save a search, I start my very particular search process: Is the listing legit? Is the condition good? Is the price fair? Is it nearby? This is my "software," simple filtering logic I use to find what I'd like - logic saved search can't handle, but that Grok Bot can. My Grok Bot is now looking across Craigslist and Facebook Marketplace, checking each day for new espresso machines that match my criteria. It can draft a message and send one for me. It can advise me on what to buy and what not to buy. It can make sure I don't make dumb mistakes (I often do when I'm tired). It's a much better interface than a web browser. Consumer and enterprise UIs are collapsing into chat. Information retrieval Much of knowledge work is search and retrieval. It's asking questions and getting answers. Tools like Notion and Slack revolutionized the way we communicate, but finding the right information is still terribly difficult - especially across multiple sources. Learning is limited by feedback loops. If it takes 2 hours to answer a question, I will have fewer "cycles" than someone who gets an answer in 2 minutes. This can be painful, because many of us were first introduced to plugins and MCP servers through flaky, brittle interfaces. But they've gotten much better - in large part thanks to the Grok Bot team. I've found Grok Bot plugins to be excellent - surprisingly excellent. I've hooked up our codebase, Slack, Notion, my email, my calendar, Figma… Multiple accounts, even. And Grok is scary good at finding things. This was the first thing I did when I joined Cursor. Onboarding at Cursor I onboarded at Cursor in about a week. I asked @leerob a few questions on my first day. Then, I got access to Grok Bot. My onboarding turned into dozens of questions to Grok. Questions about the product, questions about IT, questions about where I should park, or when lunch was. Questions about what launches typically look like, who owns what, where things live. Every single time I thought "Grok won't be able to answer this." Every time, it really did. Sometimes, my years of professional 'experience' kicked in "who owns this thing? I should ping them on Slack." "NO! 🙅♂️" I would tell myself (with that emoji in my head) "I will ask Grok! I will not send my busy teammates more messages!" It turns out, at a company of Cursor's (and now SpaceX's) size, most people have asked your question and a surprising number of things have been documented. But code is more than software, it's a source of truth. Grok Bot has been able to look through our codebase and tell me where things are in the app.⁶ Imagine the wasted hours if I had to ping a person about each question - I probably wouldn't be writing this right now! And now... I'm using Grok Bot to onboard to @SpaceXAI. The future is chat Last year, we watched the IDE collapse to chat. Now, we're seeing other interfaces do the same. More than automating common tasks, Grok Bot has me reconsidering what I build. If I can emulate a workflow with an agent and a SaaS, do I really need to vibe code a solution? Or is an agent and a computer good enough? SaaS is thriving, but the consumers are now computer-use agents. Chat is replacing a surprising number of my other workflows. This is a bit scary: if not for the tools, what is a craftsman? But what if the real tool is English: the ability to articulate what we perceive and desire. And the real craft is having novel ideas about what we build. Chat is the most familiar human interface. We needed skeuomorphic design on the first iPhone because humans understood tactile interfaces. We need chat interfaces with AI, because humans know chat. And it turns out I like bothering my agents with voice notes the same way I like bothering my friends. Footnotes ¹ Unless you work in developer relations :) ² Shout out @convex & @PlanetScale ³ Packaged as Agent Plugins ⁴ Shout out @dbreunig ⁵ The ramblings of effective altruists may lead us to this conclusion ⁶ this tweet, for example