Quick Start

Host a script on Runny.sh and fetch it with a one-liner. We host the bytes. Your runtime executes them.

Three steps

Create a script. Sign in, open New script, paste the file, pick a runtime, and save.
Copy the raw URL. Every script gets an unguessable 12-character slug and a stable https://runny.sh/r/{slug} endpoint.
Fetch and run it locally. Open the script’s share page, review the bytes, then pipe them to the runtime on your machine. Runny never executes the script.

The one-liner contract

Every script has a stable raw endpoint. Fetch it from a shell, pipe it to the runtime you reviewed, and keep the path simple.

Bash

curl -fsSL https://runny.sh/r/{slug} | bash

Bash

curl -fsSL https://runny.sh/r/{slug} | python3

Bash

curl -fsSL https://runny.sh/r/{slug} | node

/r/{slug} returns text/plain; charset=utf-8 with X-Content-Type-Options: nosniff, Cache-Control: private, no-store, and a restrictive Content-Security-Policy. It never sets a session cookie.

Windows

In Windows PowerShell, curl is often an alias for Invoke-WebRequest. That alias rejects -fsSL. Call curl.exe instead.

PowerShell

curl.exe -fsSL https://runny.sh/r/{slug} | pwsh

See PowerShell for 5.1 vs 7+ and a native Invoke-WebRequest form.

Private scripts

Private scripts need a fetch token on the raw request, not a login session. Prefer a header so the token stays out of shell history and access logs.

Bash

curl -fsSL -H "Authorization: Bearer TOKEN" https://runny.sh/r/{slug} | bash