Skip to content
Start here

POPULAR GUIDES

    FROM THE DOCUMENTATION

    Open this guide ↗
    ↑ ↓ select ↵ open esc closeV3Code Docs
    Nock · NockBot and cloudnock

    NockBot cloud computer

    ↗ View as Markdown

    Learn what the cloud computer can access, how its files persist, and when it wakes or sleeps.

    A NockBot’s cloud computer is the remote workspace where it can work with the selected project. It is separate from your Mac or PC and does not use your local files unless you put those files in the cloud project yourself.

    The workspace keeps the selected repository clone, task worktrees, code index, and embedding-model cache together in the cloud. The service snapshots workspace state so a sleeping or restarted computer can be restored. A new task can use the project workspace without recreating its whole history. A snapshot is not a guarantee that every open app state, browser session, or uncommitted external action is restored.

    The agent can use the project files and cloud browser/computer tools that are available to the bot. It does not automatically get your desktop screen, local disk, or provider credentials. GitHub access is supplied for the cloud task through the connected cloud service; credentials are not intended to be placed in the workspace.

    A question or ordinary chat can be answered without waking the computer. A task that needs code, files, the browser, or computer interaction wakes it. When it is idle, the computer can sleep; a later task can wake it again. View the screen from the cloud bot interface when you need to inspect or take over computer work.

    Cloud workspaces are scoped to the signed-in account and cloud session. Use the same V3Code account when opening NockBot from another supported surface. Avoid putting secrets or personal files in a project unless the cloud task needs them. For provider billing and usage, see Cloud bots and Usage and limits.