Contents

Engineering agents at Indy (opens in a new tab)

Internal engineering agents built to handle recurring development work.

Chapter 2Mergedindy-agents into mainMay 2026 – October 2026agentic engineering

Context

Indy makes accounting software for freelancers and independents in France. Like in any engineering team, some work keeps coming back: Vue migrations, dead-code cleanup, and new tasks that look a lot like the last ones.

That kind of work suits an agent well. It’s well defined, it repeats, and nobody is sad to hand it over.

Changes

The agents pick up those tasks, work through them in the repository, and create or advance pull requests on their own. Engineers then review the result like any other pull request.

Design decisions

Most of my time went into making the system reliable, not just impressive in a demo:

  • The orchestrator decides what happens next, not the model.
  • The model does the actual work, inside clear limits.
  • Git and CI steps are predictable, so every run ends somewhere you can understand.

In short: the software stays in control of the workflow and the important decisions, and the model does the work.

Turn the pageChapter 3: VULX