Grok
- Always-on bots
- On their own cloud computer
- Grok models in Cursor's agents
Runs our bots on their own cloud computer, so routine checks happen without anyone's laptop being open.
- 5bots we describe publicly
- 12repositories watched for silent pushes and failed builds
- 2services it belongs to
- 6tools it connects to
Why we run a bot fleet
Works while the laptop's shut
The bots run on a cloud computer in Cursor's cloud, not on our laptops, with a browser, files and a terminal, so the checks carry on overnight.
Meetings filed for us
Meeting Intel turns each Fireflies transcript into a client log entry and Twenty tasks, and never files the same meeting twice.
Sites watched
Site Watch records each problem it finds in Twenty, and serious ones go to our uptime alerts first.
Silent pushes caught
A change pushed straight to main, or a build that fails, gets an issue raised across 12 repositories, and pull requests get a check for bugs and secrets.
Filed, not just said
Chat is where we talk. The repository, Twenty or a pull request is where the work is kept.
Grok in Cursor's agents
It's one of the models Cursor's agents can run on for bulk jobs, and we pick the model on every launch.
Grok Bot is our night shift. A small fleet of bots runs on one cloud computer in Cursor's cloud, not on our laptops, so the routine checks happen whether or not anyone's laptop is open. They talk to us in one shared Google Chat space, and anything that matters gets filed in our repository or in Twenty, not left in chat.
The bots
- Brain takes our questions and routes them. When we post from the editor, it usually picks the question up within a minute.
- Meeting Intel reads each new Fireflies transcript and files it in the client's activity log and as tasks in Twenty. It checks the Fireflies ID first, so a meeting is never filed twice.
- Site Watch checks our sites for problems and records each finding in Twenty. Anything serious goes to our uptime alerts first.
- A push-and-build watcher catches changes pushed straight to the main branch and failed builds across 12 of our repositories, and files an issue. It also reviews pull requests for bugs and secrets. It doesn't merge anything.
- A second bot posts notes on keeping our git repositories tidy.
Where the work lands
Chat is the live board. The record is the repository, Twenty or a pull request: if it isn't filed there, it didn't happen. Meeting Intel's notes-only pull requests merge themselves, and everything else waits for a person.
Rules the bots work to
- No emails, client messages, publishing or live-site changes unless someone on the team asks for it in that moment.
- No launching Cursor cloud agents on their own, and no Claude models through Cursor.
- No secrets in git, pull requests or chat.
Grok in Cursor's agents
Separately, Grok is one of the models our Cursor agents can run on for bulk coding jobs, next to Cursor's own models. We set the model on every launch, and the thinking and reviewing stays with Claude Code.
As of 10 October 2026.
What we connect it to
A bot only flags what it's been told to look for, and it can't see what happens in our editors' chats. People still decide what matters and what to do about it.
CursorGrok Bot is Cursor's always-on agents, and Grok models are available in Cursor's agents for bulk jobs.
Google WorkspaceGoogle Chat is the shared space where the bots and we talk.
GitHubThe push-and-build watcher looks here for pushes straight to the main branch and failed builds, and files issues.
FirefliesMeeting Intel reads each new transcript from here and files it.
Twenty CRMWhere the bots file tasks and site findings.
AnthropicOne of the models Cursor's agents run on for clear-cut jobs.
Services that use it
We don't sell it on its own. Each of these services uses it alongside the rest of your setup.
- Management, Support & ReportingWe keep improving your ads, website and reporting month after month, so your marketing doesn't stand still.Related tools: Webflow, Google Analytics 4 (GA4), Looker Studio, BigQueryHow it fits
- Custom BuildsWhen nothing you can buy does the job, we build the missing piece and connect it to the rest. We've built and run several of these for ourselves.How it fits
What Grok is
Grok is the AI model family from xAI. We meet it in two places. Grok Bot is Cursor's product for always-on agents, called Bots, each with a name, a job and a memory, working on a cloud computer with a browser, files and a terminal. And Grok models are available in Cursor's agents for bulk coding jobs.
We've written about this
How to make a free websiteYou can make a free website and own it. Here's how we built our own, pacing.agency, with AI coding tools and hosting that can cost nothing, step by step, and the parts that still cost money.Read the note
The secret life of the user ID: what it is, why it matters, and when you can’t use itIf you're not using User IDs, do you really know what your website users are doing? Probably not.Read the note.png)
Why move your website from WordPress to Webflow?Migrations might be a pain, but longer term they're worth it.Read the note
Start with your numbers.
We'll tell you which tools you need and which connections are missing.
Bring your numbers.
We'll tell you if the spend makes sense.
- A 15-minute callYour goals, your challenges, and whether we're the right fit.
- A 1-hour discovery callWe dig into your numbers. Worth a hundred emails.
- A concrete planAds, a custom build or both, as a one-off project or ongoing.