[ PRODUCT ]

One command that finishes the task.

Hearth reads your code, plans the change, edits, runs your tests and opens the pull request. Here is what happens at each step, and where you stay in control.

INSTALL HEARTH

SEE PRICING

01 READ

It reads like a person: outline first, then the files that matter.

Hearth builds a small map of your repository on your machine, opens only the files a task needs, and shows you each one.

✓

Shows every file it opens

✓

Skips folders you list as private

✓

Remembers the map between tasks

~/shop-api

❯ fix the failing checkout test

● map: 3,418 files, 212 folders

◆ Read src/cart/total.ts

◆ Read tests/checkout.test.ts

● opened 2 of 3,418 files

~/shop-api

❯ fix the failing checkout test

● map: 3,418 files, 212 folders

◆ Read src/cart/total.ts

◆ Read tests/checkout.test.ts

● opened 2 of 3,418 files

~/shop-api

❯ fix the failing checkout test

● map: 3,418 files, 212 folders

◆ Read src/cart/total.ts

◆ Read tests/checkout.test.ts

● opened 2 of 3,418 files

~/shop-api

plan.md

1. Move rounding to after tax

2. Update the two affected tests

3. Run the checkout suite

⏎ run step 1 e edit plan

~/shop-api

plan.md

1. Move rounding to after tax

2. Update the two affected tests

3. Run the checkout suite

⏎ run step 1 e edit plan

~/shop-api

plan.md

1. Move rounding to after tax

2. Update the two affected tests

3. Run the checkout suite

⏎ run step 1 e edit plan

02 PLAN

It says what it will do before it does it.

For anything bigger than a one-line fix, Hearth writes a short plan you can edit. Reorder it, delete a step, add a note.

✓

Plans are plain Markdown files

✓

Edit the plan, then press enter

✓

Each step is ticked off as it finishes

03 EDIT

Every edit is a diff. Undo is one key.

Nothing is rewritten silently. Changes appear as a diff, file by file, and esc undoes the last one as a normal change in your history.

✓

Diffs use the full width of your terminal

✓

Comments land on the exact line

✓

Undo never touches your other work

~/shop-api

src/cart/total.ts +2 −1

− const lines = items.map(i => Math.round(i.price * i.qty))

+ const lines = items.map(i => i.price * i.qty)

+ return Math.round(sum(lines) * (1 + taxRate))

esc undo a accept r reject

~/shop-api

src/cart/total.ts +2 −1

− const lines = items.map(i => Math.round(i.price * i.qty))

+ const lines = items.map(i => i.price * i.qty)

+ return Math.round(sum(lines) * (1 + taxRate))

esc undo a accept r reject

~/shop-api

src/cart/total.ts +2 −1

− const lines = items.map(i => Math.round(i.price * i.qty))

+ const lines = items.map(i => i.price * i.qty)

+ return Math.round(sum(lines) * (1 + taxRate))

esc undo a accept r reject

~/shop-api

◆ Run make test

FAIL checkout rounds once

● adjusting: tax read from settings

◆ Run make test

✓ 42 passed

~/shop-api

◆ Run make test

FAIL checkout rounds once

● adjusting: tax read from settings

◆ Run make test

✓ 42 passed

~/shop-api

◆ Run make test

FAIL checkout rounds once

● adjusting: tax read from settings

◆ Run make test

✓ 42 passed

04 CHECK

It runs your tests, reads the result, and tries again.

Hearth uses the test command from your rules file. A red result sends it back to the plan with the failure in front of it.

✓

Uses your own test command

✓

Stops after three tries and asks you

✓

Never edits a test just to make it pass

05 SHIP

It opens the pull request and explains it.

The description says what changed, why, and which checks passed. When a reviewer replies, Hearth reads the comment and answers with a fix.

✓

Branch names follow your rules

✓

Descriptions you would be happy to read

✓

Replies to each review comment

~/shop-api

/ship

● checks: lint, types, tests

✓ all green

✓ branch fix/cart-rounding

✓ opened pull request #318

~/shop-api

/ship

● checks: lint, types, tests

✓ all green

✓ branch fix/cart-rounding

✓ opened pull request #318

~/shop-api

/ship

● checks: lint, types, tests

✓ all green

✓ branch fix/cart-rounding

✓ opened pull request #318

The same job, two ways.

By hand

With Hearth

Find the cause of a failing test

Read logs, guess, add prints

Reads the trace and names the line

Write the fix

Type it, run tests, repeat

Proposes the smallest diff

Explain the change

Write it up afterwards

Description written with the change

Get a review

Wait for someone to open it

Pull request opened for you

Undo a bad idea

Remember what you changed

Press esc

[ START ]

Start a session in your terminal.

curl -fsSL get.hearth.example | sh

COPY

INSTALL HEARTH

[I]

SEE PRICING