Skip to main content
Grok Bot is xAI’s always-on agent. Each bot has its own computer in the cloud, so it keeps working after you close your laptop, and you talk to it the way you’d text a teammate. Install the Kino desktop app on that computer and the bot gets the full editor: your library, the timeline, motion graphics, and export. Nothing to configure on your side. The Kino desktop app ships its own MCP server, and it runs on the bot’s computer, next to the bot.
A Grok Bot conversation: the bot posts a rendered SemiAnalysis clip and three motion-graphic stills from Kino, and the user asks it to send the link to the team

Set up

Grok Bot comes with SuperGrok and Cursor Pro plans. Once you have a bot, send it this:
The bot installs the app, asks how you sign in, and reports back with your project list. With email sign-in, paste the one-time code into the chat when it arrives. With Google, the bot hands you its sign-in page so you can approve it yourself. Keep Kino open on the bot’s computer. The MCP server runs only while the desktop app is running, and the bot can relaunch it if it ever quits.

Ask for an edit

From here it’s a chat. Give the bot a project, or a reference, and tell it what you want back:
The bot replies with a link to the project, a rendered clip you can watch in the thread, and a note on what it changed. Long jobs are fine. It messages you when it’s done, not when you check in.

What it can do

The bot has the same tools as any agent on the Kino MCP server: transcript and visual search, timeline edits, composition code, screenshots to check its own work, and export. The prompts that work in Claude Code and Codex work here too.

Troubleshooting

  • If the bot says Kino isn’t running, ask it to open the desktop app again. The server stops when the app quits.
  • If sign-in stalls, tell the bot which method you use for Kino and have it start the sign-in again.
  • To see what the bot did, open the project link it sends. Its edits show up in version history like anyone else’s on the team.