I open-sourced the start button I built for my own PC

Description and use

The author built a PWA that lets users start Claude Code sessions on their PC from a phone, preserving local configuration and using Tailscale for secure, firewall‑free access.

Problem

Remote coding sessions were limited to a single machine; hosted options ran in cloud sandboxes, losing local hooks, rules, and profiles.

Outcome

The solution allows users to start and stop Claude Code sessions on their PC from a phone while keeping local configuration intact, with secure, firewall‑free access via Tailscale.

Workflow

• Open the PWA on the phone and tap a project folder
• The PWA sends a request over HTTPS via Tailscale serve to the Node agent on the PC
• The Node agent (bound to 127.0.0.1) starts a new Claude Code window with --remote-control and the user profile
• The session runs until the user taps STOP on the PWA, which terminates the session

Evidence

The hosted options can start a session from a phone, but they run in a cloud sandbox on a copy of your repo. Everything I've built up locally, the hooks, the rules, the profile, stays behind.

Source

I open a small PWA on my phone and tap a project folder. A Claude Code session starts on the PC, in that folder, with my profile loaded and --remote-control on, so it shows up in the Claude app and I carry on there. STOP ends it.

Source

The agent is plain Node with zero runtime dependencies and binds only to 127.0.0.1. tailscale serve terminates TLS with a real certificate and forwards to it, so nothing is exposed to the internet and no firewall rule is needed.

Source

A launched session runs with your user account's full permissions, and every device on your tailnet can reach the agent. On a single-user tailnet that you control, that's a reasonable trade. On a shared one it isn't.

Source