How to Connect a Computer to Rabbit OS3 with Rabbit Agent

Rabbit OS3 became generally available on September 22, 2026, and one of its most useful features is the ability to connect an existing Windows, macOS, or Linux computer as a node. The local Rabbit Agent lets OS3 work with software, files, tools, and commands already available on that machine. This tutorial shows how to register a computer, install Rabbit Agent, verify the connection, and remove the node safely when you no longer need it.

What Rabbit Agent actually does on your computer

Rabbit Agent is a small local program that connects a computer to your OS3 account. Rabbit describes the connected machine as a node, and OS3 can use that node when a task needs local software, files, or command-line tools. The agent runs locally, while OS3 itself uses cloud services and the artificial intelligence model provider configured for the account.

This distinction matters before you install anything. Connecting a node does not mean Rabbit automatically copies the entire computer into the cloud, but OS3 can operate the connected machine when you approve a task. Rabbit's current terms explicitly describe capabilities such as reading files, opening applications, typing, browsing the web, installing tools, and completing transactions, so the agent should be treated as software with meaningful control over the machine.

Check the computer before registering it

Rabbit Agent supports Windows, macOS, and Linux computers, including cloud machines that you control. You do not need a Rabbit R1 to use OS3, because the OS3 workspace is available through a browser. Before starting, make sure you can sign in to your Rabbit account and that you have administrative permission on the computer where the agent will be installed.

It is also worth choosing the machine deliberately. A development workstation containing source code, credentials, browser sessions, and production tools has a much larger security footprint than a clean test computer. For your first experiment, a machine with limited access to sensitive accounts gives you a way to understand what the agent can do before connecting your main workstation.

Open Rabbit OS3 and register a new agent

Sign in to the OS3 workspace in your browser. Open Settings, then select Rabbit Agents. Choose Register Rabbit Agent. OS3 will generate a registration token and display installation commands for the supported operating systems.

Leave that registration page open while you install the agent. The token is temporary, so do not generate one and wait several hours before using it. If the token expires, start the registration process again and use the newly generated command.

Install Rabbit Agent on Windows

On the Windows computer you want to connect, open a normal PowerShell terminal rather than an agent-controlled terminal. Return to the Rabbit Agents page in OS3 and copy the Windows installation command generated for your registration. Paste that command into PowerShell and press Enter.

The installer uses the registration information supplied by OS3 to associate the local program with your account. Wait for the command to finish before closing PowerShell. Rabbit's support documentation says a successful installation reports that installation has completed, after which the computer can appear as a connected node in OS3.

Do not manually modify the generated command. OS3 creates the registration information for the particular node, and changing the command can prevent the computer from pairing correctly.

Install Rabbit Agent on macOS or Linux

On macOS or Linux, open a new terminal session and return to Settings > Rabbit Agents in OS3. Select Register Rabbit Agent and copy the command generated for macOS or Linux. Paste it directly into the terminal and run it.

Use a terminal that you opened yourself rather than executing the installer from another AI agent session. Rabbit specifically recommends running the installation command directly in a terminal. When the installer finishes successfully, return to the Rabbit Agents page and wait for the new computer to appear in your account.

Confirm that OS3 can see the connected computer

Return to Settings > Rabbit Agents after the installation finishes. The computer should appear in the list once the local agent has paired with your account. If it does not appear, check that the installation completed successfully and that the registration token had not expired before you ran the command.

Give the node a useful name if you have several computers. Names such as home-pc, dev-laptop, or linux-server make it much easier to understand where a task will run. Rabbit says one OS3 account can connect up to five devices, so naming becomes increasingly useful once you have more than one node.

Test the node with a harmless task first

Do not begin by asking OS3 to modify important files or install software. Start with a read-only task that tells you whether the correct computer is being used. For example, ask OS3 to inspect the connected machine and identify the operating system and a harmless local directory that you know exists.

Check the response against the computer you actually connected. If the result identifies the wrong machine, stop there and review the node list before giving OS3 another instruction. A simple verification task is much easier to recover from than discovering the mistake after an automated task has changed files.

Once the node responds correctly, try a small operation that has an obvious result, such as asking the agent to create a temporary text file in a test directory. Check the file yourself before moving to more consequential work. This gives you a practical checkpoint for understanding what OS3 can access through the node.

Use OS3 with your existing development tools

The useful difference between a cloud-only assistant and a connected Rabbit Agent node is the local environment. If a project already has its dependencies, command-line tools, source files, or build environment installed, OS3 can work from that environment rather than starting with an empty machine.

For example, a connected development computer could be asked to inspect a local project, run an existing test command, or examine the output of a build. The exact task depends on the tools installed on the node and the permissions available to the agent. Keep the first experiments inside a disposable project so that an unexpected command cannot damage an important repository.

OS3 also supports multiple connected computers. Rabbit says the service can use up to five devices on one account and determine where a task should run. That makes the node concept more useful than simply remote-controlling one desktop: a project can have access to different environments without requiring every tool to be installed everywhere.

Understand what happens to your data

Rabbit says Rabbit Agent does not automatically copy all files from the connected computer to its servers. However, that does not mean everything involved in a task stays local. OS3 operates as a hybrid service, and information required to reason about a task can pass through Rabbit's infrastructure to the artificial intelligence provider selected by the user.

That distinction becomes important when working with private source code, customer information, contracts, credentials, or production data. Before asking the agent to inspect a sensitive file, determine what information the task requires and which model provider is configured for the account. Treat the node as a privileged automation component, not as an ordinary desktop utility.

Remove Rabbit Agent when you are finished

If you no longer want a computer connected to OS3, the recommended removal method starts in the OS3 workspace. Open Settings > Rabbit Agents, find the computer, choose Remove, and confirm the operation. Rabbit says the agent will be uninstalled automatically within about 30 minutes once the computer is connected.

For a computer that needs immediate manual removal, Rabbit also provides operating-system-specific uninstall commands through its support documentation. Use the uninstall command supplied by Rabbit rather than attempting to delete individual agent files yourself. Afterward, remove the corresponding device entry from the Rabbit Agents settings if it remains listed.

What to do if the node stops responding

Start by checking whether the computer is powered on and connected to the network. Then look at the Rabbit Agents list in OS3 and confirm that the node still belongs to the account you are using. If the original registration token expired before installation completed, register the agent again to obtain a fresh token.

If the agent was installed successfully but the node never appears, repeat the registration process from the OS3 settings page rather than guessing at command-line parameters. For multiple computers, also verify the node name so you are testing the machine you intended to connect. Once the connection works, keep the node's role clear: a development machine should not silently become the place where unrelated production automation runs.

Rabbit Agent makes OS3 considerably more useful because it connects an AI-controlled workspace to computers that already contain the tools and environments people use every day. The trade-off is equally clear: giving an agent access to a real machine means permissions and data handling become part of the programming problem. Start with a disposable node, test one operation at a time, and expand its access only after you know exactly what the connected computer allows.