[ FROM THE BLOG ]
Small models, big repos: how Hearth reads code
Hearth does not send your whole project to the model. It builds a map and asks for the parts it needs.
Maren Voss
9 min
Engineering
Large projects do not fit in a single request, and sending everything would be slow and wasteful anyway. Hearth reads the way a person does: skim the outline, then open what matters.
The map
On first run Hearth builds a map of your repository: folders, files, the names inside them and how they import each other. The map is small and stays on your machine.
The read
For each task it picks the files the map suggests, reads them and adds more only if it needs to. You see every file it opens.
Large projects do not fit in a single request, and sending everything would be slow and wasteful anyway. Hearth reads the way a person does: skim the outline, then open what matters.
The map
On first run Hearth builds a map of your repository: folders, files, the names inside them and how they import each other. The map is small and stays on your machine.
The read
For each task it picks the files the map suggests, reads them and adds more only if it needs to. You see every file it opens.
