Skip to content

INSTALL.md

Latest commit

 

History

History
85 lines (63 loc) · 3.26 KB

INSTALL.md

File metadata and controls

85 lines (63 loc) · 3.26 KB
Raw

Installing

Two halves: the game on the console, and a pusher on your PC that knows your Claude usage. The game also runs without the PC half - you just play the synthetic PROTOCOL DRILL instead of your real numbers.

Before you start, check the console can run it at all: docs/COMPATIBILITY.md.

Shortest path — the PortMaster zip. Grab runnerprotocol-port.zip from the latest release, drop it into your device's ports/autoinstall/ folder (ArkOS: /roms/ports/autoinstall/, or /roms2/ports/autoinstall/ on dual-card setups), launch PortMaster once, restart EmulationStation, and Runner Protocol appears in the Ports menu. Press Y on the NO SIGNAL screen for the drill — no PC needed. The steps below are the manual install for everyone else.

1. Get the files onto the console

Over the network, if SSH is on (ArkOS: Options → Enable Remote Services), from the repo root:

scp -r device "ark@<console-ip>:/roms/tools/claude"
scp "device/Claude Runner.sh" "ark@<console-ip>:/roms/tools/"

(Windows users with the repo checked out: pc\deploy-runner.ps1 does exactly this, plus runs the test suite first.)

Or with the SD card in your PC: copy the device folder onto the card's ROMs partition as tools/claude, and device/Claude Runner.sh into tools/.

The launcher is self-locating: it finds runner.py next to itself or in a claude/ subfolder, so either layout works.

2. Put it on the carousel (optional, ArkOS-family)

Claude Runner.sh already appears in the Tools menu. For a proper carousel entry with its own logo and video snap:

cd /roms/runner-protocol   # wherever you copied the repo's install/ folder
sudo ./install-carousel.sh

It backs up es_systems.cfg, adds a RUNNER PROTOCOL system, installs theme logos, and restarts EmulationStation. uninstall-carousel.sh puts everything back. Re-running either is harmless.

3. Start the PC side

The game plays against your real Claude Code usage, which your PC pushes to the console:

pc\Start Usage Pusher.cmd      # Windows, double-click

Within a minute the NO SIGNAL screen clears and the live window appears. The pusher reads your own Claude session on your own machine; nothing leaves your network. See the repo README for how the link works and pc/hotspot-on.ps1 if the console joins the PC's hotspot.

No PC / just trying it out

On the NO SIGNAL screen, press Y: the PROTOCOL DRILL runs a full window - cold start, the band, critical, blackout, reset - on synthetic data, compressed into ninety seconds so you can feel the loop (and practice the EXTRACT timing) without burning five real hours. The header is badged PROTOCOL DRILL / SYNTHETIC the whole time; Y again ends it. --demo or RUNNER_DEMO=1 starts the game straight into the drill.

4. Exit, update, remove

  • Exit: hold SELECT+START.
  • Update: copy the new files over the old ones (or re-run deploy-runner.ps1). History survives updates.
  • Remove: sudo ./uninstall-carousel.sh for the carousel entry, then delete /roms/tools/claude and /roms/tools/Claude Runner.sh. Your history file is inside that folder - copy usage_hist.jsonl out first if you want to keep the record.