What happens on this machine
- Run the bootstrap
.cmd— installs the prerequisites and Claude Code. - Download and unpack the setup bundle.
- Open Claude Code, paste the handoff prompt. It measures, plans, then fixes.
- Inject the secrets capsule when it asks (if one is armed).
- Send the parity report back here so the result is on record.
i Published payload
Loading…
📡 Bridge-only setup no Claude · no bundle
Just needs this machine reachable from DL for scripts and automation — nothing more? Use this instead of steps 1–5 below. It installs Tailscale, has you sign in, then turns on inbound SSH. No Claude Code, no Git/Node, no laptop-setup bundle.
Generate it as single-use with a short expiry — it's spent the moment Rakesh's machine joins, or the moment it expires, whichever is first. Never reuse the same key for a second machine.
Opens the guide in a new tab — it walks through every step. If you pasted
a key above, both the guide's own download and this page's are pre-loaded with it, so
Rakesh's copy joins automatically; otherwise he signs in himself (never with your password
— the guide covers that). Download the other two into the same folder, then right-click
bridge-setup.cmd and Run as administrator.
The guide's own copy of the cmd/script downloads works standalone once forwarded — you don't need to be signed in here for that part.
1 Bootstrap this machine
Downloads BOOTSTRAP-THIS-MACHINE.cmd. Right-click it and
Run as administrator. It installs Git, Node, Python and Claude Code, then stops and tells
you what to do next. Safe to re-run.
2 Download the backup
The full laptop-setup bundle — skills, memory, MCP
installers, tools, the dependency verifier and its DL baseline. The bootstrap unpacks it to
%USERPROFILE%\laptop-setup.
3 Handoff prompt
After Claude Code is installed, open it in the bundle folder and paste this. It measures first, plans, then runs to completion — and stops only for a login ceremony.
4 Secrets capsule checking
Checking capsule state…
5 Parity report
On the target machine run
verify-dependencies.ps1 -Json out.json -Baseline baseline-DL.json
(Claude does this for you), then drop out.json here so the result is
recorded against this machine.
Fleet
Machines running the outbound beacon — DL, DL2 and Dev-PC — report in on their own schedule. Read-only: nothing here can arm or push anything to a machine.
The button does not push anything to DL — the VPS cannot reach DL directly. It only asks DL's own beacon to notice and run a publish on its next check-in.