Grok Bot integration

Grok Bot is an external always-on agent that works on its own cloud computer, separate from this Mac. Nock can send it a task and show its progress, questions, and result in Nock. It is not NockBot: NockBot is Nock’s own cloud agent. Grok Bot uses its own environment and model, and does not automatically receive your current conversation or files.

It is also distinct from Grok Build, the local coding tool whose saved and active chats can appear in the Agents panel. Use Chat Manager for those local Grok chats; use the connection below to send work to a remote Grok Bot.

Set up the connection

Open Settings → Agent → Grok Bot and follow How to connect. The automatic setup is the simplest route:

1. Choose Copy setup message and open the external Grok Bot app.
2. Paste the message into a chat with your bot. Review its request to read the Nock setup file before approving it. The file contains the report-back connection details; keep it private.
3. Follow the bot’s setup instructions to create a routine named Nock tasks that runs when its webhook fires.
4. Open the bot’s computer panel, choose Routines → Nock tasks, then copy the routine’s POST to address and key into the matching fields in Nock. Keep the key private.
5. Choose Connect and test. Check the result and the Reports back status before sending a real task.

The test starts a real, small external run that should report Connected. It waits up to three minutes for the report to come back; an accepted webhook by itself is not proof that the return path works. After a successful report, Nock removes the setup file. You can remove it yourself with Remove setup file.

Send a task

Name Grok Bot explicitly, for example: “Send this to Grok Bot: compare these three public links and report the differences.”

Nock sends a task description rather than forwarding the whole conversation or automatically attaching project files. Include the goal and necessary context explicitly. The external bot uses its own environment and model selection.

Choose Start tasks → Background to send the task through the configured routine. Choose Window to open the external app and type the task; on Mac, that can require Automation permission. If the app is not in front, Nock can leave the text on your clipboard instead. On Windows, the other start choice is Clipboard: Nock opens the external app and you paste and send the task there.

Reports and errors

Progress, questions, and the final result return through the report-back connection. A long quiet period may mean the external bot is waiting for approval in its own app; check there. Nock cannot answer every prompt shown by the external app.

For a failed test, inspect Last test, Reports back, and the connection status in Settings. A rejected key, missing or inactive routine, and unavailable report-back service are different problems. Recheck the saved routine and credentials without sharing the key. If Copy setup message is unavailable because reporting is unavailable, retry after the service recovers; do not substitute an unverified address.

Stop and disconnect

Stop asks the external bot to stop through the report-back channel, but it is not an immediate remote kill. The request reaches the bot when it next reports. Quitting Nock can leave its task running; check the external app to confirm it has stopped.

Disconnect removes Nock’s saved connection and any remaining setup file. Review or remove the external routine in Grok Bot separately. See Coding agents, NockBot, and Privacy.