# Your fixes, remembered. Your agent, caught up.

Earlyn keeps the errors you hit in a terminal, an editor or a local page together with what fixed them, and hands your coding agent the context of a project from your own recent work, so neither of you solves the same problem twice.

[Video: An error in the terminal, a build that succeeds, and weeks later Earlyn saying the error was fixed before, with the steps that fixed it.](https://www.earlyn.app/video/clips/clip-errors)

## Errors and what fixed them

Earlyn reads error lines on developer surfaces only: terminals, editors, Xcode, the Simulator, and browser pages on localhost or with DevTools open. Each error is kept by its signature, with file paths, line numbers and ids taken out, so the same mistake in another file is one entry. When a build, a test run or the dev server reports success in the same app, the error is marked fixed, and the windows you went through in between (the docs page, the file you edited, the command you ran) become its fix.

- **Comes back?** A notification says you fixed it before, with the date. Nothing from the error itself is in the notification.
- **Brain → Errors** lists every error with how often you saw it and whether it is fixed. A fixed one shows what happened before the fix, each step opening Rewind at that moment.
- **Your agent asks first.** The `similar_errors` tool gives Claude Code the past fix in a few lines before it starts debugging.

[Video: Claude Code calling Earlyn's project_context and screen tools in a terminal.](https://www.earlyn.app/video/clips/clip-project)

## Catch your agent up on a project

Start Claude Code in a repository and it can call `project_context` with the folder: how long you worked on it and when, the files and windows you had open, the pages you read while working on it, meetings that mention it and the errors still open. A few hundred tokens instead of a tour of the codebase. The “Start on this project” skill makes it the first thing the agent does.

## Let it check its work on screen

Turn on Let AI tools read the screen in Settings → Connect. Excluded apps, private windows and anything that looks like a password are never shown.

| Tool | What it returns |
| --- | --- |
| screen_errors | Only the error lines on screen, in the app it is working on |
| screen_changes | Only what changed since its last look |
| find_on_screen | Whether a button or message is visible, and where |
| wait_for_text | One call that waits until a build finishes or a page loads |
| see_screen | A picture, only when layout matters |

## Questions

### Does Earlyn read every error I come across?

Only on developer surfaces. An article or a chat message about an error is not your error, so browsers count only on localhost or with DevTools open.

### Does this send my code anywhere?

Earlyn sends nothing. Your agent reads through Earlyn on your Mac, and what the agent reads goes to its own service, like anything you paste into it.

---
Canonical: https://www.earlyn.app/features/for-developers · Updated 2026-10-05