Live data from Hacker News

Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec

news.ycombinator.com

1–10 of 196 posts

Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec

#1
Hey HN, I’m Tejas at Morph. We’ve built a blazing-fast model for applying AI-generated code edits directly into your files at 4,500+ tokens/sec. No more slow full-file rewrites or brittle search-and-replace hacks.

Here's a demo video: https://www.youtube.com/watch?v=LdT8epGHJPk.

Why? AI spits out code that can’t reliably be inserted into existing code. Full file rewrites, brittle search-and-replace hacks are too slow, expensive, or error-prone.

Morph's approach:

- Your agent outputs edits “lazily”, referencing unmodified lines in the existing file (ex: // ...existing code...)

- Morph instantly applies these edits to a file using our Fast Apply model + speculative decoding against the original file, making AI patches fast, reliable, and production-ready.

This approach was pioneered by Cursor last year, but their models aren’t available as APIs—so we built Morph for developers everywhere (with a large free tier!)

Live demo (no signup): https://morphllm.com/dashboard and docs: https://docs.morphllm.com/quickstart

We have 2 Fast Apply models: morph-v3-fast - 4500+ tok/sec, and morph-v3-large - 2500+ tok/sec. These models power Fast Apply at create.xyz, databutton, continue.dev, and more!

We also provide retrieval models for embedding + reranking. Next Up: Inline Edit Model (Cmd-K): Extremely fast inline edits - keep dev flow state; and Morph Tab API: Our Next Edit Prediction model guesses your next code edit + action with sub-500ms latency. It's currently in private beta, but you can request early access here: https://morphllm.com/tab

Hot takes:

1) Raw inference speed matters more than incremental accuracy gains for dev UX—agree or disagree?

2) Full-file rewrites by frontier models are legacy—Fast Apply edits win on speed, cost, reliability.

3) As benchmarks on narrow tasks saturate to 99%+, complexity is shifting from single frontier models to specialized inference-optimized models. As frontier models move upmarket, they'll leave simple tasks behind, and they'll be used to do tasks only frontier models can do

We’d love to hear your ideas and experiences with coding agents!

Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec

#4

Is there anyway to bring this into Claude Code?

There might be a way to using their new hooks commands, but out of the box, not yet. email us if you want to make it happen!

https://docs.anthropic.com/en/docs/claude-code/hooks

Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec

#6
post #5

Is there anyway to bring this into Claude Code?

If this proves the way forward, it will be in Claude Code soon enough natively

There is already https://www.relace.ai/, albeit not as blazing fast at mere 4300 tok/s

Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec

#7
post #5

Is there anyway to bring this into Claude Code?

If this proves the way forward, it will be in Claude Code soon enough natively

Perhaps. Boris from the Claude Code team shares a bit about their view here https://www.youtube.com/watch?v=Yf_1w00qIKc

My read is that despite Claude moving upmarket in what it can do, they are keen on clinging to all the (token heavy) tasks they're leaving behind

Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec

#9
> 1) Raw inference speed matters more than incremental accuracy gains for dev UX—agree or disagree?

I know you are trying to generate some controversy/visibility, but i think if we are being transparent here, you know this is wrong. People prefer using larger (or reasoning) models, with much bigger diff in tok/sec just for quality in coding, it comes first. Even if i have a big edit to apply, like 5k tokens, 200-300ms of difference in edit time are nothing. Edit speed is definitely not a bottleneck for dev UX, quality is. A dev who wants to save 200ms every code change over quality is someone who well, i cannot relate. If im using 1-2 agents in parallel, most of the time the edits are already applied while im reviewing code from the other agents. But again maybe that's just me.

Speaking of quality, how do you measure it? Do you have any benchmarks? How big is the difference in error rate between the fast and large model?

Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec

#10
post #8

Can't you ask these LLMs to simply output a patch file? https://man7.org/linux/man-pages/man1/patch.1.html

you can - but they dont work reliably in practice. Common issues include search match fails, missing commas in replaced items (model doesnt have surround context while replacing), and a few other error cases. This issues are much worse for scattered edits across a file from real world queries (ex: make this page look nicer). Patches tend to work fine for single line or extremely focused edits though - Cursor uses s&r/patches for single line edits:

https://github.com/x1xhlol/system-prompts-and-models-of-ai-t...

Post reply on HN