Connect to the Grok Bot cloud computer with Tailscale SSH

A community article, “Connect to the Grok Bot server with SSH,” demonstrates a useful path: sign the local computer and the Grok Bot cloud computer into the same Tailscale account, then connect over the private network.

This is a community workaround, not a first-class feature documented by xAI. It works only while the managed computer permits Tailscale to be installed and run. Do not treat the computer as a permanent production server, and do not assume the Linux user is always box. Run whoami and use the observed result.

Understand the boundary first

Grok Bot works from a persistent Linux cloud computer. Every Bot on the account shares its files, browser sessions, and command-line credentials. xAI recommends /workspace for durable project files and says temporary directories, manually installed packages, and uncommitted state should be treated as replaceable.

Tailscale does not require exposing SSH to the public internet. Both devices join one private tailnet, and policy decides which identity may connect. When Tailscale SSH is enabled, Tailscale handles connections and authentication on port 22 for the device’s Tailscale address.

Good uses include:

• Inspecting artifacts in /workspace from a local terminal
• Deliberate file transfer with scp or rsync
• Read-only diagnostics or short development sessions

Poor uses include:

• Hosting the only copy of a file or a long-running production service
• Bypassing Grok Bot approvals or account boundaries
• Leaving production secrets, recovery codes, or broad credentials on the shared computer

Before you start

Confirm that:

1. You own a Tailscale account; the personal plan is enough for a small test.
2. Tailscale can be installed on the local Mac, Windows PC, or Linux machine.
3. You accept that every Bot on the Grok Bot account can see shared computer files and command-line credentials.
4. Important results are in /workspace and backed up somewhere else.

Step 1: Install Tailscale locally

Open the Tailscale download page, install the client for the local system, and sign in. Continue only after its status is Connected.

Do not create a long-lived auth key for this first setup. Interactive sign-in makes it easier to see exactly which device is being authorized.

Step 2: Inspect the Grok Bot computer before changing it

Send this to Grok Bot first:

Inspect Agent Computer only. Do not change the system yet.

1. Run whoami and report the actual Linux user.
2. Identify the operating system and architecture.
3. Check whether tailscale and tailscaled are already installed.
4. Check whether the current user has the permissions required to install software and start a service.
5. Propose an installation plan based on official Tailscale documentation, but do not execute it.

Do not create an auth key, expose a public port, or change the firewall.

Record the result of whoami. The community article observed box, but current xAI documentation does not promise that as a permanent username.

Step 3: Install and enable Tailscale SSH

After reviewing the inspection, send:

Follow the plan and install Tailscale from its official package source, then start tailscaled.
Use interactive sign-in and enable Tailscale SSH.

Stop when I need to sign in and hand the login page to me.
Do not display or store auth keys, access tokens, cookies, or one-time codes in chat.
Do not listen on a public address or configure a subnet router or exit node.
When finished, return only the device name, tailscale status, Tailscale IPv4 address, and whether SSH is enabled.

For an already connected Linux device, the official opt-in command is:

tailscale set --ssh

During first connection, tailscale up --ssh can sign in and enable SSH together. Complete the sign-in yourself. Do not paste an auth key or sensitive parameters from the sign-in URL into ordinary chat.

If the managed computer lacks the necessary installation permission, stop. Do not escalate privileges, alter the image, or use an unknown script to cross the boundary.

Step 4: Confirm both devices share one tailnet

Open the Tailscale admin console. It should show:

• The local computer online
• The Grok Bot cloud computer online
• Both devices under the same Tailscale account
• A 100.x.x.x Tailscale IPv4 address or usable MagicDNS name for the cloud computer

An unmodified tailnet policy normally lets a user reach their own devices in check mode. A customized policy must allow both:

1. Network access from the source to port 22 on the destination
2. Tailscale SSH from that identity to a non-root user on the destination

Prefer check mode and a non-root account. Do not replace a failed rule with “everyone may SSH everywhere as root.”

Step 5: Connect from the local computer

Use the username verified in step 2:

ssh <verified-user>@<Tailscale-IP>

Use this form only when whoami actually returned box:

ssh box@100.x.x.x

The Tailscale client also provides:

tailscale ssh <verified-user>@<device-name-or-Tailscale-IP>

Replace 100.x.x.x; it is a placeholder, not an address to copy literally.

Step 6: Run a non-destructive acceptance check

Start with read-only commands:

whoami
hostname
pwd
ls -la /workspace
tailscale status

The connection passes when:

• The account matches the inspection and is not unexpectedly root
• The expected /workspace projects are visible
• Tailscale lists only devices you recognize
• Grok Bot continues to work normally after the SSH session closes

Do not install a development stack, add startup services, or move a large directory during the first connection. Prove the access path first.

Common failures

Connection refused

Confirm Tailscale is online on the destination and that tailscale set --ssh was run. Joining a tailnet does not by itself enable Tailscale SSH.

Permission denied

Verify the user against whoami, then inspect both the network grant and the SSH rule. Do not switch to root as a debugging shortcut.

Only one device appears

The devices may use different accounts, or one device may still await authorization. They must belong to the same tailnet.

Tailscale disappears after an update

xAI describes manually installed packages as replaceable state. An Agent Computer update, recovery, or rebuild may require installation and sign-in again. Keep external backups even for files placed in /workspace.

The computer cannot install or start the service

Stop and use Agent Computer, plugins, or file attachments instead. This community path is not an officially guaranteed capability.

Revoke access cleanly

Disable Tailscale SSH on the cloud computer:

tailscale set --ssh=false

If the computer should leave the tailnet entirely:

tailscale logout

Then remove the device from the Tailscale admin console. Disabling or revoking access interrupts active SSH sessions, so save work first.

How to find more tutorials like this

Combine a product name, a capability, and an outcome instead of searching only for “Grok Bot tutorial.”

Useful X searches:

"Grok Bot" (tutorial OR workflow OR routine OR guide) filter:links -is:reply
"Grok Bot" (SSH OR Tailscale OR /workspace OR "Agent Computer")
"Grok Bot" min_faves:20 filter:media
from:0xlangeai "Grok Bot"

Useful Google searches:

site:x.com "Grok Bot" (tutorial OR workflow OR guide)
site:x.com "Grok Bot" (SSH OR Tailscale OR routine)
site:docs.x.ai/grok-bot computer OR routine OR plugin

Run every candidate through five checks:

1. Does it name the date and product version?
2. Does it include reproducible inputs, commands, and an acceptance result?
3. Does it separate official behavior from a community workaround?
4. Does it include permissions, failure handling, and a rollback?
5. Does it ask for tokens, passwords, or durable keys in chat? If so, skip it.

For ongoing discovery, follow official documentation updates, add strong practitioners to a private X list, and repeat a stable keyword set weekly. Save the source, then reconstruct and verify the workflow—do not republish it verbatim.

Sources and verification

Last verified: August 29, 2026.

• Community source: connect to the Grok Bot server with SSH
• Use the computer and apps (xAI)
• Approvals, security, and privacy (xAI)
• Tailscale SSH documentation
• Tailscale quickstart