Installation
Get sling on your machine, sign in, and verify your setup
Installation Prompt
Paste this prompt into your coding agent:
Install the Sling CLI on this machine.
1. Check whether `sling` is already installed. If it is, show me `sling --version` and do not reinstall it.
2. Confirm this machine is supported: Apple Silicon macOS or x64 glibc Linux. If it is not, stop and explain that the CLI cannot be installed here.
3. Before making changes, show me the official installer command and ask for approval. Once I approve, run:
curl -fsSL https://runners.starsling.dev/cli/install.sh | sh
4. Follow any PATH instructions printed by the installer, then verify both `command -v sling` and `sling --version` succeed.
5. Determine whether your environment and my terminal share the same machine and user account. If they do, give me a login command that works in my terminal—use the absolute path returned by `command -v sling`, or include the installer's PATH update—then ask me to run it and complete the GitHub browser approval. Wait for me to confirm. If you run on a separate host or in a container whose credentials my terminal cannot share, run `sling login` in your environment, relay its device code and approval URL to me, and wait for me to approve it. Do not attempt to approve the login for me.
6. Run `sling whoami` and `sling doctor`. Report the identity, organization, and every doctor result, including advisory checks.
Do not claim the installation is complete unless the binary works and the authentication checks finish successfully. If a step fails, explain the exact failure and the next action instead of skipping it.Install manually
On Apple Silicon macOS and x64 glibc Linux:
curl -fsSL https://runners.starsling.dev/cli/install.sh | shThe installer detects your platform, downloads the matching build, verifies its SHA-256 digest, and activates it. If ~/.local/bin is not on your PATH, the installer prints the export line to add.
It supports Apple Silicon macOS and x64 glibc Linux.
Check the install:
sling --versionTo upgrade, rerun the same command.
Get 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, auto-update state, org resolution, whether the sling agent skill is installed for a coding agent, and whether Python 3.9+, PyYAML, and gh are available for sling speedup. Exit 0 means healthy; exit 10 means a real check failed. A row marked ! is an advisory — a newer CLI, a coding agent without the skill, or a missing speedup prerequisite — and still counts as healthy; ○ marks a check that could not run. The speedup row checks that gh is installed, not that it is signed in.
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 → https://github.com/acme/api.git
✓ patch_tooling git found (/usr/bin/git)
✓ version up to date (0.1.129)
✓ auto_update on; last checked 2026-08-04 17:00 UTC: sling is up to date (0.1.129).
✓ org starslingdev (paid)
✓ agent_skill sling skill installed for Claude Code
✓ speedup Python 3.9+, PyYAML and gh available for sling speedup
Environment healthy!