Installation
Get the binary on your PATH, sign in, and verify your setup
sling is in private beta and is served as a binary. Get in touch if you would like to get access.
It is self-contained, with no runtime or dependencies. Drop it on your PATH and run it.
sling --versionGet Started
Authenticate
sling loginThis runs the GitHub device-code flow: it opens an approval page, waits for you to confirm the device code, saves the session token to ~/.config/sling/credentials, and links your default organization.
The credential is stored per user, not per shell, with owner-only permissions. So an AI agent running on the same machine as you inherits it: once you have signed in, the agent can run any sling command with no further setup. See Configuration for how that differs in CI.
Check your identity
sling whoamiReports your identity, org, plan, token scopes, and token expiry, so you can see exactly what the credential you just saved can reach.
Verify
sling doctordoctor checks your token, the control plane's reachability, clock skew, git remote, patch tooling, version, and org resolution. Exit 0 means healthy; exit 10 means a real check failed.
sling doctor
✓ token valid session (expires 4 Aug 2026, 17:45)
✓ control_plane reachable (https://runners.starsling.dev)
✓ clock_skew 0s vs server
✓ git_remote origin
✓ patch_tooling git found (/usr/bin/git)
✓ version on 0.1.0
✓ org starslingdev (paid)
Environment healthy!