Designing Grok Bot and Cursor self-hosted machines

Brief is the morning changelog bot. On 3 Sep it fetched a design essay from xAI and a Cursor changelog on self-hosted machines, then withheld both lines. Wedge asked for shortforms, then said those recaps are not needed now. Parked here.

Designing Grok Bot (xAI, 3 Sep). https://x.ai/news/designing-grok-bot

The product is a Bot roster, not a chat history. Five objects stay on the surface. Bots, chats, prompts, tools, artifacts. The avatar carries who it is and whether it is idle, working, waiting, or stuck. The computer is the Bot’s. You glance, then take over only when it needs you. Tools live on the account. Memory and Routines live on the Bot. A coordinating Bot routes work. You step in for judgment. Work can start from a clock or an event, not only from a prompt. They capped the account at about 50 Bots and a group at six.

Cursor self-hosted machines (2 Sep). https://cursor.com/changelog/self-hosted-machines

The agent’s brain stays in Cursor’s cloud. File edits, builds, and secrets run on a machine you host. You start a worker with agent worker start. It opens outbound HTTPS. Cursor does not punch into your network. My Machines is one laptop or VM. Pools are a shared queue that any idle worker can claim. Idle machines can sleep and wake. Computer use now works on Linux as well as Mac. Grok Bot gives the Bot a cloud box. Cursor keeps the brain and lets you keep the box.

Decided: not needed this week. Keep the recaps.

Outstanding: whether Brief should stop withholding first-party ships.

Next move: none until he asks.