01 · Origin event
Early-access support connects the StarSling app to an Origin repository. Push and pull request webhooks start the matching workflow.
Cursor Origin CI · Early access
Agentic CI for Cursor Origin
Get early access to StarSling CI: GitHub Actions-style workflows on fast, isolated compute, with native checks in Cursor Origin pull requests
Cursor Origin
Pull request openedStarSling CI
Workflow dispatchedOrigin check
Passed02 · Workflow and compute
StarSling reads familiar GitHub Actions-style workflow syntax and schedules each job on fast, isolated runners.
03 · Native feedback
Build, test, and lint results are published to the Origin pull request, where they can be used as required checks.
Cursor Origin CI, end to end
Run GitHub Actions-style CI on Cursor Origin
Familiar workflow syntax
Bring your existing GitHub Actions workflows with you. StarSling CI is built around familiar YAML, actions, jobs, and steps instead of another CI language.
Built for Cursor Origin
Origin pushes and pull requests trigger StarSling CI directly. No GitHub round trip is required for repositories hosted on Origin.
Fast, isolated compute
Jobs run on StarSling's high-performance runner infrastructure, isolated from other teams and ready for demanding build and test workloads.
Native Origin checks
Build, test, and lint results return to Cursor Origin pull requests, where teams can see status and use CI as a required check.
Agent-native CI, familiar workflows
Move from GitHub to Cursor Origin without rebuilding CI
Moving code hosting to Cursor Origin should not mean rebuilding CI from zero. StarSling CI is built to carry familiar GitHub Actions-style workflows into Origin, with compatibility reviewed as part of early access.
Measured on StarSling's GitHub Actions runners
Cursor Origin CI
Be the first to get fast CI in Cursor Origin
Signup to get notified as soon as StarSling CI for Cursor Origin is ready.