Maya: Hey builders! Here's what's on the radar today on Cursor HQ. Grok Bots can now use Cursor Projects, a builder torched twenty percent of a weekly limit in ninety minutes, six habits for Cursor Projects, Plan Mode, and Supermemory's rebuilt plugin. I'm Maya.

James: And I'm James. Let's get into it.

Maya: So users say on September thirtieth that Grok Bots can now connect to Cursor Projects. A Grok Bot is a bot you set up and message, say in Slack. You at-mention it whenever you want coding done, and it records video demos of its work.

James: Right, and the split is the interesting part, Maya. The coding runs on Cursor's cloud agents, each with its own computer, so the bot acts more like a manager than a builder. Any model available in Cursor works with them.

Maya: Exactly right. One user creates a team engineer bot, adds it to Slack, and can tell it to create new Projects, grouping related agents into one conversation. Another compares it to phoning an assistant to get the factory building something. That's one person's impression, not a measured result.

James: One more thread, Maya: a separate post says the Grok Bots SpaceXAI's engineers use are free to import and remix. It adds that Cursor's SWE bot alone writes code, triages issues and monitors production.

Maya: Here's one worth a careful read. A builder posted on September thirtieth that they tried a Pro five hundred plan with Ultrafast and blew twenty percent of their weekly limit in about ninety minutes. Their verdict: not worth it. They closed with Opus five point five we are back.

James: And I want to flag something, Maya. The post never mentions Cursor. The Cursor link comes from a Vibin Signal page whose title and slug frame it that way, and its source date is a day earlier, so the dates actually conflict.

Maya: Fair point, James. And it's one person's experience, with no detail on what the session involved or how Ultrafast is metered, so it can't be read as a typical rate.

James: Separately, a developer who has used Cursor Projects since its internal debut shared six habits. Projects use a coordinator agent that dispatches other agents, running in Cloud Agents by default. Tip one: create one Hub project, like an office manager, that audits how the others are working.

Maya: That's a smart anchor, James. They also say start with just a few projects, and pick the coordinator model deliberately. They call Grok four point seven good for coordination, dispatching Opus or Fable for heavy work, since Cursor doesn't bind you to one model.

James: Right, and the rest: give coordinators more autonomy, telling it you don't want to be bothered and having it ask upfront about MCP logins. Set icons and colors to switch context, and enable remote workers for anything localhost-only. These are one user's practices, not documented guidance.

Maya: Next, Plan Mode. A twenty-five tip walkthrough argues the common way to get stuck is opening Agent mode cold, describing a feature with no plan. The agent drifts, you correct, it drifts again, and you're in a long fix-and-retry loop.

James: So Plan Mode is the fix, Maya. You describe what you want, and Cursor writes no code yet. It returns an architecture overview, schema changes, and a checklist of every step. You edit that plan, then click Build, and it switches to Agent mode and works down the list.

Maya: And the caution, James, is that the agent writes into your real files as it works. So test before you accept. Undo All exists, but that window closes while the build continues. The example was a task-labels feature touching frontend, backend, and a database migration.

James: Exactly. And if you have a requirements document or a pull request, attach it as a file at the start of Plan Mode. Vague instructions give vague output, so a clear plan up front saves several correction rounds.

Maya: Last one. Supermemory has rebuilt its Cursor plugin, and it's now on the Cursor Marketplace. Supermemory is an add-on that gives an AI assistant a way to remember what happened in earlier chats and sessions, so you don't repeat yourself.

James: Right, Maya. They announced it on X on September twenty-eighth, in a roundup of integrations shipped over recent months, saying Supermemory now lives in six more places your agents run. The Cursor listing was one of six.

Maya: And one honest limitation, James: the post gives no detail on what the rebuilt Cursor plugin changes compared with the earlier version. It says only rebuilt plugin, now on the Cursor Marketplace. For teams already in Cursor, that's where it lives.

Maya: That's your Cursor HQ daily brief. Check cursorhq.ai for the full stories. Keep building.