# remoting \(\#9680\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/cb4f86881556e817067b4c8c839c241a26e078c2)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: cb4f86881556e817067b4c8c839c241a26e078c2

Requested commit: cb4f86881556e817067b4c8c839c241a26e078c2

Commit: cb4f86881556e817067b4c8c839c241a26e078c2

Tree: 311415fcdade6009bb781229f4b4ef4ac240fb22

Author: Conrad Irwin

Committer: GitHub

## Message

```
remoting (#9680)

This PR provides some of the plumbing needed for a "remote" zed
instance.

The way this will work is:
* From zed on your laptop you'll be able to manage a set of dev servers,
each of which is identified by a token.
* You'll run `zed --dev-server-token XXXX` to boot a remotable dev
server.
* From the zed on your laptop you'll be able to open directories and
work on the projects on the remote server (exactly like collaboration
works today).

For now all this PR does is provide the ability for a zed instance to
sign in
using a "dev server token". The next steps will be:
* Adding support to the collaboration protocol to instruct a dev server
to "open" a directory and share it into a channel.
* Adding UI to manage these servers and tokens (manually for now)

Related #5347

Release Notes:

- N/A

---------

Co-authored-by: Nathan <nathan@zed.dev>
```

## Parents

- [f56707e0769a0ca1ccdac4ed1338d5df042c2311](https://git.cafe/gitcafe/zed/commit/f56707e0769a0ca1ccdac4ed1338d5df042c2311?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/cb4f86881556e817067b4c8c839c241a26e078c2?format=markdown)