Harness engineering for AI agents · Code audits · Code takeovers
A developer for twenty years, I help development teams move to AI agents, or make better use of them, without losing control of their code.
For teams producing more code with AI agents than they can review.
Harness engineering builds the environment AI agents work in: the context they receive, the rules they follow, and automated checks on every commit and in CI. Whether the team is starting with agents or already uses them, I set it up with the team, for example with Claude Code, and we put it to the test together on your real tasks. Everything stays in your repositories, documented.
I read the code, the architecture, the tests and the CI, then how the team works day to day. You get a written assessment with the priorities in order, and I can handle the most urgent ones right away: fixes, updates, missing tests. First findings come within a few days.
I take the code where it is stuck: what breaks with every change, what slows the application down, what nobody understands anymore. The goal is for the team to ship fast again without fear of breaking everything, whether the code came from agents or from a framework that is no longer maintained.
Topics I work on
Your situation fits none of these? Describe it, and we set the scope together.
Recent engagements, in different contexts.
TypeScript/Next.js product · 2026
Working as a team with AI agents on a product in production: 20 architecture checks set up, 129 PRs merged in 10 weeks.
Harness engineering: speeding up with AI agents while keeping control of the code
Business application · Laravel · 2026
An assessment of the code, dependencies and CI within a few days, then an upgrade from Laravel 8 to 13.
Mobile app and back office · 2026
An assessment within a few days, then slowdowns fixed at the source.
HR SaaS · Development lead
A unified library for more than fifteen recruiting platforms, interfaces and APIs for clients such as Ubisoft and Decathlon, and mentoring the developers.
Go · SaaS platforms
Moving Laravel components to Go on a data processing platform, then leave-tracking history and carry-over rules on another engagement.
Twenty years of software development, five of them as lead developer, first in industry (EADS, Airbus, Naval Group), then on SaaS platforms and business applications. I use AI agents every day, and I build Synapse, my lab: an agent orchestrator where I test what I later set up for clients.
Discover my background →I work in your repositories with the access you grant me. When I use an AI agent on your code, it goes through an account you control.
Yes, before any access to the code.
No. Audits, code takeovers and the CTO role do not depend on agents. Harness engineering is for teams that use them or want to bring them in.
Your team’s: Claude Code, Codex or Gemini. If another tool suits your use better, I tell you why, and the decision is yours.
Everything that was set up stays in your repositories: automated checks, agent rules, documentation. Nothing depends on me to keep working.
Your codebase, your AI workflows or a specific difficulty: a few lines are enough. Scope gets clarified in an initial conversation.
Your data: see the privacy policy
Remote engagements · French and English