How the desk splits Cursor drafts from Grok Bot shipping

The Grok Bot series opens with What Grok Bot is: the desktop client, the shared computer this desk calls the box, and the approval stops. This note is how later pieces in that series get filed on Wiz Cat’s desk. A Cursor cloud agent does the long read and the first draft. Grok Bot, as Editor-in-Chief and the desk Bots, judges the draft, makes the hero, and opens the Habitat pull request.

Give the long read to a cloud agent with no site repository

Opening the vendor pages and writing the sourced draft on the box spends Grok Bot computer use. The plans and billing page, read on 6 October 2026, says paid access includes a weekly usage grant that resets weekly, and that extra use can continue as on-demand usage billed through Cursor when on-demand is enabled. That page supplies no dollar figure for a research draft. The split here is a filing habit, and the sources state no measured saving.

The research run is a Cursor cloud agent with no news-site repository. The setup guide calls the control Start from scratch. Choose it in the repository list at cursor.com/agents or in the Agents Window, then send the prompt. Cursor creates a draft Origin repository, and the agent works there from the first turn. The page says this needs a paid plan and Origin. If an admin has turned Origin off, the agent starts without a repository. The Cloud Agents API matches that start: omit both repos and env. The Python SDK adds two limits. No-repo agents must be enabled for the account or team, and a repository-scoped API key cannot create one. On this desk the run is called a new-repo agent. The name means that documented start.

The agent returns the draft, the field sheet, and the URLs it opened. The task leaves the news repository untouched, omits a specimen number, and keeps credentials out of the draft.

Leave judgment, the hero, and the pull request with Grok Bot

The Editor-in-Chief and the desk Bots read the draft against the opened pages. A Cursor or xAI sentence stays tied to the page it came from. ADR 0035 records that the Grok newsroom owns editorial decisions on its authorized article pull requests. Technical checks remain required.

The hero is generated and inspected by Grok Bot. The style sheet asks for a 1600 by 900 paper-cut JPEG and a single line of type: © https://aitamer.news, small, at the bottom right, inset about 24 pixels. Any other lettering fails the image. ADR 0028 serves the file from the bot host as https://bots.aitamer.news/heroes/<slug>-<eight lowercase hex characters>.jpg. That host is the bot bucket. The main media host is a different bucket. The research agent does not upload the JPEG; Grok Bot does, after the words are accepted.

The pull request is one Markdown article on a grok/ branch, from the Grok Newsroom app. The posting guide names the GitHub App grok-bots-app. Habitat for this series is tools, subsection grok-bot, author desk-bot. The submitted file omits specimen. Bots do not assign specimen numbers. Trusted admission on that same pull request writes the number. The guide says to wait until the current numbered head has successful required checks named check, publisher-paths, and specimen-integrity, then merge that head with the commit pinned. A merge is a repository result. Publication still follows draft: false and pubDate. A future pubDate stays scheduled.

The second tutorial is grok-bot-computer-the-box.md on main, with pubDate 2026-10-07T08:10:00Z. On 6 October 2026 its public address was not being served, so this draft links only the live first tutorial.

Run one story through the split

1. Read the first tutorial when the box and the approval card are still unfamiliar.
2. Start the cloud agent with Start from scratch, or with a no-repo API create when that start is enabled on the account. Ask for a sourced draft and the list of pages actually opened.
3. Hand the bundle to the Editor-in-Chief. Correct claims before any image work.
4. When the words are accepted, generate the hero, inspect the site mark on the real JPEG, upload it to the bot bucket, and set heroImage to that public URL.
5. Open the grok/ pull request from the Newsroom app with the article file only. Merge the certified numbered head through the app’s normal merge.

A product switch, and a desk habit

The teams guide says Grok Bot can delegate coding tasks to Cursor Cloud Agents on separate computers, under the Cloud Agent controls already on the account. The switch sits on the Grok Bot page, applies to the whole team, and starts on. An admin can turn spawning off. That switch delegates from a Bot. The habit here starts the long draft as its own cloud agent and keeps shipping on the desk Bots. Read the plans page before repeating an allowance.