Hearth is a coding agent that lives in your terminal. It reads your code, makes the change, runs your tests and opens the pull request. You read every line before it merges.
$
Northlight
parcelworks
Ledgerly
TIDEMARK
Fernbank
quarry/io
Olvane
Brightwell
Northlight
parcelworks
Ledgerly
TIDEMARK
Fernbank
quarry/io
Olvane
Brightwell
[ 01 · WHY HEARTH ]
Terminal speed, without the terminal guesswork.
every edit lands as a diff first

NEED NO EDITS
TEAMS EACH WEEK
USED FOR TRAINING
[ 02 · WHAT IT DOES ]
One prompt in the terminal. Five steps you can watch, stop or undo.
READ THE PRODUCT TOUR
01 READ
It reads like a person.
Outline first, then only the files that matter. Every file it opens is listed on screen.
02 PLAN
It says what it will do first.
A short plan in a plain Markdown file. Reorder it, cut a step or add a note before anything changes.
03 EDIT
Every edit is a diff.
Nothing is rewritten behind your back. Press esc and the last change is gone.
04 CHECK
It runs your tests, then tries again.
Your own test command, from your rules file. A red result sends it back to the plan.
05 SHIP
It opens the pull request.
With a description you would be glad to review. It replies to comments with fixes.
[ 03 · SLASH COMMANDS ]
(6)
Type a slash and pick one, or describe the job in plain words. Each one shows its work as it goes.
BUILT IN
6
YOUR OWN
UNLIMITED
MEDIAN RUN
11 MIN
UNDO
ESC
or write your own in a Markdown file

[ 05 · CONNECTIONS ]
One command per connection, each asking for the smallest permission that works.
ALL TEN CONNECTIONS
three more on the page

[ 06 · CUSTOMERS ]
Names and companies in this template are fictional.
PARCELWORKS · 40 ENGINEERS
review time per pull request, because the description arrives with the change
PRIYA NAIR · NORTHLIGHT
ACROSS 4,200 TEAMS
median from task to a reviewed pull request
RAVI MENON · CTO, QUARRY
MORE CUSTOMER STORIES
[ 07 · THE SESSION ]
review · total.ts
[ FIG. 6 ]
REVIEW
Hearth explains each edit where it made it. Reply in the margin, accept, reject or ask for another go.
permission
[ FIG. 7 ]
PERMISSIONS
The prompt names the exact command, where it runs and why. Your answer can be saved for the whole team.
press esc and it is gone


Your code stays yours
Only the files a task needs are sent to the model. Nothing is used for training.
Rules live in a file
hearth.toml lists what is allowed and what never is. Commit it and your team shares it.
Secrets are left out
Keys and tokens are recognised and removed before anything leaves your machine.
Your region, your data
Prompts are kept 30 days in the region you choose, then deleted.
[ 09 · PRICING ]
Change plans or cancel any time. No seat minimums, no sales call.
Free
$0
for personal projects
No card needed
Try Hearth on side projects and small repositories.
+
50 tasks each month
+
Balanced model level
+
All slash commands
+
Community support
CHOOSE PLAN
Pro
$20
per month
or $16 a month billed yearly
For people who use an agent every working day.
+
Unlimited tasks, fair use
+
Quick, balanced and deep levels
+
Resumable sessions
+
Email support in one day
CHOOSE PLAN
Team
$40
per person, per month
or $32 a month billed yearly
For teams that share rules, approvals and a bill.
+
Everything in Pro
+
Shared RULES.md and approvals
+
Usage reports by project
+
Priority support
CHOOSE PLAN
COMPARE EVERY PLAN
most teams start on Pro

[ 12 · HELP ]
Docs
Short pages with a command to try at the end of each.
EXAMPLE: HOW DO I LIMIT WHICH FILES IT CAN TOUCH?
OPEN THE DOCS
People
A person answers within one working day.
EXAMPLE: CAN WE TRY IT ON A TEAM OF TWENTY?
WRITE TO US
[ 13 · QUESTIONS ]
ASK SOMETHING ELSE
What is Hearth?
Which languages does it work with?
Do I have to use a particular editor?
What happens if it gets something wrong?
Is there a free plan?
Can I change plans or cancel?






