Really like this. I've been trying microsoft's copilot and it's so clunky, particularly when applying edits. One would assume they have the resources to train the model.. Request: please provide a system prompt in the docs to help the llm generate the diff format that performs best w/ your models. LLMs frequently change the way they present diffs on upgrades and I don't want to be guessing which format is best. EDIT:…
done! Yeah we have ZDR options as well, just email us to enable it info@morphllm.com Morph via OpenRouter is always zero data retention
Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
121–130 of 196 posts
Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#122Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#123I’d just like to put a pitch in here for someone to do “smart rebase+merge” with AI. Now THAT would really speed up development, if my AI was intelligently merging code from different users in the background, based on understanding the intent behind each conflicting change.
You can do that with Claude Code. Just tell it to merge in another branch and fix the merge conflicts.
Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#124Earlier quoted context omitted.
I think it depends - the actual thing to measure it to keep a developer in flow state. Many errors as well as latency break this. To be brief yes, accuracy comes first. Quality is measured 2 main ways: 1) End-to-end: User query -> to task resolution. These are aider style benchmarks answering the question of actual task completion 2) Apply Quality: Syntax correctness, character diff, etc.. The error rate for large vs…
I don't believe anyone can be in some kind of "flow state" while waiting on LLM responses. I think it's funny that we complained for years about C and others being slow to compile and now folks are fine waiting seconds++ everytime they want to change something.
I had tried doing it with different features in different worktrees in the same codebase but found flow much harder there.
Lately I am also just spending a lot more time reworking code manually to keep the code in good shape. Still getting a ton of value out of the LLM doing a lot of work, but not exactly spending lots of time just waiting for it because I am dropping back down to manual mode frequently.
Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#125"Let's be wrong faster! It's a feature, we swear!"
Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#126Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#127Just for clarification here because I am a bit confused, Morph is a tool for integrating the output of other LLMs and not an LLM itself? It doesn't generate 4500 tok/sec, it can edit 4500 tok/sec?
Correct, but morph is a LLM as well. In practice its basically Big LLM using small LLM as a tool call
Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#128Earlier quoted context omitted.
Flow state has been redefined now that we are all using Claude Code. If I can stay focused on tests, reviewing code, etc while CC is doing its thing, we are good. The kloc/s doesn't matter as much.
if LLMs are ever able to write the kind of code I write for work, I'm going to move to management. spending 100% of my time reviewing AI slop and writing tests is the opposite of what I want. I want to define behavior quickly and have AI do the boring parts; you're letting the computer do the fun bit and spending your entire life doing the shit part, and paying for the privilege. fuck. THAT.
Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#129Re: Launch HN: Morph (YC S23) – Apply AI code edits at 4,500 tokens/sec
#130I am assuming your models are not opensource/openweights?