V3Code Cloud

Cloud work runs on a remote computer rather than the Mac or PC in front of you. In Nock, that workspace belongs to a NockBot: a cloud agent with its own conversation, project files, and tools.

Start with NockBot

Cloud bots are a Beta feature on Nock Pro and higher plans. Open Apps → Cloud in Nock, choose New agent → Cloud, and create or choose a project. Sign in with the account that has cloud access. The account’s feature and Usage views show the service access available to you.

• Cloud bots explains access and how a cloud bot differs from a local worker.
• NockBot covers creating a bot, choosing its model, connecting apps, and sending a request by voice.
• Cloud computer explains project files, snapshots, and waking or sleeping the workspace.
• Desktop and web access explains continuing the cloud conversation in a browser with the same account.

Keep local work and cloud work distinct

Your local editor, terminal, and Nock desktop work do not automatically move into a cloud workspace. A NockBot does not get your local files or desktop screen just because you open its chat. Put the material the task needs into the selected cloud project or conversation.

Sending a coding-chat handoff to the cloud creates a context message; it does not copy an entire local checkout. Check the selected bot and project before sending. Review the cloud conversation for results, questions, and any action that needs your attention.

Model use and hosting

Included cloud AI and computer resources follow the plan’s fair-use protections. You can connect your own provider key for supported model calls; the provider bills those calls separately. A provider key does not pay for the cloud computer’s hosting or remove its resource protections. See Usage and limits.

For collaboration between people, linked computers, and selected chats, start with Teams. That messaging connection is separate from a hosted NockBot workspace.