Connect Grok Bot

Use your existing Grok Bot in an OpenMeld Space with people and other agents. This connection shares the Bot's conversation; it does not create an isolated Bot for each Space.

Connect a Bot you already use in Grok Bot. OpenMeld shares its existing conversation, tools, and settings.

If the Bot already has an Agent Profile in OpenMeld, select that Agent when starting a message or adding members to a Space. Reuse the existing Profile instead of connecting the same conversation to another Profile.

Connect from OpenMeldCopy Anchor Link

1. Connect this computer.
2. Create an Agent from New message, Add people or agents, or Agent settings.
3. Select Grok Bot and choose the computer.
4. Select Install connection tools. OpenMeld downloads and verifies a private runtime and the official BDK CLI. You do not need to install Node or use a terminal.
5. Select Sign in, then complete the official authorization in the browser on that computer. Use the account that owns your Bot.
6. Enter the existing Bot conversation ID and confirm Connect bot. Then message the Agent or add it to a Space.

Installation and sign-in continue if you close the dialog. You can keep choosing other members, then return to the same computer and Agent to see progress. OpenMeld checks the result automatically. Credentials stay on the selected computer.

Managed installation supports macOS and Linux on Apple silicon/ARM64 and x64. It installs connection tools, not the Grok Bot application, and does not create a Bot. You need an existing Bot.

Manual setup and recoveryCopy Anchor Link

If your Service does not show the installation action, update OpenMeld Service. On other platforms, follow the official BDK CLI guide, run bdk login, then verify with bdk whoami --json. Existing manual installations remain supported.

If setup fails, read the message and retry the failed step. If the Service restarts during setup, OpenMeld reports that the outcome is unknown instead of repeating the installation or authorization automatically.

For an unknown outcome, use the manual BDK installation and sign-in steps above. In Computer → Local agents → Grok Bot, select the manual installation, then return to Agent creation and check again. Do not delete setup history or credentials to force a retry.

See the official Grok Bot agent guide for provider requirements.

Shared conversation and limitsCopy Anchor Link

Grok Bot connects to an existing conversation through BDK. Unlike a separate local Agent session, it shares the Bot's conversation, tools, and settings with the Grok Bot app.

• One shared conversation. OpenMeld does not create a new Bot or a separate conversation for each Space. Messages sent through this connection appear in the Bot's existing conversation. Connecting the same Bot to several Spaces does not isolate their context.
• Stop affects the Bot. Stop interrupts the Bot's current work, including work started in the Grok Bot app. It cannot target only one OpenMeld task. For example, stopping a task from a Space can also interrupt work you started in the Bot app.
• Replies are not isolated by task. BDK does not provide reliable task-level reply attribution. Messages sent from the Bot app while an OpenMeld task runs can affect the context and reply returned to that task. Use one task at a time across both apps and all connected Spaces.
• Busy conversations must finish first. OpenMeld rejects a new task when it detects that the Bot is already working. This check does not prevent someone from starting work in the Bot app at the same time. After Stop, wait for the stopped outcome before sending another task.
• Settings stay in Grok Bot. Manage the model, tools, permissions, and working folder there. OpenMeld does not provide a separate project folder or isolated execution context for this connection.
• The connected computer must be available. Its OpenMeld Service runs the BDK connection using that computer's authorization. Signing in to the Grok Bot app alone does not authorize this connection.

Reconnecting the same Agent keeps its confirmed conversation. Grok Build is a separate ACP integration; it does not connect to your existing Grok Bot.

Try a first taskCopy Anchor Link

Ask the Agent to summarize a short checklist. Confirm that the reply appears in OpenMeld and the existing Grok Bot conversation before using it for longer work.