# Announcing the awx-tui **URL:** \ **Category:** Project Discussions\ **Tags:** awx-tui, mindshare, awx-modernization, awx\ **Created:** [March 24, 2026, 7:04pm UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591 "2026-03-24T19:04:10Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![tyraziel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tyraziel/32/10215_2.png) [@tyraziel](https://forum.ansible.com/u/tyraziel)\ **Post date:** [March 24, 2026, 7:04pm UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/1 "2026-03-24T19:04:10Z")
Hello everyone, I’m Andrew, a software engineer on the Ansible engineering team at Red Hat. I’ve been working on a side project that I’m excited to share with the community. # What is awx-tui? awx-tui is a text-based Command Line Interface (CLI) tool to help the community develop, manage, and use AWX. ![AWX-TUI-logo-640px](https://us1.discourse-cdn.com/ansible/original/2X/f/fca9c2b90cda9e0f39ae2b446fc8869c51d7a34b.jpeg) ### awx-tui: - Functions as a specialized, developer-focused REST API client for AWX. - Provides a diagnostic interface that can introspect what is going on in the API while creating resources, running playbooks, and viewing raw job events. - Inspects JSON responses for AWX constructs and exports them as tasks for Ansible playbooks. - Supports connections to concurrent, multiple instances of AWX from a single interface. - Visually presents AWX information through a dashboard backed by an extensible plugin system. ![image](https://us1.discourse-cdn.com/ansible/original/2X/e/ebad063af17e10e1f1fedf137349ab790dc72308.jpeg) ![image](https://us1.discourse-cdn.com/ansible/original/2X/b/b522be05b95632e343d4606b19d0fb3a6c6f7caf.png) ![image](https://us1.discourse-cdn.com/ansible/original/2X/5/508015cc869bab9117176f13e76970950ed1810d.png) ![image](https://us1.discourse-cdn.com/ansible/original/2X/d/dc2ac111691a9a7bcee08a00bbbdc44906495ed5.png) ![image](https://us1.discourse-cdn.com/ansible/original/2X/a/a6bdc4d94b4a2838b0cfc8076ad6e531eda7a57c.png) ![image](https://us1.discourse-cdn.com/ansible/original/2X/d/d9a8d44dfdac3d64a175c1171ae3cdd023adb638.jpeg) ![image](https://us1.discourse-cdn.com/ansible/original/2X/1/1cce59152257db7e71e655c7196f35e5f559e91a.jpeg) ![image](https://us1.discourse-cdn.com/ansible/original/2X/3/3a6a244e23307e84abb94b54ec5202b69563ffb3.png) # Call to action! At CfgMgmtCamp talked about awx-tui and got some positive feedback. Those conversations helped us realize that making this tool more widely available would be beneficial to the community. To that end, we’re asking for the Ansible community to get involved and shape the future of this project. Here are some ways you can do that: - Follow the [Quick Start Guide](https://github.com/ansible-community/awx-tui?tab=readme-ov-file#quick-start) to get up and running with awx-tui. - Fork or clone the [awx-tui’s GitHub repository](https://github.com/ansible-community/awx-tui) and [set up a development environment](https://github.com/ansible-community/awx-tui?tab=readme-ov-file#development). - Open [issues](https://github.com/ansible-community/awx-tui/issues) in the repository if you find bugs or have a cool idea for new features or capabilities. - Open a [pull request](https://github.com/ansible-community/awx-tui/pulls) if you want to make some changes. - Join the discussion on the forum, using the [awx-tui tag](https://forum.ansible.com/tag/awx-tui). We also want community members to join us as project maintainers. If you are interested in overseeing some of the development work on awx-tui and want to have a say in where we go from here, please let us know. You can reply directly to this thread or by opening an issue in the repo. If you’re on Matrix, you can also get in touch in the [Ansible AWX](https://matrix.to/#/#awx:ansible.com) room. I’m looking forward to our collaboration! ---
**Author:** ![bvitnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bvitnik/32/4132_2.png) [@bvitnik](https://forum.ansible.com/u/bvitnik)\ **Post date:** [March 24, 2026, 9:58pm UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/2 "2026-03-24T21:58:34Z")
Just one question. Why angry potato 😄? ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [March 25, 2026, 6:33am UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/3 "2026-03-25T06:33:24Z")
@bvitnik The “Rage Potato” is the official icon for the AWX project: ![awx-icon](https://us1.discourse-cdn.com/ansible/original/2X/5/5afe2fdc0b71cacff7f9419db2e48392d8662266.svg) And this is the official logo for the AWX project ![awx-logo](https://us1.discourse-cdn.com/ansible/original/2X/b/b461b03ebf2fac7f13091bd540d9537e32aec5bf.svg) ---
**Author:** ![bvitnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bvitnik/32/4132_2.png) [@bvitnik](https://forum.ansible.com/u/bvitnik)\ **Post date:** [March 25, 2026, 11:33am UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/4 "2026-03-25T11:33:03Z")
First time seeing it now. Sorry 😄 ---
**Author:** ![watsonb](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/watsonb/32/309_2.png) [@watsonb](https://forum.ansible.com/u/watsonb)\ **Post date:** [March 25, 2026, 12:45pm UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/5 "2026-03-25T12:45:30Z")
Came here from the Reddit post. I was overly cautious at first because I’m seeing an explosion of seemingly cool CLI tools and TUIs that are obviously vibe-coded quickly and shipped. I’m not disparaging AI-assisted coding, but I need to see things to make me comfortable trying something, and a quick gander at the repo makes me think this thing has some real merit behind it. As a long time AWX user and CLI enthusiast, I’ll be sure to check this out. ---
**Author:** ![watsonb](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/watsonb/32/309_2.png) [@watsonb](https://forum.ansible.com/u/watsonb)\ **Post date:** [March 25, 2026, 2:16pm UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/6 "2026-03-25T14:16:13Z")
Well I must say it is quite nice. I’ve already submitted a feature request. Good job thus far. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [March 25, 2026, 4:05pm UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/7 "2026-03-25T16:05:39Z")
> [@watsonb](#): > > Came here from the Reddit post. I was overly cautious at first because I’m seeing an explosion of seemingly cool CLI tools and TUIs that are obviously vibe-coded quickly and shipped. I’m not disparaging AI-assisted coding, but I need to see things to make me comfortable trying something, and a quick gander at the repo makes me think this thing has some real merit behind it. > > As a long time AWX user and CLI enthusiast, I’ll be sure to check this out. Disclaimer: I’m part of the Ansible Community team at Red Hat, and have a few small commits in awx-tui. @watsonb Nice to see some of the r/ansible crew on the Ansible Forum. I agree that everybody should be careful, especially with the low bar to entry that AI gives us. This is a tool that been used inside Red Hat by some of the Controller (AWX) team for a while, great to see positive feedback already > [@watsonb](#): > > Well I must say it is quite nice. I’ve already submitted a feature request. Good job thus far. Great that you’ve already had the chance to use it > > > \### Summary > > I think those of us that use vi/vim/neovim would appreciate the abi…lity to navigate using the classic h, j, k, and l keys. > > \### Additional Information > > N/A > > \### Code of Conduct > > \- \[x\] I agree to follow the Ansible Code of Conduct I’m sure there are more of us vim users out there that would also welcome this ---
**Author:** ![BoerBart](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/boerbart/32/10083_2.png) [@BoerBart](https://forum.ansible.com/u/BoerBart)\ **Post date:** [March 26, 2026, 6:38am UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/8 "2026-03-26T06:38:27Z")
This looks great. Never thought about needing such a thing, but now I see this, this really looks like something I’ll be using on a daily basis. Will give it a try soon, thanks for putting the project out there! ---
**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\ **Post date:** [March 31, 2026, 7:09pm UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/9 "2026-03-31T19:09:46Z")
I’ve never been a huge vi fan, but I appreciate where the “hjkl nav” desire comes from. Every new laptop puts the cursor keys _somewhere new_, but at least they’ve left the home-row keys mostly alone (so far). ---
**Author:** ![maxamillion](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/maxamillion/32/98_2.png) [@maxamillion](https://forum.ansible.com/u/maxamillion)\ **Post date:** [April 3, 2026, 3:02pm UTC](https://forum.ansible.com/t/announcing-the-awx-tui/45591/10 "2026-04-03T15:02:47Z")
This rules! I love it. I’m all-in on tuis. It’s like k9s but for my ansible. Absolutely incredible. \<3