Sign the Claude CLI in as the jarvis service account on home1
Claude Code is the engineering worker. Its sign-in is an interactive OAuth device flow: it prints a URL, waits for a browser, and writes the credential itself. Nothing headless can complete it, and until it is done home1 can be dispatched planning work but no code.
Blocks: All engineering dispatch to home1. The node will onboard, heartbeat and advertise capacity without it — and every coding task will still land on VIN's single slot.
Run this
ssh root@uk-james-home1.tail99ba7.ts.net sudo -u jarvis -H npm install -g @anthropic-ai/claude-code # only if `sudo -u jarvis -H command -v claude` is empty sudo -u jarvis -H claude # then, at the prompt: /login — it prints a URL, open it, approve, come back
Values you will be asked for
- Account
-
jkkec23@gmail.comThe same account the CLIs on home1 already use under the 'james' user. Using a different one is fine, but write down which. - Verify
-
sudo -u jarvis -H test -f /home/jarvis/.claude.json && echo signed-in - Then
-
sudo /opt/jarvisos/bin/jarvisos-bootstrap.sh advertiseRe-advertises immediately; this card clears on the next heartbeat.
Open https://claude.ai/login
Onboarding detail →
Clears itself when home1 advertises
worker-claude.
All declared entities are operational
20 entities reporting. Recovery readiness 40%.
Nodes
Physical and virtual hosts.Home1
No heartbeat has ever been received from this entity.
VIN / VPS
No heartbeat has ever been received from this entity.
VPS1 / de-james-vps1
No heartbeat has ever been received from this entity.
NAS
No heartbeat has ever been received from this entity.
GWSCLI / S3
No heartbeat has ever been received from this entity.