The Hearth glass pages

[ FROM THE BLOG ]

Running Hearth in CI without breaking the build

A checklist for the first month of using an agent in your pipeline.

Tobias Reyes

8 min

Guides

An agent in CI is different from an agent in your terminal: nobody is there to say yes. That changes how you set it up.

Start read-only

For the first week let it comment and never push. Read what it would have done.

Write the rules down

Everything Hearth may do in CI must be in hearth.toml. If it is not there, the step fails with a clear message.

Give it one job per step

Fix formatting. Update snapshots. Write the changelog line. Small jobs are easy to trust and easy to switch off.

[ START ]

Start a session in your terminal.

Start a session in your terminal.

Start a session in your terminal.

$

curl -fsSL get.hearth.example | sh

curl -fsSL get.hearth.example | sh

COPY

Hearth logo

hearth

A coding agent that lives in your terminal. It does the work, you read the diff.

$

curl -fsSL get.hearth.example | sh

curl -fsSL get.hearth.example | sh

COPY

© 2026 HEARTH LABS · A FICTIONAL PRODUCT FOR THE CODEMAXX TEMPLATE

MADE FOR TERMINALS. REVIEWED BY PEOPLE.

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

hearth

Create a free website with Framer, the website builder loved by startups, designers and agencies.