Overview
The agent-first CLI for StarSling
sling is the primary interface to the StarSling platform for agents and humans. The questions you ask most often are each a single command: why a job failed, where the time went, and what sits at the top of your spend.
sling time
Job Name: Lint, typecheck, test & spell · Wall-Clock: 58s · Queue-Wait: 2s
PHASES TIME %-SHARE TIMELINE
provision 4.0s 7.14% ██░░░░░░░░░░░░░░░░░░░░░░
checkout+patch 2.0s 3.57% ░░█░░░░░░░░░░░░░░░░░░░░░
steps 46.0s 82.14% ░░░███████████████████░░
Set up Bun 1.0s ░░░█░░░░░░░░░░░░░░░░░░░░
Set up mise tools 2.0s ░░░█░░░░░░░░░░░░░░░░░░░░
Install dependencies 1.0s ░░░░█░░░░░░░░░░░░░░░░░░░
Lint (Biome) 2.0s ░░░░█░░░░░░░░░░░░░░░░░░░
Lint shell (shellcheck) 14.0s ░░░░░██████░░░░░░░░░░░░░
Lint Dockerfiles (hadolint) 0.0s ░░░░░░░░░░░█░░░░░░░░░░░░
▸ Typecheck 18.0s ░░░░░░░░░░░████████░░░░░
Test 7.0s ░░░░░░░░░░░░░░░░░░░███░░
Catalog drift 1.0s ░░░░░░░░░░░░░░░░░░░░░░█░
Spell (typos) 0.0s ░░░░░░░░░░░░░░░░░░░░░░█░
teardown 4.0s 7.14% ░░░░░░░░░░░░░░░░░░░░░░██Install
On Apple Silicon macOS and x64 glibc Linux:
curl -fsSL https://runners.starsling.dev/cli/install.sh | shThen sign in and confirm the install:
sling login
sling --versionsling login runs the GitHub device-code flow and saves your session per user, not per shell — so an agent running on the same machine inherits it with no further setup.
For PATH setup, upgrades, digest verification, and sling doctor, see Installation.
What you can do with it
sling whyclassifies why a job failed, with evidence and a fix to run.sling logsfilters server-side, returning only the logs that matter.sling timedecomposes where the time went, phase by phase.sling topranks what sits at the top of your spend.sling usageattributes runner minutes and cost, grouped how you ask.sling billis a read-only budget check for the open period.
Authentication and setup
login, logout, whoami, doctor, and picking a default org.
Inspecting CI
resolve, runs, jobs, and server-side filtered logs.
Analyzing CI
usage, top, time, why, and the runner-label catalog.
Billing
Read-only budget snapshots and prior invoices.
Why it exists
AI agents working inside CI jobs on StarSling runners, and the humans supervising them, have no first-class way to answer the questions CI work actually consists of: why did this job fail, where does the wall-clock go, what is burning our runner minutes, show me the logs that matter.
Those answers otherwise live behind the GitHub UI (hostile to agents), raw APIs (no diagnosis, no aggregation), and dashboards (exports, not interfaces). Agents end up screen-scraping logs into their context windows, guessing at failure causes, and unable to branch on outcomes without parsing prose. Humans get no leverage from the telemetry StarSling already collects.