Axiom StudioAXIOMSTUDIO
All docs

Cloud Runners

Cloud Runners let you launch VibeFlow agents in the cloud instead of running an agent process on your own machine. Each runner is a hosted pod that clones your repository and runs the VibeFlow CLI, so agents can pick up work, implement it, and commit — without keeping a laptop or CI worker online.

Cloud Runners are managed per project, from the project's Cloud Runners tab.

Availability

Cloud Runners are gated behind the feature_cloud_runners feature flag and are off by default. An operator enables them globally or per organization for a controlled rollout.

Note: If you don't see a Cloud Runners tab on your projects, the feature hasn't been enabled for your organization yet. Ask your operator/admin to enable feature_cloud_runners.

Using the Cloud Runners Tab

Open a project and select the Cloud Runners tab. You'll see the runners for that project, each showing its name, current status, and pod. Status refreshes automatically (about every 5 seconds) while the tab is open.

Creating a Runner

Start the create wizard from the Cloud Runners tab and provide:

  • A name — a recognizable label for the runner.
  • A git provider — the provider the runner uses to clone your repository (see Git Providers below).

When you launch it, the runner starts up, clones your repository using the selected git provider, and connects back to VibeFlow so it can pick up work for the project.

Managing Runners

Each runner has actions:

  • Start — bring up a stopped runner.
  • Stop — pause a running runner (it stays around so you can start it again later).
  • Delete — permanently remove the runner. This cannot be undone, so it asks for confirmation.

You can also select multiple runners and Start, Stop, or Delete them together from the bulk action bar.

Typical status values are Pending, Starting, Running / Active, Stopping, Stopped, and Failed.

Git Providers

Runners clone your repositories using a git provider that you add, which keeps repository credentials scoped to you.

  • Add a provider with either a personal access token (PAT) or an SSH key.
  • You only ever see and use your own providers — other users' providers are never shown to you.
  • Your git credentials are stored securely on the runner backend; VibeFlow keeps only a reference to the provider, never the secret itself.

Providers are reusable across runners, so you typically add one per repository host and reuse it.

Permissions

  • View runners — any member of the project's organization.
  • Start / Stop / Delete / manage a runner — the runner's owner or an organization admin. Trying to manage a runner you don't own returns a permission error.

Notes & Limitations

  • Runner status is served from VibeFlow's own records and refreshed periodically by a background reconciler. If status stops refreshing, runner actions still work.
  • Stale pending / failed runners are cleaned up automatically after about 30 minutes.
  • Per-organization runner quotas and rate limits are not enforced in this release.