igneum/relay/clients/CLAUDE-PC.md
igneum-labs 53f7f55796 Relay: text, files and runnable tasks between the Mac, the PCs and the phone (relay.igneum.network)
New Vercel project igneum-relay from relay/: one function (api/relay.mjs) over Neon tables relay_items and relay_machines,
files in Vercel Blob store igneum-relay (50 MB client uploads, 4 MB through the function), phone-first web page at /r/<token>/
with the site tokens. Mac CLI tools/relay.mjs (feed, read, drop, task, run, watch, inbox, machines, role, name).
Windows clients send.bat/send.ps1 and the igneum-agent (registers hostname, role, GPUs, WSL, nvcc; runs queued PowerShell
scripts, posts results, reboot-continue via scheduled task + RunOnce), bash twins send.sh and agent.sh (verified live),
playbooks for WSL setup, prover setup, prove-block, miner v4, one-click placeholder. make-clients.sh bakes the secrets
into a zip; the repo copies hold placeholders. Screenshots under docs/design/relay.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-04 10:04:30 +00:00

2.5 KiB

Igneum relay: standing instruction for the Claude Code session on this PC

the project lead's Mac and this PC talk through the Igneum relay (relay.igneum.network). You never need Gmail, a USB stick or the project lead to carry text or files. The relay clients live next to this file (the folder you unzipped igneum-relay-clients.zip into). Everything below runs in cmd or PowerShell from that folder.

Four commands

You want to Type
See what the Mac has queued for you (and mark it read) send.bat inbox
Report back (what you did, what broke, the numbers) send.bat result "<text>"
Send a file (log, screenshot, zip, up to 50 MB) send.bat <path>
Fetch an item or its file by id send.bat get <id>

Also: send.bat "<text>" posts a plain note, send.bat peek reads without marking, send.bat done <id> closes a task. Add -TaskId <id> to a result so it links to the task it answers, -Title "..." for a headline, -To Mac to address one machine.

The loop you follow

  1. At the start of every session, and whenever the project lead says "check the relay": run send.bat inbox. Each item is a task from the Mac: a title, a body, sometimes a file. Do what it says.
  2. When a task is done or blocked: send.bat result "<what happened, exit codes, paths, the numbers>" -TaskId <id>. Keep it factual. Attach logs with send.bat <logfile> -TaskId <id> rather than pasting hundreds of lines.
  3. Close it: send.bat done <id>.
  4. Nothing waiting? Say so and carry on with what the project lead asked for locally.

The agent

igneum-agent.bat is a separate, automatic runner. the project lead double-clicks it once (it asks for administrator rights once) and leaves the window open. From then on the Mac queues scripts (run tasks) that the agent executes by itself, posts the output as result items and reboots the PC when a script asks for it. Do not stop that window. Do not run run tasks yourself; send.bat inbox only shows the task items meant for you. If the agent window is closed, tell the project lead and ask him to start igneum-agent.bat again.

Rules

  • The URL, key and token baked into send.ps1 and igneum-agent.ps1 are the secret. Never paste them into chat, a commit, a screenshot or another machine.
  • Never edit send.ps1 or igneum-agent.ps1. If they break, report it with send.bat result and the project lead ships a new zip.
  • Copy law applies to results too: short sentences, numbers in tables, no em dashes.