add-remote-access
Skill1 starsChanged 7 months agoMITView on GitHub
Set up remote access to IronClaw via Tailscale (private VPN)
- Reads credentials
- Installs packages
In this repository9 other files it gives its agents.
- add-agentSkill
- add-telegramSkill
- configureSkill
- resetSkill
- security-auditSkill
- setupSkill
- startSkill
- stopSkill
- switch-agentSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Check if Tailscale is installed:
- Distinctive: line 17
If not installed, tell the user:
- Distinctive: line 27
If not connected, tell the user to open the Tailscale menu bar app and sign in.
- Very specific: line 33
Check if IRONCLAW_WEB_PASSWORD is set in the web package's env:
- Distinctive: line 38
If not set, use AskUserQuestion to ask the user to enter a password.
- Very specific: line 55
Update the root .env with the Tailscale IP for CORS:
- Very specific: line 60
Update packages/web/.env.local so the web app connects to the gateway via the Tailscale IP:
- Distinctive: line 75
Ask the user to confirm they can:
- Distinctive: line 81
If the web app loads but WebSocket fails (connected indicator shows red):
- Very specific: line 82
Check that CORS_ALLOWED_ORIGIN in .env matches http://<TAILSCALE_IP>:3000
- Very specific: line 83
Check that NEXT_PUBLIC_GATEWAY_TOKEN in packages/web/.env.local matches GATEWAY_WS_TOKEN in .env
- Very specific: line 96
If the Tailscale IP changes, re-run /add-remote-access to update the config
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/add-remote-access — Remote Access Setup
Set up remote access so you can use the IronClaw web app from your phone or other devices while it runs locally on your machine. Uses Tailscale — a private mesh VPN that's free for personal use.
Step 1: Check Prerequisites
Check if Tailscale is installed:
which tailscale 2>/dev/null || ls /Applications/Tailscale.app 2>/dev/null && echo "INSTALLED" || echo "NOT_INSTALLED"If not installed, tell the user:
- Download from https://tailscale.com/download/mac (installs as a menu bar app)
- On iPhone/Android: search "Tailscale" in the App Store / Play Store
- Note:
brew install tailscaledoes NOT work — must download from the website
Check if connected:
/Applications/Tailscale.app/Contents/MacOS/Tailscale status 2>/dev/null | head -5 || tailscale status 2>/dev/null | head -5If not connected, tell the user to open the Tailscale menu bar app and sign in. Both devices (Mac and phone) must be signed into the same Tailscale account.
Step 2: Ensure Web Authentication is Enabled
CRITICAL: Remote access without authentication means anyone on your tailnet can access your agent.
Check if IRONCLAW_WEB_PASSWORD is set in the web package's env:
grep -q "^IRONCLAW_WEB_PASSWORD=." packages/web/.env.local 2>/dev/null && echo "SET" || echo "NOT_SET"If not set, use AskUserQuestion to ask the user to enter a password. Then add it:
printf "\nIRONCLAW_WEB_PASSWORD=%s\n" "USER_PASSWORD" >> packages/web/.env.localAlso ensure the root .env has GATEWAY_WS_TOKEN set (should already be from /setup):
grep -q "^GATEWAY_WS_TOKEN=." .env 2>/dev/null && echo "SET" || echo "NOT_SET"Step 3: Get Tailscale IP and Configure
Get the Tailscale IP:
/Applications/Tailscale.app/Contents/MacOS/Tailscale ip -4 2>/dev/null || tailscale ip -4 2>/dev/nullUpdate the root .env with the Tailscale IP for CORS:
grep -q "^CORS_ALLOWED_ORIGIN=" .env && sed -i '' "s|^CORS_ALLOWED_ORIGIN=.*|CORS_ALLOWED_ORIGIN=http://<TAILSCALE_IP>:3000|" .env || echo "CORS_ALLOWED_ORIGIN=http://<TAILSCALE_IP>:3000" >> .envUpdate packages/web/.env.local so the web app connects to the gateway via the Tailscale IP:
grep -q "^NEXT_PUBLIC_GATEWAY_URL=" packages/web/.env.local && sed -i '' "s|^NEXT_PUBLIC_GATEWAY_URL=.*|NEXT_PUBLIC_GATEWAY_URL=ws://<TAILSCALE_IP>:18789|" packages/web/.env.local || echo "NEXT_PUBLIC_GATEWAY_URL=ws://<TAILSCALE_IP>:18789" >> packages/web/.env.localReplace <TAILSCALE_IP> with the actual IP from the command above.
Tell the user:
- Restart IronClaw:
pnpm start:all - On their phone: install Tailscale, sign into the same account
- Open
http://<TAILSCALE_IP>:3000in the browser - Log in with their password
Step 4: Verify Connectivity
Ask the user to confirm they can:
- Open
http://<TAILSCALE_IP>:3000from their phone - See the login page
- Log in successfully
- Send a chat message and receive a response
If the web app loads but WebSocket fails (connected indicator shows red):
- Check that
CORS_ALLOWED_ORIGINin.envmatcheshttp://<TAILSCALE_IP>:3000 - Check that
NEXT_PUBLIC_GATEWAY_TOKENinpackages/web/.env.localmatchesGATEWAY_WS_TOKENin.env
Step 5: Confirm
Show a summary:
- Tailscale IP:
<IP> - Web app URL:
http://<IP>:3000 - Gateway URL:
ws://<IP>:18789 - Authentication: enabled
Remind the user:
- Access is private to their Tailscale account — no one else can reach it
- Both devices must stay connected to Tailscale
- If the Tailscale IP changes, re-run
/add-remote-accessto update the config
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

