Launch HN: StarSling (YC P25) – Self-improving CI for agent-volume repos
discuss
- Points66
- Comments37
discuss
We’re Yonas and Daniel and we’re building StarSling (https://starsling.dev), fast GitHub Actions runners with AI agents that ship PRs to continuously improve your tests and workflows. Every CI job gets its own ephemeral sandbox on the fastest Zen 5 machines and NVMe Disk with unlimited concurrency so a burst of agent PRs all run at once. We’re different from other runners because ours come with agents that cut down your CI bill over time. PRs are generated through our CI harness, which runs an…
Story details from Hacker News ↗ · linked article on starsling.dev.
Launch HN: StarSling (YC P25) – Self-improving CI for agent-volume repos was first seen on Hacker News · Front page on Nov 17, 2026. Since then it has appeared in 74 checks on 2 different days. Its best position was #7 of 30, reached on Nov 17, 19:28 UTC. It dropped off the list after Nov 18, 14:43 UTC.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Hacker News.
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
We should probably be measuring deployable merges to main. The math just doesn't work for pipeline based CI as you add more agents. Three things matter. 1 -- How many non-conflicting changes can actually be made at one time (Fan Out) 2 -- How long a critical path takes 3 -- How many times you have to run that…
Bereket from Better Auth - we've been on StarSling for about a year now, it's been such a hard a problem for us ot solve CI to the amount of PRs we get and continues need of optimization and faster runners, im so bullish!
So the agent compares the changed workflow with the existing one and judges whether the speedup is significant. But a change that re-shards or skips tests would always look like a win on speed alone, wouldn't it? How do you check that such changes still catch the bugs the old workflow caught? I had the same worry…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 18, 14:43 UTC, after 2 days of trending.
#7 on Hacker News · Front page, on Nov 17, 19:28 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Nov 17, 2026 and has been on the list on 2 days (74 checks) since.
66 points and 37 comments; submitted by yonasb on Nov 17, 2026.