Grok Bot is xAI's AI teammate, in beta since Aug 11, 2026. A Bot can run Ken's Keep campaigns running template on a routine in the cloud, with your laptop closed. For how the templates work and stay safe, see Run Ken's agent templates in your own AI tool.

Before you start

  • A plan that includes Grok Bot. xAI lists it with several Grok, X and Cursor plans. Check in the Grok Bot app.
  • Agent templates on for your workspace. If the Bot says Ken's agent tools are missing, they aren't on for your workspace yet.
  • An Admin or Editor role in the Ken workspace. The agent edits campaigns, and you approve its proposals.

What to know first

  • The Bot acts as you, with your role in Ken. It can do what you can do in Ken. The template tells it to change campaigns only through Ken's agent_team tools, and Ken decides what to apply and what to turn into a proposal.
  • Prefer an API key in a header for a scheduled run. A sign-in can expire and stop a routine without warning; a key in a request header doesn't. If Grok Bot offers a request header when you add Ken, use a key there. Otherwise sign in to Ken in the browser, and check the routine's runs.
  • Never paste a Ken key or password into the Bot's chat. A chat is not a safe place for a key.
  • Switch off Ken's other write tools. Block them with an Auto Review rule (below), and switch them off if Grok Bot lists Ken's tools one by one.
  • Credits. The Bot's thinking runs on your Grok Bot usage and costs no Ken credits. Ken actions cost what they cost in the app: a lead top-up pays for the emails Ken finds and the AI work that follows, the same as when you add the leads yourself. See How credits work.

Connect Ken

  1. In Grok Bot, open Connect apps in the sidebar, then click Add.
  2. Add a custom MCP server with the address https://mcp.ken.so/mcp. If you belong to several Ken workspaces, add the workspace, such as https://mcp.ken.so/mcp?workspace=42.
  3. If there is no field for an address, ask the Bot in chat: "Add Ken's MCP server at https://mcp.ken.so/mcp."
  4. If Grok Bot offers a request header, add Authorization with the value Bearer followed by a Ken API key made for this Bot (see Create a key). Otherwise sign in to Ken in the browser window that opens and select Allow access. Finish the sign-in within about 10 minutes.
  5. Ask the Bot: "Load Ken's skill keep-campaigns-running and tell me its first step." If it can't, it isn't using Ken.

If Grok Bot can't add Ken by its address either way, it can't run Ken's templates yet. Use Claude instead.

Give the Bot its job

  1. Click the Bot's name and rename it after the job, such as Ken - Keep campaigns running.
  2. Paste the starter prompt from Agent templates reference into the Bot's chat, and ask it to remember it. Grok Bot has no instructions field.
  3. Ask it to run the job once now. Check that it loads the skill, reads what changed in Ken, and calls only load_skill, Ken's read tools (names ending in _read) and agent_team_write.

Set Auto Review rules

Auto Review checks risky actions and allows them, asks you, or blocks them. You add Custom Rules on top.

  1. Open Settings, then Bot, then Auto-review.
  2. Add an Allow automatically rule for load_skill, Ken's read tools (names ending in _read) and agent_team_write.
  3. Add a rule that stops every other Ken tool whose name ends in _write, such as "Block Ken tools ending in _write, except agent_team_write". The template never calls them, so the rule only catches a mistake.

Why not ask first on agent_team_write? An approval raised inside a routine expires after about 10 minutes, so a routine that stops to ask at 07:00 while you sleep fails. You don't need the Bot to ask: Ken applies a change only inside your Autopilot bounds, and the rest waits in Ken as a proposal, with no time limit.

Make the routine

  1. Check your time zone under Settings, then Bot, then Timezone.
  2. Ask the Bot: "Every Monday at 07:00, run the Ken job you remembered."
  3. Click the Bot's name, then Details, then Routines. Check the routine's Instruction and When to run.
  4. A new routine doesn't run when you create it, so ask the Bot to run it once now.

Check the first run

  1. Open the Bot's chat, or Run history in the phone app, and read the run. It lists what Ken applied, with each undo deadline, and what it proposed.
  2. Open Today in Ken and approve or skip each proposal.
  3. Ask the Bot: "What changed in Ken this week?" It reads Ken's change log, where each change names who made it.

To undo a change, ask the Bot to undo it before its deadline.

If the Bot says something changed and Ken shows nothing, the call never reached Ken.

Good to know

  • Routines pause if you go quiet. After a long absence the Bot asks whether to keep routines running, and pauses them if you don't answer.
  • Each run spends your Grok Bot usage. There is no spend cap per Bot.
  • A sign-in can expire. The routine then stops reaching Ken. Check the run history, and click Reconnect if Ken calls fail.

Next: Agent templates reference, Use Ken from Claude or ChatGPT or What Ken does on its own.