A purpose-built workshop for people who ship code
Drift pairs a deep reading of your repository with a broad tool belt and a live sense of what you just did, folding all three into one unhurried, collaborative rhythm. It is the calmest way we know to write software with a model beside you.
Built to hold your place in the work — it reads the intent behind a request and carries the tangled parts of the codebase so you can stay on the interesting half.
Explore DriftStart something new, or make one change ripple across the whole repository.
Models make mistakes. Read every diff before you keep it.
One keystroke, no ceiling, unbroken flow. The full reach of Ravenglass Glide lives only in the Studio — our plugins for other editors carry the completion step alone.
Tap to move the caret. Tap to pull in the import you forgot. Tap until the file is finished.
Glide featuresDrift keeps hold of the decisions that shape your codebase, and the habits that shape you.
Drift spots the lint errors it just introduced and clears them before you see them.
Extend what Drift can reach by wiring in your own services. Curated bridges live in Ravenglass settings for one-click set-up.
Build the screen you drew by dragging the image straight into Drift.
Forgot the flag? Press ⌘+I in the terminal and stay where you are.
Drift tracks what you were doing, so “carry on” is a complete instruction.
Switch on Sprint in settings and let Drift run the safe commands itself.
“Give any one of these engineers a single afternoon with Ravenglass and they come back changed. The work that used to eat a whole week now takes an evening, and they are still the ones steering it.”
Ravenglass beats the setup I nursed for years. The steps just get shorter — I type the prompt, wander off for a coffee, come back and there is a working preview sitting there.
I think Ravenglass wins this round of the editor wars, and not because of the product alone — it is the pace the team keeps and the way they answer.
Unreal. Whole app, one prompt.
Three weeks on it exclusively now. Nobody is paying me to say this. It is good. Genuinely, unreasonably good.
I picked Ravenglass because the team never stops sanding down the rough edges. The recent pricing rework — plain limits, no theatre — is what finally convinced me to move the whole studio across. It reads like they think about the people using it.
Ravenglass makes writing code fun again, and fast.
The quietly best thing in the Studio is the Problems tab — every issue in the project, in one honest list.
Been building a small tool all evening and I have spent almost none of it waiting, because the replies land before I lose the thread.
First-class support for every serious model provider
The same agentic workflow, folded natively into the Fathom editors your team already keeps open all day.
Install the pluginI can see you are working on the win condition for the Ludo game. Let me read the file, take in the context, and finish it with you.
The check_win method is empty and looks like a duplicate of has_won. I will build it from the game rules.
Repo digests, swap-and-replace edits, disposable dev containers, and rather more.
On something else? See every build we ship