Grok Bot integration

Nock’s Grok Bot integration sends a task to your external bot and displays its reports in the notch. It is off by default and requires a working external bot, connection setup, and report-back service. It is distinct from Nock’s own named agents, a local coding CLI, and Nock cloud agents that are not publicly available during launch preparation.

Set up the connection

When the integration is available in your build, open Settings → Agent → Grok Bot:

1. Choose Copy setup message and open Grok Bot.
2. Paste the setup message into its chat. Review the requested setup-file access before approving it. The setup file contains connection information needed to report back; treat it as sensitive.
3. Follow the setup to create the Nock tasks routine. In the external bot’s computer panel, open Routines → Nock tasks and locate its webhook details.
4. Copy the POST to address and key into Nock’s corresponding fields. Keep the key out of chat, screenshots, and support reports.
5. Choose Connect and test. Read both the test result and the Reports back state.

The test starts a real, small external run whose instruction is to report Connected. An accepted request alone does not prove the report-back path works. The test waits up to three minutes for the return report. The setup file is removed after a successful report, and Remove setup file is available separately.

Send a task

Name Grok Bot explicitly, for example: “Send this to Grok Bot: investigate these three public links and return a comparison.” This is an example request, not a claim that a test has run.

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.

Start tasks → Background uses the configured routine. Window opens the external app and types the task; that path needs appropriate macOS automation access. If the intended app is not in front, Nock can leave the task on the clipboard instead. Inspect what actually started before retrying.

Reports and errors

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

For a failed test, inspect Last test, Reports back, and relay status. A rejected key, missing routine, inactive routine, and unavailable report-back service are different problems. Recheck the saved routine and credentials without publishing them. If Copy setup message is disabled because reporting is unavailable, wait for the service rather than inventing a connector address.

Stop and disconnect

Stop stops following the run and requests cancellation through the report-back channel. It is not an immediate remote kill: the bot receives that request when it next reports. Quitting Nock can leave the external run active. Check the external app when you need to confirm work stopped.

Disconnect removes Nock’s saved webhook connection and remaining setup file. Review the external routine separately. See Coding agents, Named agents, and Privacy.