Why Kidge exists.
No corporation, no feature bingo – a concrete problem that demanded a better solution.
The backstory
Kidge started as a Python prototype that remote-controlled Autodesk Inventor from the outside via win32com. It worked – but only with fragile workarounds: temporary iLogic rules just to reach certain API functions, and Windows polling to dismiss dialogs that blocked the script. Any Inventor crash took the script down with it. The fix was a complete rewrite as a native C# add-in that runs directly inside the Inventor process: full API access, real exceptions instead of silently hanging calls, no remote control from the outside.
Who's behind it
Kidge is built by Jonas Hayk – no corporation, no investor pitch, a single developer who uses Inventor himself and got tired of the same time-consuming click chains. That shapes the beta approach too: rather show honestly what works today and what doesn't yet (see the download page) than make big promises.
What problem Kidge solves
Repetitive CAD busywork – maintaining iProperties, counting through parameters, setting standard features, dimensioning drawings – eats up time in Inventor that should belong to actual design work. At the same time, a plain ChatGPT tab is useless if it can't see the model. Kidge connects modern AI models directly to the Inventor API, instead of forcing copy-paste between chat and CAD.
The philosophy
Two principles run through the whole project: self-verification – Kidge plans, works step by step, and backs up every step with evidence instead of just claiming success – and BYO-AI – you decide which AI sees your data and what it costs, not Kidge.