1# Remote Development
 2
 3Remote Development is in the early stages of development. If you'd like to try it please email [alpha@zed.dev](mailto:alpha@zed.dev).
 4
 5Remote Development allows you to code at the speed of thought, even when your codebase is not on your local machine. You use Zed locally so the UI is immediately responsive, but offload heavy computation to the development server so that you can work effectively.
 6
 7## Overview
 8
 9Remote development requires running two instances of Zed. A headless instance on the remote machine, and the editor interface on your local computer. All configuration is done on your local computer.
10
11Currently the two instances connect via Zed's servers, but we intend to build peer to peer communication in the future.
12
13## Setup
14
15> **Note:** You must be in the alpha program to see this UI. The instructions will likely change as the feature gets closer to launch.
16
171. Download and install the latest [Zed Preview](https://zed.dev/releases/preview).
181. Open the remote projects dialogue with `cmd-shift-p remote`.
192. Click "New Server".
203. Choose whether to setup via SSH, or to follow the manual setup.
21   > **Note:** With both options your laptop and the remote machine will communicate
22     via https://collab.zed.dev/, so you will need outbound internet access on the remote machine.
236. On your laptop you can now open folders on the remote machine.
24   > **Note:** Zed does not currently handle opening very large directories (for example, `/` or `~` that may have >100,000 files) very well. We are working on improving this, but suggest in the meantime opening only specific projects, or subfolders of very large mono-repos.
25
26## Toubleshooting
27
28### UI is not showing up
29
30This can happen either if you were just added to the alpha, in which case you need to restart Zed. Or, if you lost connection to the Zed server, in which case you just need to click "Sign In" in the top right.
31
32### SSH connections
33
34If you chose to connect via SSH, the command you specify will be run in a Zed terminal given you an opportunity to type any passwords/keyphrases etc. that you need.
35Once a connection is established, Zed will be downloaded and installed to `~/.local/bin/zed` on the remote machine, and run.
36
37If you don't see any output from the Zed command, it is likely that Zed is crashing
38on startup. You can troubleshoot this by switching to manual mode and passing the `--foreground` flag. Please [file a bug](https://github.com/zed-industries/zed) so we can debug it together.
39
40### SSH-like connections
41
42Zed intercepts `ssh` in a way that should make it possible to intercept connections made by most "ssh wrappers". For example you
43can specify:
44
45- `user@host` will assume you meant `ssh user@host`
46- `ssh -J jump target` to connect via a jump-host
47- `gh cs ssh -c example-codespace` to connect to a GitHub codespace
48- `doctl compute ssh example-droplet` to connect to a DigitalOcean Droplet
49- `gcloud compute ssh` for a Google Cloud instance
50- `ssh -i path_to_key_file user@host` to connect to a host using a key file or certificate
51
52### zed --dev-server-token isn't connecting
53
54There are a few likely causes of failure:
55
56- `zed --dev-server-token` runs but outputs nothing. This is probably because the Zed background process is crashing on startup. Try running `zed --dev-server-token XX --foreground` to see any output, and [file a bug](https://github.com/zed-industries/zed) so we can debug it together.
57- `zed --dev-server-token` outputs something like "Connection refused" or "Unauthorized" and immediately exits. This is likely due to issues making outbound HTTP requests to https://collab.zed.dev from your host. You can try to debug this with `curl https://collab.zed.dev`, but we have seen cases where curl is whitelisted, but other binaries are not allowed network access.
58- `zed --dev-server-token` outputs "Zed is already running". If you are editing an existing server, it is possible that clicking "Connect" a second time will work, but if not you will have to manually log into the server and kill the Zed process.
59
60## Supported platforms
61
62The remote machine must be able to run Zed. The following platforms should work, though note that we have not exhaustively tested every Linux distribution:
63
64- macOS Catalina or later (Intel or Apple Silicon)
65- Linux (x86_64 or arm64, we do not yet support 32-bit platforms). You must have `glibc` installed at version 2.29 (released in 2019) or greater and available globally.
66- Windows is not yet supported.
67
68## Settings and extensions
69
70> **Note:** This may change as the alpha program continues.
71
72You can edit the settings file on the remote instance. To do so, add a new project to your server in the directory `~/.config/zed`. You can create a file called `settings.json` if it does not yet exist.
73
74Note that this is most useful for configuring language servers, as any UI related settings do not apply.
75
76If you'd like to install language-server extensions, you can add them to the list of `auto_installed_extensions`. Again you don't need to do this to get syntax highlighting (which is handled by the local zed).
77
78```
79{
80  "auto_install_extensions": {
81    "java": true
82  },
83}
84```
85
86## Known Limitations
87
88- You can't use the Terminal or Tasks if you choose "Manual Connection"
89- You can't yet open additional files on the machine in the current project.
90- You can't run `zed` in headless mode and in GUI mode at the same time on the same machine.
91
92## Feedback
93
94Please join the #remoting-feedback channel in the [Zed Discord](https://discord.gg/qSDQ8VWc7k).