Engineers in initial rollout
Onboarding workshops per team
Development speed target
Figures as of writing. The rollout is ongoing.
The Stakes: When Legacy Becomes Liability
Ida Infront has a long product history and public-sector customers. In that position, compliance concerns, risk analysis, and legacy infrastructure can all limit AI experimentation. CTO Magnus Grimsell recognized the risk: a younger competitor might build faster and cheaper and erode the value of Ida Infront’s platform. He decided to move early:
“We want to address that risk and take advantage of the opportunity by being early adopters.”
Magnus Grimsell, CTO
The Plan: One Tool, Three Workshops
Ida Infront’s goal is to double development speed by theby the end of 2026. Random experimentation won’t get it there.
After evaluating several AI coding assistants and agentic tools, Ida Infront standardized on Kilo, an open-source, model-agnostic tool that puts AI agents in the editors, terminals, and notebooks developers already use. That was before Kilo joined Anaconda in July 2026. Kilo by Anaconda is now a core part of AI workspaces in the Anaconda Platform, used by more than 5 million developers.
Magnus had watched peer companies leave adoption to chance: they told developers to use whatever AI tools they wanted, then waited, and nothing happened.
Ida Infront chose the opposite: one tool, organizational commitment, and a three-workshop program that brings its teams through the transition together.
The first workshop covers agentic engineering fundamentals. The second tackles the issues teams run into in practice. The third is non-technical: teams explore the phases of Ida Infront’s AI adoption framework and share how they feel about where they are on the journey, including their concerns and expectations. A structured exercise surfaces fears and hopes, so team members feel heard and can work through any resistance.
Early adopter teams are trained to coach the teams that follow. Kilo helped build the program, and Magnus valued the expertise it brought as well as the product itself: someone coming in to show the team how agentic engineering is done.
The Shift: From Coding Assistant to a Different Way of Working
As of writing, Ida Infront is still in the early stages of adoption, but early indicators are promising. Developers who already used a coding assistant expected an incremental improvement from Kilo. “With an assistant, you’re working the same way as before, just a little faster,” Magnus says. “With agents, the developer role itself starts to change.”
Now that teams have seen Kilo in action, they are eager to get onboarded, and other companies in Ida Infront’s parent group are already looking to replicate the model. Magnus sees both excitement and possibility:
“I’ve been through the shift from waterfall to agile. This is the same kind of shift. It affects everything. And I’d rather be shaping what that looks like than waiting to find out.”
Magnus Grimsell, CTO
“We didn’t just receive support for the product, but expertise that I’ve valued as well. It’s great to have somebody come in and say, ‘This is how we do agentic engineering.’”
Magnus Grimsell
CTO, Ida Infront
Open-source AI agents in your editor and terminal. 5M+ developers, 500+ models, now part of Anaconda.