What does an AI coding agent need in order to be useful in a real software project?
Not a toy repository. Not a greenfield demo with a single happy path. A project with history, conventions, old decisions, security boundaries, tests, release procedures, and requirements that are never quite as complete as one would like.
That question is why a project I call Lutions—a self-hosted web application for projects and ticket workflows—grew into more than just the ticket system I originally set out to build.
This is an English adaptation of my original German article, Agentic AI: Wie ich zu meiner idealen Entwicklungsumgebung kam. It is not a product announcement or a claim that everyone should build their own ticketing system. It is a field note about the kind of working context in which agentic software development becomes concrete.
The project began with a much simpler problem
