Local workflows. Shared purpose.

Good work starts
close to home.

Your GitHub Actions. Your machine. Bellows runs the workflows; Kiln supplies the runner. Stoke brings them together.

Set up your workspace See the workflow

Two independent tools · One shared workflow

Bellows / orchestration Kiln / environment
STOKE / the local feedback loop
A little feedback, before the push.Sample workflow
$ bellows doctor ✓ act available ✓ Docker daemon reachable ✓ Runner mapping configured Environment: ghcr.io/smeltery/kiln Ready to preview your workflow.
Illustrative output · no workflow connected
THE SAME WORKFLOWS. A CLOSER FEEDBACK LOOP.BUILT FOR THE WORK.
01 / Before the push

A short path
back to the work.

Keep the workflows you already have. Check compatibility, preview the plan, and run supported jobs locally before they reach hosted CI.

01 / CHECK

Know what will run

Bellows diagnoses dependencies and runner mappings. Preview jobs and estimates before starting a container.

02 / RUN

A place for the workflow

Kiln gives act a Wolfi-based environment with glibc, Node.js, Python and common build tools, on AMD64 and ARM64.

03 / ITERATE

Keep the feedback close

Catch supported workflow failures on your machine. Keep hosted checks for platform coverage and merge enforcement.

02 / The working pair

A little heat.
A shared purpose.

One command assembles the workspace. Each tool keeps its own source, releases and responsibility.

StokeAssemble the workspace BellowsPlan and run the workflow KilnSupply the environment
03 / Good to know

A few practical
details.

A shared home, clear responsibilities, and documentation for the parts that matter.

Does Stoke replace Bellows or act?

Stoke assembles the source repositories and shared documentation. Bellows orchestrates workflows using act and Docker; Kiln supplies the runner image. Setup does not install the CLI or start Docker.

Is Kiln an Ubuntu runner?

Kiln runs Wolfi Linux with glibc and uses apk. Ubuntu-style tags are compatibility aliases. Workflows requiring apt, systemd or a complete hosted VM need adaptation.

Will updates overwrite my work?

Stoke skips dirty checkouts, feature branches and detached HEADs. Clean main branches update with fast-forward-only pulls. It never stashes, resets or switches branches.

Can I keep my hosted CI?

Yes. Local feedback complements hosted checks. Keep hosted CI for native platform behavior, GitHub integration and required merge checks. A Linux container does not emulate macOS.

04 / Bring it home

Ready for
the next run.

Clone the workspace, then follow the getting-started guide to install Docker, act and Bellows.

TERMINAL / ASSEMBLE THE WORKSPACE
git clone https://github.com/smeltery/stoke.git
cd stoke
bash scripts/fleet.sh setup