NockBot

Create and chat with a Nock agent that works in your cloud workspace.

NockBot is Nock’s cloud agent: a bot, its conversation, and a cloud computer for work that should continue away from your desktop. It is not the same as a local Nock worker, and it is not the separate Grok Bot coding-agent integration.

Create a NockBot

Sign in to Nock with the account that has cloud access.
Open Apps → Cloud and choose New agent → Cloud.
Create or choose a cloud project, then select the bot and project in the cloud view.
Start with a chat or give the bot a specific task.

Cloud bots are a Beta feature on Nock Pro and higher. Free and the trial do not include them. Nock Own does not include cloud bots. The cloud service checks the account’s plan before opening access.

Chat or ask it to work

Ordinary chat does not need to wake the bot’s computer. A task that needs files, a browser, code, or the computer starts the work session. The bot responds in its conversation; you can follow progress, answer its questions, view the computer, or stop the task from the cloud surface.

Connect an app in Nock before asking a bot to use it. In the cloud view, open Apps from the bot list to manage account connections, or open the bot’s face/model sheet and use its Apps switches to choose which connected apps that bot may use. Connections are shared with Nock on your Mac and your other bots; a bot switch only changes access for that bot. Disconnecting the app removes access across Nock on your Mac and all your bots. App permissions and Nock’s action approvals still apply. A NockBot is different from Grok Bot, which uses its separate external account and setup. See Connected apps and Grok Bot.

Choose this bot’s model

In the cloud chat, select the bot’s face and open model and providers. The sheet says Choose a provider, then a model. Select a model under Included with Nock, or expand a provider and choose one of its available models. This choice is for that bot’s cloud conversation; changing Nock’s desktop AI selection does not automatically change every bot.

To use your own provider account, expand that provider, enter a key in [Provider] API key, and choose Connect [Provider]. The sheet confirms the key is saved to your Nock account and used only by your bots. Select a model after its list loads. Your provider bills its model calls separately; this does not pay for cloud-computer hosting, which remains subject to Nock’s fair-use protections.

Talk to a selected NockBot from desktop voice

You can send a spoken message straight to one of your cloud bots from Nock desktop:

Open the bot from Apps → Cloud so its chat is selected in the right-side agent list.
Hold your usual Nock agent-voice shortcut and speak. Nock sends the recognized words to that selected bot’s cloud conversation.
Open the bot’s chat to follow its reply, answer a question, or review the task.

This is a message to the selected bot, not a local voice session moved to the cloud. The voice message sends the words you said; it does not attach your desktop screenshot, a selected screen region, or local drawing automatically. Add the needed material to the cloud project or conversation yourself. To route work from an existing coding chat, use that chat’s Send to the cloud action and choose the bot. This sends a handoff message with recent chat and project/worktree context, which can include a bounded diff of uncommitted changes; it does not move the local chat or copy the full project files. See Cloud computer for the workspace boundary.

Nock’s main voice agent can also send a request to a cloud bot by name. Say or type “ask [bot name] to …” or “tell [bot name] …”; Nock uses the bot’s cloud conversation, and its reply appears in that chat. Check the bot name in the Cloud list first. If more than one bot matches, Nock asks you which one before sending. This is different from selecting a bot as the direct destination for your next held voice message.

Model use and computer use

Cloud AI and hosting are subject to Nock’s fair-use protections, with more room available on higher plans. A provider key saved for the bot can be used for supported model calls; your provider bills those calls. Cloud-computer hosting and resources are separate from provider charges and remain subject to Nock’s fair-use protections.

Use the account’s Usage view to check current cloud service status.

Where the work lives

The cloud bot conversation and workspace are server-side, so they are not confined to the Nock desktop’s local chat history. The workspace contains the selected project clone, task worktrees, and its code index/model cache. Cloud state is saved through the service’s snapshot process; a running computer can sleep when idle and wake for later work.

See Cloud computer, Cloud routines, and Cloud bots.