Morph on Morph / Internal case study
We use Morph to make Morph better.
We merge thousands of lines of code every day. Coding agents help us ship at that pace. Morph helps us keep the codebase in good shape as we go.
Fast shipping left us with too many ways to handle the same error.
Services and screens had picked up different error shapes, duplicate helpers, and fallback paths. In a few places, a screen decided what to do from the wording of an error message. A copy edit could change behavior.
We gave Morph a clear finish line: one coherent error-handling pattern, stable codes for decisions, and the existing behavior preserved as old paths changed.
One goal became reviewable changes across repositories.
Morph mapped the affected code, broke the cleanup into milestones, and opened focused PRs. Our engineers reviewed the plan, diffs, and tests before merging changes.
A simpler error-handling system is in place.
The cleanup is merged. Services now follow a documented error contract, with stable codes guarded by tests and competing helpers consolidated. Browser flows use those codes instead of relying on error-message wording to decide what to show.
What would you clean up next?
Tell us about one pattern that keeps returning and the change it now blocks.