2026

I’ve been busy over weekend with completing a few work items that were in the cooking for a while. Some have been on my wish-list since day one, some have been brewing since a few years ago. It’s unbelievable how far certain architectural decisions can go, and I am genuinely excited to bring this new version to the daylight: 3.2.1.

I owe you an explanation. Not a corporate statement. Not a carefully worded legal notice. An actual explanation, from me to you, because you’ve trusted this tool – and by extension, me – for years. You deserve more than a changelog entry. So here it is. Four years. My pocket.

So you’ve jumped on the agentic coding train. You’re using Cursor, or Claude Code, or Windsurf, or whatever the cool kids are using this week. Your AI assistant writes AL code for you, and life is good. Except… who’s making sure your object IDs don’t collide? Nobody, that’s who. Until now.

You know what’s supposed to be unique? Snowflakes. Fingerprints. And GUIDs. A GUID (Globally Unique Identifier) is mathematically designed to be so astronomically unique that if you generated one hundred billion GUIDs per second, you’d still have a better chances of being struck by lightning twice and then winning the lottery, all on the same day, than generating a duplicate.

I’ve just released Ninja 3.1.0 , and it adds something I’ve wanted for a while: language-model tool-based object ID assignment . In practice, this means that when an agent is writing AL code inside VS Code, it can now use Ninja directly as a tool to allocate and commit object IDs. No typing.