Skip to main content

Copado Brings AI Agents to DevOps Platform for Building Custom Salesforce Apps

Copado has added artificial intelligence (AI) agents to its DevOps platform for building and deploying custom applications for the software-as-a-service (SaaS) application platform from Salesforce.

At launch, Copado is making available Agentia AI agents specifically that can be assigned plan, build and testing tasks via an orchestration agent that manages the overall workflow. Each Agentia AI agent understands the unique metadata framework that Salesforce developed but also all the dependencies, pipelines and testing activity occurring across the software development lifecycle (SDLC) that is captured via the Agentia Context Hub.

Additionally, there is an Agentia Studio tool that can be used to build AI workflows and other autonomous agents.

Copado CEO Ted Elliot said the Agentia AI agents have been trained using metadata, pipelines, and customer-provided knowledge to automate, for example, planning and documentation tasks or the actual writing for code.

DevOps teams can also apply policy-based controls based on roles and approval gates. Those teams can also generate a complete audit trail for any agentic workflow that is executed.

Finally, Copado plans to soon provide additional observability agents to provide deeper levels of visibility across the SDLC.

The overall goal is to increase the speed at which applications can be developed in a way that also serves to improve quality, said Elliot. While application development tools can use any number of AI coding tools, if they lack any context about the runtime environment the quality of that code is always going to be suboptimal, he added.

AI tools, ultimately, should be used to augment human application developers that can now spend more time building applications that provide more value to the organization, noted Elliot.

However, if application developers are removed from that process organizations will one day discover they will need to retrain them because ultimately it’s a human that is responsible for how any given application functions, he added. Application developers, even with the help of AI, are not going to be able to fix code if they don’t understand how it was constructed in the first place, noted Elliot.

Mitch Ashley, vice president and practice lead for software lifecycle engineering at the Futurum Group, said DevOps teams have a clear need for agentic SDLC platforms that, in addition to enabling them to govern agents, also allow them to prove what shipped. Multiple vendors are competing to own the agent control plane within a Salesforce environment, he added.

Regardless of approach, the pace at which custom Salesforce applications can be built and deployed has accelerated. It’s not clear how many of the organizations building those applications have an appreciation for best DevOps practices, but as the number of applications that need to be maintained increases, the need for a more structured approach to application development becomes apparent.

The challenge then, of course, becomes integrating custom Salesforce applications with the rest of the portfolio of applications that is being managed by all the other DevOps teams that typically exist in the same organization.



from DevOps.com https://ift.tt/SHUid6R

Comments

Popular posts from this blog

Cursor’s New SDK Turns AI Coding Agents Into Deployable Infrastructure

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...

OpenAI Debuts Symphony to Orchestrate Coding Agents at Scale

OpenAI has unveiled Symphony, an open-source specification that shifts how software development teams deploy AI in workflows, moving from interactive coding assistance toward continuous orchestration of autonomous agents. Symphony reframes project management tools as operational hubs for AI-driven coding. Rather than prompting an assistant for individual tasks, developers assign work through issue trackers, allowing agents to execute tasks in parallel and deliver outputs for human review. The change reflects a trend in enterprise AI in which systems are increasingly embedded into production pipelines rather than used as standalone tools. Symphony emerged from internal experimentation at   OpenAI , where engineers attempted to scale the use of   Codex   across multiple concurrent sessions. While the agents proved capable, human operators became the limiting factor. Engineers found they could only manage a handful of sessions before coordination overhead offset pro...