# Is there a future for AWX? **URL:** \ **Category:** Get Help\ **Tags:** awx\ **Created:** [September 22, 2025, 1:30pm UTC](https://forum.ansible.com/t/is-there-a-future-for-awx/44527 "2025-09-22T13:30:56Z")\ **Posts on this page:** 1\ **Showing post:** 48
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [January 14, 2026, 7:13am UTC](https://forum.ansible.com/t/is-there-a-future-for-awx/44527/48 "2026-01-14T07:13:05Z")
Like @utoddl I also agree that communication should be better handled in this case. But I also agree with his call for caution on interpreting the signs here. Sometimes no news are just… no news. But we only know for sure _after_ we have updates. We are still missing on those. That being said, > [@XakV](#): > > I’m not a huge fan of AI, but setting that aside, how is code generated by Claude licensed? Can AI generated code be said to be free of end-user-agreements? There’s been some discussions about this in [Ansible AI Policy?](https://forum.ansible.com/t/ansible-ai-policy/42642/1) - not sure whether the AWX team is following that or not (if we cannot get them to update the status of the refactor, I am not holding my breath they will stop and digress about how they are using LLMs). > [@Nico\_Kadel-Garcia](#): > > Using a single branch to handle refactoring and ongoing patches is by different developers is something I’ve done, and it gets pretty painful pretty fast. Respectfully, that’s quite a jump to an inference based on too little information. The fact that the commits are in the main/devel branch does not mean they were not worked out in other branches before merging, so please hold your horses. And whilst I cannot vouch for most of the developers in the “Ansible-sphere” individually (I can do that for some) nor for most of the specific teams, I am confident that some basic practices are in place, including working in branches. --- _[View the full topic](https://forum.ansible.com/t/is-there-a-future-for-awx/44527)._