Morph / Codebase cleanup

Coding agents left a mess? Morph can clean it up.

Fast agent work can leave duplicate helpers, catch-all error paths, and callers still expecting old behavior. Morph traces the affected code across your repositories, opens focused PRs, and checks the workflows those changes could break.

Discuss a cleanup project →See our cleanup case study →

Map the pattern · Change affected callers · Check behavior

System map · each agent builds on the last

Illustrative example · three rounds of agent passes ↻
Agent changes accumulate across shared repositoriesFifteen illustrative agent passes over three clockwise rounds use Claude Code, Codex, OpenCode, and Pi around three example repositories. Each pass shows added and removed lines. The center adds those diffs to a starting codebase of 140,000 lines, so total lines of code increase from pass to pass. Each repository bar marks an agent pass that touched it. Morph scopes one cleanup across the codebase. All counts and repository changes are illustrative, not measured outcomes or claims about any agent.ROUND 01 / 03SHARED REPOSITORIES01 / 15TOTAL LINES OF CODE148,285+10,432−2,147platform-apiweb-appshared-lib

01 / Agent passesEach pass edits part of the system and adds more code.

02 / Code builds upNew helpers and fallback paths stay in the repositories for the next pass.

03 / Morph cleanupMorph finds duplicates and inconsistent error paths, opens reviewable PRs, and checks behavior.

What builds up over time

The cost shows up in the next change.

The next fix has to account for every duplicate helper, hidden fallback, and caller still using the old contract.

01 / Duplication

Duplicate code

A new helper duplicates an older one. The next fix must find and change both.

02 / Hidden failures

Failures hidden by fallbacks

A catch returns an empty value instead of surfacing the failure. The screen looks normal while the bug stays hidden.

03 / Behavior drift

One fix breaks another path

One path is updated, but an older caller still expects the previous response. A quick check passes while that workflow fails.

How Morph handles the cleanup

Give the cleanup a finish line.

Choose the convention to keep and the behavior that cannot change. Morph maps the affected callers and helpers, then proposes milestones for your team to approve.

01 / Find

Map the affected code.

Morph traces routes, screens, and shared helpers before editing.

02 / Change

Open PRs your team can review.

Each milestone has a defined change and acceptance check, so reviewers know what to look for.

03 / Check

Check the behavior that matters.

Tests and acceptance checks show whether the cleanup met the goal before your team merges it.

An internal case study

We use Morph to make Morph better.

Our own product had picked up several ways to handle the same error. Some screens chose what to do by reading error wording, so a copy edit could change behavior. We gave Morph one cleanup goal and reviewed its plan, PRs, and tests ourselves.

Modelcode internal case study
Morph on Morph · Code cleanup

We put Morph to work on our own error handling.

Changing an error message could change what a screen did. Morph mapped the affected code and opened reviewable PRs for a shared error contract.

Read the case study
Your codebase

What would you clean up first?

Share the recurring pattern and the change it blocks. We'll follow up to scope a first cleanup project and see whether Morph is a fit.

Start with one code problem

Tell us what's hard to change safely.

A short description is enough. Please leave private code out of the form.

We'll read your note and reply by email.