Blitzy this week added a chat interface to a platform that enables DevOps teams to employ artificial intelligence (AI) agents by expressing their intent in natural language.
Dr. Neeraj Deshmukh, Field CTO for Blitzy, said the Chat to Prompt interface makes it possible for a software engineer to describe a desired outcome that is then automatically converted into a prompt that assigns a task to an AI agent. Additionally, DevOps teams via that interface can ask AI agents to explain how and why certain tasks were performed, he added.
The overall goal is to make it simple to explore an onboarded codebase, investigate the impact of proposed changes, and refine requirements in one conversation, said Deshmukh. Blitzy then converts that conversation into a structured build prompt, he added.
A Build Prompt Strength scoring tool then evaluates the draft against defined quality standards to surface any remaining issues.
At the core of the Blitzy platform is a knowledge graph that spans architecture, dependencies, business logic and data flows, which are then mapped back to the actual code. Thousands of AI agents are then used to build, validate and test code in parallel, with the output surfaced as a set of pull requests (PRs) prioritized by risk level that human software engineers can then review and approve. The knowledge graph itself can be queried and continuously evolves as a codebase changes.
The Blitzy platform then validates the implementation against the technical specification and the codebase context represented in its knowledge graph, with relevant testing and quality assurance (QA) results presented alongside the changes. Reviewers see what edits were made and whether the implementation meets the intended requirements. Additionally, DevOps teams can conduct file-by-file or line-by-line reviews of PRs if they so choose.
Any known and previously undiscovered vulnerabilities are traced through their execution paths, checked against dependencies, and validated for remediation.
Those capabilities are critical in the era of AI coding because a PR now spans hundreds of thousands of lines of code. Manually reviewing all that code line-by-line is simply not feasible, noted Deshmukh.
DevOps teams also need to be conscious of token costs that can be contained by making sure the prompts used to assign a task provide as much context as possible, he added.
The rate at which DevOps teams are employing AI agents varies from one organization to the next, but as they are used to generate code existing pipelines are becoming overwhelmed. At this point, it’s more a question of when DevOps teams will need to rely more on AI to manage that volume of code. The issue then becomes determining whether AI agents can be successfully incorporated into existing workflows or if DevOps teams will need to adopt an entirely new platform.
Regardless of approach, there is little doubt AI agents will be incorporated into those workflows. The only thing left to determine is how much faith to put in the output generated by AI agents that no matter how well constructed still require a significant amount of supervision.
