Try Raven
Docs menu
Get started
Call the API
Use DCode
Use the Raven app
Account and billing
Search the docs/

Remote workspaces

Work on code that lives on another machine, in WSL or in a container, from the DCode desktop app, or run the CLI where the code is.

On this page

In a remote workspace, DCode reads, edits and runs commands where the code is, while you work in the desktop app on your own computer. The agent, its terminal and its files are on the remote side.

Connect

  1. On a new chat, open the workspace menu (Choose workspace) and choose Remote connection.
  2. Choose the method: SSH, WSL, Docker or Server.
  3. Fill in the connection settings and choose Connect. The connection log shows each step as it happens.
  4. When it is ready, choose the directory to open. The workspace opens in the current window.

Saved connections are offered again the next time. Closing the window before you choose a directory discards the session, and going back while it connects cancels the attempt.

The four methods

SSH: a remote host

  • Host, Port and Username. Host and username are required.
  • Authentication method: Password, or Private key with its file and an optional passphrase.
  • SSH config alias (optional): pick a host from your SSH config to fill in the host, port, username and key.
  • Resource download method: DCode sets up the files it needs on the server, either downloaded on your computer and uploaded (Download locally, then upload), or downloaded by the server itself (Download on remote server). The second is quicker, but the server must be able to reach the internet and have tools to download, extract and check files.

WSL: Windows Subsystem for Linux

On Windows, connect to the default distribution or choose one installed on the computer, and the Linux user (the default user unless you pick one). Running as root runs the agent and its terminal as root, so files made in the session may belong to root. When you open a folder by its WSL path, DCode offers to open it through a WSL connection instead.

Docker: a local container

Choose a running container from the list, or type its name or ID if the list is incomplete. DCode works in the container through docker exec and docker cp.

Server: a running DCode server

Connect to a DCode server that is already running: its Server URL, a display name, a Token if the server needs one, and optionally a default directory (leave it empty to choose one after connecting).

Your tools on the remote side

Plugins and MCP servers run where the workspace is. In a remote workspace, Settings, Plugins and MCP servers show which remote you are on and offer to sync your local plugins and MCP servers to it; ones that already exist there are skipped. A server or plugin that needs a program, a file or a variable must find it on the remote machine too.

Computer Use is not available in a remote workspace (Computer Use).

The CLI over SSH

The DCode CLI runs on Linux, macOS and Windows, so you can also install it on the machine where the code is and use it in an SSH session. On a server without a browser, sign in with the link instead:

shell
ssh you@build-servernpm install -g @dipoleml/dcode-clidcode login --no-browsercd ~/code/api && dcode

dcode login --no-browser prints a sign-in link and a code; open the link on any device and approve the sign-in there. For a machine that runs DCode without anyone at it, use an API key instead (Sign in on a CI machine).