Short answer: Adir Ben-Yehuda says it covers front end and back end, generating mock data when no APIs exist. Sending to dev opens a GitHub pull request, and its few thousand weekly pull requests get 86% approval on first shot.
From Episode 43: The AI Product Team Replacement? Inside Autonomy AI’s Live Demo, starting at 12:05.
Jordan Metzner [12:05]: Is this front end only? Is this connected to data sources? Kind of what is kind of the next steps of kind of turning this from kind of prototype into kind of the next level production? Or I mean, I saw the sent to devs, but, tell me a little bit more.
Adir Ben-Yehuda [12:19]: So it's it's a great question. It's not front end only. It's front end and back end. You can actually everything is connected directly to the APIs. If you don't have APIs, we'll generate mock data for you and you can actually ask us to generate the back end itself. But and that's a huge part of it. Right? Think about the audience we're catering is not like a audience that understand the code base itself. Right? So from a guardrail perspective, you won't do everything ad hoc. We wanna give a visual validation for the user itself. And once they decide to send it to dev, we have an agent that actually goes on the PR and connects everything together. You can be more prescribed and force us and ask from the agent to do everything. We have no problem in doing it as well.
Jordan Metzner [12:57]: Got it. So it can sit on top of your existing code base, creating new tools using the existing data sources you already have and then connecting it at the PR level?
Adir Ben-Yehuda [13:06]: Correct. You can update current screens or current flows from that perspective or generate a new one, but everything will be connected to your code base itself.
Jordan Metzner [13:14]: Awesome. Okay. Cool. And then deploy to dev is like giving basically taking that URL and putting it on the Internet in some way or another. Right? Like giving you a host hosted version of that. Right?
Adir Ben-Yehuda [13:23]: Let's let's do it now. Let's send it to dev. It will take a few seconds. Right? And what it would actually do, it will prep the pull request itself. It will send it to your GitHub repository and will generate it a full pull request from that perspective. It takes a few minutes because like we're preparing all the back end there from the flow. And you will see it like every pull request you see from engineers. It goes to the CICD option. I'll give you a nice stat. On a weekly basis, we have a few thousands of pull requests. We have 86% approval on first shot. Because the pull request we're generating are part of your organization.
Jordan Metzner [13:59]: Oh, I got it. So, yeah, since the pull request knows kind of all the permutations that are required in order to have a successful PR, then it just does that the first time.
Adir Ben-Yehuda [14:08]: Correct.