Development Agent overview development-agent-overview
The Development Agent helps AEM developers and administrators create, debug, deploy, and optimize code more efficiently.
Currently, the agent can retrieve pipeline statuses and help you troubleshoot failing build steps by suggesting fixes, saving time when debugging AEM as a Cloud Service deployments to development, stage, and production environments. It examines build logs and related code to recommend a fix that you can apply manually.
Access the Development Agent through Cloud Manager how-to-access-the-agent
You access the Development Agent through the AI Assistant found in user interfaces including Cloud Manager or Experience Hub.
To access the Development Agent through Cloud Manager:
-
To get started, click Adobe Experience Cloud to open its home page.
-
In the left rail, under the Services heading, click Cloud Manager.
note important IMPORTANT The widgets, tools, and artifacts shown depend on the user persona, entitlements, and AEM deployment type (AEM as a Cloud Service or Managed Services 6.5/6.5 LTS). -
In the left rail, under Program, click
. -
On the Program Overview page, in the Pipelines card, click a pipeline.
-
In the Build and Code Scanning page, note the failed pipeline.
-
Near the upper-right corner of the AEM user interface (either from Cloud Manager pages or the author instance of the AEM environments), click the AI Assistant icon.
See also AI Assistant in AEM.
-
In the AI Assistant panel text box near the bottom, type your question or prompt, then press
Enteror click .For example:
In the “eda-org-01-no-access” program, analyze the failure to the “no-access” pipeline and troubleshoot.The prompt results in the following response.
Permissions permissions
The Development Agent’s pipeline troubleshooting job requires either the Cloud Manager - Developer role or the Cloud Manager - Program Manager role.
Sample prompts sample-prompts
Out-of-scope features out-of-scope-features
Pipeline troubleshooting operates on the Full-Stack pipeline’s build step. For other pipeline types and steps, debug failures by downloading and inspecting the logs.
Pipeline troubleshooting is not supported for programs using BYOGIT (Bring Your Own Git).