✓ ShippedByAgents
Practitioner (own blog/paper) Upgrade / modernisation

Lucas Firmo's agent fleet moves a production iOS app to Swift 6 strict concurrency in 10 days, with zero warnings left

Lucas Firmo has run most of his production work through several parallel AI coding agents for six months, across iOS, backend and web. Each task gets its own git worktree and a file on disk holding its plan and log, agents must claim a ticket before touching it, and Claude Code hooks enforce the rules: a pull request can't open without a passing review of that exact commit from a separate session, preferably a different model family, and every PR must carry proof such as a screenshot, captured output, or a test seen failing then passing. Anything touching production is refused unless he approves it. His biggest test was moving an iOS app to Swift 6 strict concurrency, with agents split by directory so they never touched the same file.

The numbers (as reported)

Time10 days for the Swift 6 strict concurrency migration
Result"zero concurrency warnings", feature work never stopped
TestsTest suite 25% larger than at the start

Facts

Company / subject
Tools
Claude Code
Codebase
brownfield
Work type
Upgrade / modernisation
Stack
Swift, iOS
Published
2026-10-08
Last checked
2026-10-23

What the source claims Practitioner (own blog/paper)

Claimed by the builder, writing about their own work. Not checked independently.

  • Swift 6 strict concurrency migration done in 10 days with zero concurrency warnings, feature work never stopped, and a test suite 25% larger 10 days; 0 warnings; +25% tests
    “We moved our iOS app to Swift 6 strict concurrency in 10 days.”

Caveats

A short personal blog post. It doesn't name the app, team or employer, the codebase size, the number of agents, the cost, or which second model does the reviews. Claude Code is named only as the tool whose hooks enforce the rules.

More stories by tool: Claude Code

Related topics: Upgrades and modernisationBrownfield codebases

Source

Bits with Lucas (Lucas Firmo)

One email a week: what actually shipped

New sourced stories, the numbers behind them, and what didn't work. No hype.

We'll only use this to send the newsletter. See the privacy page.