STEP BY STEP GUIDE
Method
GitHub + Tailscale
Protocol
RDP
Level
Beginner
Tutorial
How To Setup RDP Using GitHub (Tailscale Method)
A step by step guide to connecting to a remote Windows session over Tailscale from a GitHub workflow, with the safety and rules you need to know first
TAILSCALE
PRIVATE NETWORK
READ THE WARNING
RDP
GitHub
Tailscale
2026
This tutorial explains how the GitHub plus Tailscale RDP method works: a GitHub workflow starts a Windows machine, joins it to your private Tailscale network, and you connect to it with Windows Remote Desktop. You get the workflow file, the Tailscale download, the full steps, security tips and troubleshooting. Please read the rules warning in this post before you try it.
Needs
GitHub + Tailscale
Connect With
Remote Desktop
File Provided
Workflow File
Important Warning Before You Start
WARNING: GitHub's terms say Actions should not be used for activity unrelated to the production, testing, deployment or publication of the software project in the repository. GitHub also says it may monitor usage, and misuse can lead to terminated jobs, restricted access, disabled repositories or account suspension. Using GitHub-hosted runners as a general remote desktop may fall outside those rules, so you do this at your own risk and only with an account you can afford to lose. Never use this method for mining, for accessing systems you do not own, or for any illegal purpose.
What Is The GitHub And Tailscale Method
GitHub Actions runs jobs called workflows on machines that GitHub provides. Tailscale is a private network service that connects your devices together so they can reach each other as if they were on the same network. In this method, the workflow starts a Windows machine, joins it to your Tailscale network, and you connect to it from your own PC using the built-in Windows Remote Desktop Connection.
Tailscale is the safe part of the setup because the remote machine is reachable only from devices signed in to your own Tailscale network, not from the open internet. Tailscale's own GitHub Action is designed to join a workflow to your tailnet, and each run creates a temporary node that is removed when the workflow finishes.
Because the session lives inside a workflow job, it is temporary. When the job ends the machine is gone, so treat it as a disposable session and do not store anything important on it.
Downloads
Workflow File
The GitHub workflow file for this method. It is shared as an XML-named file, so you will rename it to end in .yml before adding it to your repository, as explained in the steps below.
Tailscale
The Tailscale client. Install it on your own PC and sign in to the same account, so your PC can reach the remote machine.
What You Need
| Item | Details |
|---|---|
| GitHub account | With permission to create a repository and add repository secrets. |
| Tailscale account | With Owner, Admin or Network admin permission so you can create an auth key. |
| Your PC | Windows with Remote Desktop Connection (mstsc) and the Tailscale client installed. |
| Workflow file | Downloaded from this post. Open it in a text editor and read it before using it. |
| Tailscale auth key | Created in the Tailscale admin console. Keep it secret. |
Step By Step Guide
1
Create your accounts. Make a Tailscale account and a GitHub account if you do not have them already.
2
Install Tailscale on your PC. Download it from Server 2 above, sign in, and check that your PC appears in the Tailscale admin console.
3
Create an auth key. In the Tailscale admin console, open the Keys page and generate an auth key. Keys last 1 to 90 days, with 90 as the default. Choosing an ephemeral key removes the device after it goes offline. Copy the key and keep it private.
4
Create a private GitHub repository. Use a private repository so that workflow logs are not public.
5
Add the secret. In the repository go to Settings, Secrets and variables, Actions, and add a new repository secret that holds your Tailscale auth key. Use the exact secret name that the workflow file expects. Open the file and look for it. Tailscale's own examples name it TAILSCALE_AUTHKEY.
6
Add the workflow file. GitHub only runs workflows that are stored in the .github/workflows folder and end in .yml or .yaml. Rename the downloaded file from .xml to .yml, then upload it to .github/workflows in your repository.
7
Run the workflow. Open the Actions tab, select the workflow and run it. Wait until the job reaches the step that keeps the session open.
8
Find the machine's Tailscale address. Open the Machines page in the Tailscale admin console and look for the new device, or read the address in the workflow log.
9
Connect with Remote Desktop. On your PC open Remote Desktop Connection, type the Tailscale address, and sign in with the username and password defined in the workflow file.
10
Finish cleanly. When you are done, stop the workflow run from the Actions tab so the session ends, and delete the auth key in Tailscale if you no longer need it.
Security Tips
Keep The Auth Key Secret
Store it only as a repository secret. Never paste it in the workflow file, in a post or in a chat. Tailscale warns to be very careful with reusable keys.
Use Private Repositories
A private repository keeps workflow logs and settings away from the public.
Prefer Ephemeral Keys
An ephemeral key removes the device after it goes offline, so old sessions do not pile up in your network.
Use A Strong Password
Use a long, unique password for the remote session and never reuse a password from another account.
Revoke Keys When Done
Delete or let expire any auth key you no longer use. Revoking a key does not remove devices already registered, so also delete old devices from the Machines page.
Read The File First
Open the workflow file in a text editor and read every line before you run it. Run only what you understand.
Troubleshooting
The workflow does not start
Check the file ends in .yml, sits in .github/workflows, and that Actions is enabled for the repository.
The workflow fails at the Tailscale step
Check that the secret name matches the workflow file and that the auth key has not expired. Auth keys last between 1 and 90 days.
I cannot see the machine in Tailscale
Make sure the workflow reached the Tailscale step and that the key was not revoked. Ephemeral devices disappear after they go offline.
Remote Desktop cannot connect
Confirm Tailscale is running on your PC and signed in to the same account, use the Tailscale address of the new machine, and check the username and password from the workflow file.
The session closed by itself
Workflow jobs are temporary and end when the job finishes or hits its limit. Start the workflow again to get a new session.
My GitHub account got a warning
GitHub may restrict or disable accounts that misuse Actions. Stop using the method and follow the instructions in the notice.
Information
| Topic | RDP using GitHub Actions and Tailscale |
| Tools | GitHub Actions, Tailscale, Windows Remote Desktop Connection |
| Files In This Post | Workflow file (rename .xml to .yml) and Tailscale download link |
| Difficulty | Beginner to intermediate |
| Session Type | Temporary, ends with the workflow job |
| Main Risk | May break GitHub's rules for Actions, so use at your own risk |
Keywords
rdp using github
github rdp tailscale
how to setup rdp using github
tailscale rdp
tailscale github actions
github actions remote desktop
tailscale download
tailscale auth key
remote desktop windows tailscale
rdp setup guide 2026
tailscale remote desktop tutorial
tech decode rdp
DISCLAIMER: This tutorial is for educational purposes. GitHub and Tailscale are trademarks of their respective owners and Tech Decode is not affiliated with them. GitHub's terms restrict how Actions may be used, and accounts that break them can be suspended, so you are fully responsible for how you use this method. Do not use it for cryptomining, for unauthorized access to any system, or for anything illegal. Read the workflow file before running it and keep your keys private.
.jpg)
){kind=link}
0 Comments