Buildkite StrawberryThe build work, done and queued for one look
Your Buildkite, worked while you do something else: 13 reads to go through it, 1 write to change it, and a card in front of every one of those changes.
Open the build. Check it against something else. Write the change. Move to the next one. That is the Buildkite afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a build until you approve it.
What it can do is exactly what Buildkite exposes to an account you authorise and nothing beyond it: 14 operations, 13 reads and 1 write. In practice that means it can create a build, and work across the builds, access tokens and artifacts.
The Buildkite API stops at Buildkite. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the builds or ask you for them?
13 of the 14 operations are reads.
Your account, not a guess at it: a companion can retry job, rebuild build and list pipelines, and the full list below is the whole list, with nothing inferred from Buildkite's documentation.
The builds are what most of this inventory is about, alongside the access tokens. A companion can hold all 14 of these operations and forty open tabs in the same pass, which is how an afternoon of Buildkite admin becomes a queue you review.
- Retry Job
- Rebuild Build
- List Pipelines
- List Organizations
- List Builds for Pipeline
- List Build Artifacts
- List Build Annotations
- Get Current User
- Get Job Log
- Get Job Environment Variables
- Get Build
- Get Access Token
- Download Artifact
Which builds wait for your approval?
The one write operation there is waits for you.
A companion can create a build, and each one is staged on an approval card first: you see the build, the field and the new value before it lands in Buildkite.
Nothing in Buildkite is sent, changed or deleted on your behalf without that click, and a rejected card leaves the build exactly as it was. The gate is the same one on every surface, described at security.
- Create Build
Does the build sweep have to be asked for every time?
Yes.
Saved as a routine, the Buildkite builds pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Buildkite builds sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents