Bring your files into the conversation. Connect your computer to your Assistant,
choose its working folder, and stay in control of its access.
Windows app · Linux server agent · standalone CLI
Start with RBDapp on Windows.
Sign in with your own RBD account, approve this computer and its working folder,
then select it in the Assistant. An RBD admin or special-user role is not required to link your computer.
The Windows installer is unsigned. Windows may display an unknown-publisher warning.
① Install · ② Sign in and approve · ③ Wait for Ready
Choose where you work
Your Windows PC RBDapp
Use My computers → Add computer on your desk. Keep RBDapp running while the
Assistant works. You choose the approved folder and can pause or revoke access.
Your Linux server Advanced setup
A dedicated service account connects one approved folder. This agent works with files;
it does not run shell commands, install software, or administer the server.
See Linux requirements.
Standalone CLI — Windows PowerShell
# run in PowerShell
irm https://rbdhub.com/downloads/rbd-code/install.ps1 | iex
Then type rbd in that window. The standalone CLI has its own
model settings and access prompts. Installing it does not link this computer to your desk.
Review the published version and engine SHA-256 in releases.json.
Approval and readiness are separate.
A successful link adds the computer to your account. Wait for Ready before sending work;
it means the agent has checked in and can use the approved access. Hosted assistant use requires
a Passport or Special access. Linking never grants Windows or Linux administrator privileges.
Work with clear boundaries
▸
Your selected computerChoose the destination in the Assistant. Your computers do not share files automatically.
▸
Your approved accessReview folders and permissions in My computers. Project folders organize conversations; they do not widen access.
▸
Your model choiceSelect an available account model or configure a supported local model. Unconfigured models show setup guidance.
▸
Pause when neededPause new work or revoke the link in My computers. Changes already made to files are not undone.
Connect a Windows computer
Download and open RBDapp on the computer you want to connect.
Sign in with the same RBD account you use on your desk.
Choose a working folder and approve that computer in your browser.
Wait for Ready in My computers, select it in the Assistant, and choose your model.
Engine and file access requirements
Windows: x64 and a working folder on a local NTFS drive. Use Node.js 24.21.0 for a manually
installed engine. Network shares, UNC paths, and linked or redirected folders
are not supported by the verified file tools.
Linux: x64 with glibc, Linux kernel 5.6 or newer, and Node.js 24.21.0.
macOS and ARM computers are not supported by these file tools. No compiler is needed.
An operating-system administrator prepares a dedicated nonroot service account, a verified
engine and Node runtime, one working folder, and a separate private state folder. The service account
must not have sudo rights. Keep its credentials and state outside the working folder.
Review the service template
and prepare its paths and permissions.
Run computer connect as the service user with explicit state and workspace paths.
Open its approval link, sign in to your own RBD account, and approve this server and folder.
Start the service and wait for Ready. It connects over outbound HTTPS; no inbound port is needed.
Create destination parent folders in advance. This file-only agent cannot create Linux
parent folders, run shell commands, or manage services. Updates are operator-managed: preserve the
private state and working folder so pairing and files remain in place.
If supported file access cannot start, the computer can remain connected without becoming
Ready. Check its setup before sending work. Approval applies to the named computer and folders only.
