Platform / CLI & API
Product 03Run your existing workflows with your uncommitted changes.
Test your local, uncommitted changes on preloop before you push, for a much faster feedback loop.
Why it exists
Today you commit, push and wait to find out whether a change works. Running your changes before you commit means you find out sooner, and your history stays clean.
The mechanism, in the order a job meets it.
Install `plp` with Homebrew (`brew install preloopdev/tap/plp`) or the install script, then log in once with a device code. The CLI stores the token and talks to the hosted API from there.
`plp ci run` uploads your working tree, including uncommitted files, as a git bundle and starts the workflow on preloop's hosted runners.
`plp ci plan` shows the job DAG before you run it. `plp ci status` lists active and recent runs, and `plp ci logs` streams a job's output.
If a job pauses, attach with `plp ci debug` or connect an editor through `plp ci dap`. Retry from any step.
`plp ci migrate scan`, `plan`, `apply` and `verify` move a workflow from GitHub-hosted runners to preloop and open the pull request for you.
Each capability is part of the product today.
Sign in with a device code. Platform access tokens last at most 15 minutes, so a leaked token is a narrow window.
Every `plp ci` command calls the same hosted API the dashboard uses. Script anything you can click.
Set, get, scope and delete secrets at the run, environment, repository, organization or global tier, bound to a branch, workflow or job. `plp ci secrets` never prints a value back.
An org holds people under six roles: owner, admin, maintainer, developer, viewer and ci-agent. Agent principals get their own scoped, short-lived tokens.
`plp ci migrate` scans a repository, plans the move, opens a pull request with the rewritten runner label, and verifies the result.
Install the preloop GitHub App for an organization, then check its status or disconnect it from the CLI or the dashboard.
Sample / bash
# start a run; uploads the working tree, including uncommitted changes
plp ci run -f .github/workflows/ci.yml
# see the job DAG without running it
plp ci plan -f .github/workflows/ci.yml --json
# watch it
plp ci status
plp ci logs -f
# a paused job: attach, fix, retry from a step
plp ci debug --from 6
# move a workflow to preloop
plp ci migrate planThe CLI is a thin client: every command calls the same hosted API the dashboard uses.
brew install preloopdev/tap/plp, or curl -fsSL https://preloop.dev/install.sh | sh. Then run plp login.
People log in once with a device code. Automation sets PRELOOP_TOKEN instead and skips the interactive step.
No. Every job runs on preloop's hosted microVMs. The CLI only uploads your working tree and streams the result back.
plp ci run uploads a git bundle of your working tree, including uncommitted and untracked files, so the hosted run sees exactly what you have, not just what you pushed.
plp ci migrate scan finds what it can move, plan and apply rewrite the runner label and open a pull request, and verify confirms it.
Yes. An agent's token is the intersection of your grants and its own ceiling, capped at 15 minutes, and task grants bind it to one run or job at a time.
Start
We will set it up with you and show you what changes.