Your files, your terminal, your browser. Flint works where your work already is — no uploading a codebase to somebody's cloud first.
› read the failing test and fix it ▸ reading src/queue.test.ts ▸ running npm test -- queue 1 failing — retry() resolves before the backoff elapses ▸ editing src/queue.ts ▸ running npm test -- queue 4 passing Fixed. retry() awaited the timer handle instead of the promise, so the backoff never blocked.
Most AI tools ask you to paste code into a browser. Flint runs beside your work instead — reading real files, running real commands.
Reads and edits real files in real projects. No copy-paste, no upload, no context window spent describing your repo.
Runs commands, reads the output, and acts on it. Tests, builds, migrations, git — the boring parts, done properly.
With the companion extension, Flint drives the Chrome you already have — signed in, with your session. Not a headless stranger.
Point it at any OpenAI-compatible endpoint. Your key, your account, your bill — no per-seat markup in between.
The engine updates on its own channel, in place. You're told what changed and choose when — nothing swaps underneath you mid-task.
Built on DeepSeek Harness, MIT licensed. The engine is inspectable, replaceable, and not ours to lock down.
Built for people who care how fast their tools are.