Side document

At the cabin Beelink — what to do

Giving that machine its own identity, then starting the single session
plain text, ready to paste

Six steps. The first one is the one that bites if skipped. Everything runs in PowerShell on the Beelink.

Step 1 — do not skip

Sync before anything else

powershell ~\claude-env\sync.ps1

This pulls down tonight's rules, memory and the corrected /close command. Starting work without it means working from stale rules and pushing them back over the good ones.

Step 2

Give the Beelink its own key

Right now several machines share one key, so the server cannot tell which machine did what. This gives the Beelink its own labelled identity. Press Enter at the passphrase prompt.

ssh-keygen -t ed25519 -C "beelink-cabin" -f $HOME\.ssh\id_ed25519_beelink
Step 3

Install it on the server

This uses the access the machine already has to add the new key alongside the old one. Nothing is removed, so there is no way to lock yourself out here.

$pub = Get-Content $HOME\.ssh\id_ed25519_beelink.pub
ssh root@143.198.182.180 "echo '$pub' >> /root/.ssh/authorized_keys"
Step 4

Tell SSH to use the new key for that server

Add-Content $HOME\.ssh\config @"

Host 143.198.182.180
  User root
  IdentityFile ~/.ssh/id_ed25519_beelink
  IdentitiesOnly yes
"@
Step 5

Prove it worked

The first command should print the server name. The second should show beelink-cabin as the key that just logged in — that is the whole point, the server can finally name the machine.

ssh root@143.198.182.180 "hostname"
ssh root@143.198.182.180 "tail -3 /var/log/auth.log | grep Accepted"

If step 5 fails, nothing is broken — the old shared key still works. Remove the block added in step 4 and you are back where you started.

Step 6

Start the one session

claude --resume 2196701d-5c4b-4a6e-8089-c0f39e56f65b

Then open the tabs you need — one for AME development, one for the Tuesday material. Same session, both people able to see it, from the machine or a phone.

What not to do yet

Do not remove the shared key

The old key paulwalhus@wholetech is still doing the automation — cron jobs, backups, deploys — and other machines still use it. It comes out only once every machine that needs access has its own labelled key. Removing it now takes the server offline for everything.

Where things already stand