Developer tools
Give your agents full access to WarpBuild.
Agents read your CI runners, jobs, and spend, and turn build infrastructure into something you can ask questions about. Combine it with GitHub and an agent can explain a slow pipeline and what it costs you.
5,000 free credits to start.
Agent reach
WarpBuild API v1
The full surface, searched at run time.
Connect with
- API key
Event triggers
Not yet
Manual, schedule, and signed webhook are available.
What the agent can do
What agents do with WarpBuild
Helios searches the WarpBuild API v1 at run time. The agent finds the endpoint the task needs and calls it.
- Search WarpBuild's entire API surface at run time and call any endpoint your token allows.
- Read runner fleets, job history, queue times, and durations.
- Pull spend data and attribute it to repositories and workflows.
- Correlate CI runs with the GitHub pull requests that caused them.
- Analyze trends in the sandbox and publish a report to Slack or a sheet.
- Alert when queue times or spend cross the thresholds you name.
Examples
Tasks you can hand to a WarpBuild agent
Report on CI spend every week
The agent attributes build spend to the repositories and workflows driving it, and shows what changed since last week.
Weekly, report CI spend by repo and workflow with week-over-week change.
- warpbuild·pull last week's job and spend data
- code·attribute spend by repo and workflow
- slack·post report to #platform
CI spend · week of Mar 3
- $3,140 total · up 12% week over week
- `api` integration tests drove 41% of spend
- One workflow doubled after a matrix change
Find the slow jobs
The agent ranks jobs by duration and queue time, correlates them with recent changes, and names the ones worth fixing first.
Find the slowest CI jobs and what made them slow.
- warpbuild·list jobs by p95 duration
- github·find the PRs that changed those workflows
- code·correlate duration with change dates
3 jobs worth fixing
- `e2e` p95 rose from 8m to 19m after #2790
- `lint` spends 60% of its time on install
- `build-matrix` queues 4m before it starts
Alert on a spend spike
A daily agent checks yesterday's spend against the trend and speaks up only when something is genuinely off.
Daily, alert if CI spend exceeds the 14-day trend by more than 30%.
- warpbuild·pull spend for the last 14 days
- code·compare yesterday against the trend
- slack·alert #platform with the top contributors
Spend spike detected
- Yesterday $780 against a $520 trend
- Driven by 61 reruns of `e2e` on one branch
Explain CI health to the team
The agent turns runner data into a readable picture of how CI is treating engineers: queue times, flakes, and where time goes.
Every Friday, summarize CI health for the engineering team.
- warpbuild·aggregate queue times and outcomes
- github·count reruns per workflow
- slack·post to #engineering
CI health · week of Mar 3
- Median queue 22s · p95 3m 10s
- Pass rate 94%, down from 97%
- `e2e` accounts for most reruns
Triggers
How a WarpBuild workflow starts
WarpBuild does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook.
Manual
Run it from the app with an optional JSON payload. Every workflow supports this.
Schedule
A cron expression or a plain sentence such as every weekday at 9am. Times are UTC.
Signed webhook
A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes.
Works with
WarpBuild works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
FAQ
Questions, answered
Put an agent on WarpBuild.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.