Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment

AI agents

AI agents for legacy code: fast drafts, no authority.

Coding agents can read an old codebase, propose changes and run the tests. They cannot be accountable for the result. Engineers are.

AceMQ engineering team3 min readEngineer-reviewed

The short answer

AI coding agents can read legacy code, explain it, propose changes and run tests in a loop. They work best on bounded tasks with good tests, such as upgrades and refactors. They fail where behavior is undocumented or untested. Ace8 uses agents as drafters. Tests gate their output and a named engineer reviews it.

On this page

  • COBOL
  • Java
  • Jakarta EE
  • OpenRewrite
  • Spring Boot
  • COBOL
  • Java
  • Jakarta EE
  • OpenRewrite
  • Spring Boot

Capability

What can an AI agent do on legacy code?

An agent is a model with tools: it can open files, search, edit, run the build and read the failures. That loop is what separates it from a chat window. On a legacy codebase it is useful for a short list of jobs.

  • Explaining unfamiliar code and drawing out the call paths, which shortens onboarding.
  • Writing characterization tests that record what the code does today.
  • Making a repetitive change across many files and fixing the compile errors that follow.
  • Drafting a migration for one module so an engineer can judge the approach.
  • Updating documentation to match what the code does.

Limits

Where do agents fail on legacy code?

The failures are predictable, which makes them manageable.

Senior engineer reviewChecked by hand before anything merges5 checks
  • F-01Behavior defined by runtime configuration or by data in a database the agent cannot see.
  • F-02Business rules that no test covers. The agent will not know the rule exists, so it can delete it.
  • F-03Very large files and deep call chains, where the agent loses context and starts guessing.
  • F-04Changes that compile and pass thin tests but alter results, such as rounding, date handling or character sets.
  • F-05Languages and platforms with little public training material, which raises the error rate.

Planning this for your estate? Get a fixed scope and price first.

Controls

What controls keep agent output safe?

Step 01 of 05

Tests first

Write or extend tests before the agent touches the code. The tests are the specification it is held to.

Choosing

Agent or deterministic tool: which for which job?

Deterministic tools such as OpenRewrite go first because they are repeatable. Agents cover what the recipes leave behind.

Better fit

Recipe

WhyRule-shaped, same result every run

5 situations. Pick the one closest to yours.

Beyond Java

What about COBOL and mainframe code?

People search for agents that can translate COBOL. Agents can explain COBOL and draft translations. The hard part is not syntax. It is copybooks, batch scheduling, data formats and the behavior of the platform around the program. Ace8 focuses on enterprise Java, so we do not offer mainframe translation. The same controls apply to any language: tests first, small scope, human review.

Practice

How does Ace8 use agents?

We use agents inside the method described on the method page: test before you touch, AI drafts and engineers decide, every step reversible. We pick agents and tools per codebase, and we compare them on the same sample application. See the tools benchmark once it is published, and the wider AI-assisted modernization guide.

We have not yet published results from our own agent runs, so this page claims no speed-up figures. When the runs are done we will report files changed, test results before and after, manual fixes and review minutes.

FAQ

Frequently asked questions

Something else on your mind? Ask an engineer.

Not safely. Agents can draft and test changes, but without tests that capture real behavior and an engineer reviewing the diff, errors reach production. Use them as drafters, not decision makers.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

  • InventoryEvery application, its stack and what it depends on.
  • Risk scoreWhere a change is likely to break, ranked.
  • Phased planWhat moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.