Grok Bot Provider

xAI's Grok Bot desktop agent as a selectable session engine, plus "ask Grok Bot" for every session: how to turn it on, how it connects through the Grok Bot app's own sign-in, how each session keeps its own conversation, the optional backup route and what it costs, and what v1 leaves out.

Grok Bot is xAI's desktop agent (download it from x.ai/bot). It is a different product from the Grok engine, which talks to xAI's model API. Grok Bot can read and search X, which is why other sessions hand X research to it.

Turn it on

Install the Grok Bot desktop app and sign in (a paid Cursor plan, SuperGrok, or X Premium).
In Omniscio open Settings → Accounts → Grok Bot and switch on Allow Grok Bot sessions.
The card's connection line should read Connected. If it names a problem, it names the fix (open Grok Bot and sign in, open the app once to reconnect, check your connection).

Nothing to paste: Omniscio reads the sign-in the Grok Bot app saved on this PC, decrypts it with the current Windows user's own key, and only ever sends it to Grok Bot's own servers.

Sessions

Pick Grok Bot as the engine like any other.
A new session is a fresh conversation, and resuming continues it. Grok Bot keeps one memory per bot, so Omniscio gives each session its own bot, hidden from your Grok Bot sidebar.
If you deleted that bot in Grok Bot, a resumed session says so and starts a new one.
If Grok Bot can't confirm it received a message, the session says so and never resends it.
"Send while it's working" and the automatic wait-and-retry when Grok Bot is busy work as they do for other engines.

Ask Grok Bot from another session

Any session can call POST /grokbot/ask with a requestId and a task. It gets back the answer, or pending with an askId to check later with GET /grokbot/ask/:askId. The grokbot skill walks an agent through it. Each ask uses its own throwaway bot, deleted once the ask ends. Asks are refused while Grok Bot is switched off, and GET /grokbot/status reads nothing then. Answers come back marked as untrusted text.

Backup route (optional)

If the direct connection breaks (for example after a Grok Bot update), Omniscio can send through a Grok Bot routine with a webhook trigger instead. To set it up, paste the card's setup message into Grok Bot, then add the routine's trigger address and key.

The backup lets that routine run commands on this computer: it needs Grok Bot's "Execution on Local Computer" set to Always allow, and the Grok Bot app running. A backup turn does not carry the session's earlier messages. The answer comes back through a file in ~/.amc/grokbot-outbox/.

What v1 leaves out

Windows only for the direct connection; elsewhere only the backup route works.
Cost is not shown; usage counts against your own Grok or Cursor plan.
No re-attach to a turn that was still running when the app restarted.
Grok Bot has no official API, so a Grok Bot update can break the direct connection. When it does, the session says so in one sentence.

Code references

grokbot-session-manager.ts: the engine
src/main/services/grokbot/: connection, gateway, conversation, ask, backup
cli-server-grokbot-routes.ts: the ask and status routes
GrokBotSection.tsx: the Settings card
Contract: grok-bot-provider-contract.md