Development Agent Overview development-agent-overview

Last update: June 17, 2026

Applies to:
Experience Manager as a Cloud Service

CREATED FOR:

User
Admin
Developer

As part of the Brand Experience Agent, the Development Agent helps traditional AEM Java-stack developers and administrators create, debug, deploy, and optimize code more efficiently.

It supports the following jobs, which are accessible through the AI Assistant’s conversational interface.

Cloud Manager Job: read-only operations, including listing of programs and environments, and pipeline status
Pipeline Troubleshooting Job: debug failed pipelines
Quiet Hours and Update Free Periods Management Job (Limited Availability): view, create, and edit Quiet Hours and Update Free Periods
Replication Troubleshooting Job (Beta): debug replication-related issues such as blocked queues.

NOTE

Developers will also find these AI-powered features useful:

IDE Agent Skills for local development scenarios such as generating AEM components.
Local MCP servers for local development, particularly debugging AEM and dispatcher issues.
Remote MCP servers for accessing APIs and AEM agents.

IMPORTANT

AI-generated responses may be inaccurate or misleading. Be sure you double-check suggested fixes and responses.

You can email development agent–specific feedback to aem-devagent@adobe.com.

Cloud Manager Job cloud-manager-job

Find information about your AEM programs and environments, including:

listing programs and environments
listing environment variables
finding the names of pipelines and current execution status and step details
retrieving links to logs that can be downloaded

Sample prompts sample-cm-job-prompts

Prompt

Result

List all my AEM Cloud Service programs

Lists programs that you have access to.

Get details for program 12345

Retrieve details about the program.

List environments in program 12345

Lists environments in the program.

Get logs for the production environment

Retrieves links to various AEM, dispatcher, and CDN log files so they can be downloaded for debugging or other purposes.

list pipelines for program 12345

List pipelines in the program.

What’s the status of the current pipeline execution?

Responds with status of the pipeline.

Get me the build log links for pipeline execution 12345

Retrieves links to pipeline build logs for a specific pipeline execution.

Quiet Hours and Update Free Periods Management Job control-updates-job

AVAILABILITY

This feature is in a Limited Availability phase and will be rolled out over the next few weeks. Email aem-devagent@adobe.com. for immediate access.

View, create, and edit Quiet Hours and Update Free Periods directly through the AEM AI Assistant.

The key benefit is fewer scheduling errors. As you make a request, the assistant guides you through what is possible and flags the limits that apply, such as the three-period cap, the mandatory one-week gap between periods, and the planned maintenance exclusion windows you cannot schedule over.

So instead of discovering a constraint after a failed configuration, Business Owners and Deployment Managers are steered to a valid schedule in the same conversation. This protects critical business windows from automatic maintenance updates while reducing back-and-forth and misconfiguration.

Sample prompts sample-updates-prompts

Prompt

Result

What’s the current update schedule for program 12345?

Results in a listing of the current AEM update rules.

Block AEM updates from 9 AM to 5 PM EST for program 12345

Sets up a rule so AEM updates aren’t applied during standard work hours.

Remove the daily update block for program 12345

Removes the rules preventing AEM updates.

Pause AEM updates starting in two weeks for program 12345

Creates a rule to prevent AEM updates.

My program keeps getting updated at inconvenient times. What options do I have?

Responds with information about how to set rules to control the AEM update schedule.

Pipeline Troubleshooting Job cloud-manager-pipeline-troubleshooting

This job 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.

https://video.tv.adobe.com/v/3478006?quality=12&learn=on

NOTE

Pipeline Troubleshooting is limited to Full Stack pipelines (Deployment and Code Quality), and Web Tier Config Pipeline.

Follow along a tutorial to learn how to use the Development Agent to troubleshoot pipeline failures.

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 get started, click Adobe Experience Cloud to open its home page.

In the left rail, under the Services heading, click Cloud Manager.

The drop-down list showing the Content Author preset is selected

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 Enter or 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 pipeline troubleshooting job requires either the Cloud Manager - Developer role or the Cloud Manager - Program Manager role.

Sample prompts sample-pipeline-prompts

Prompt

Result

Troubleshoot my failed pipeline

Performs an analysis of why a pipeline failed; if it is unclear which pipeline is being referred to, additional questions will be asked to the user.

List my failed pipelines for program Main Program.

While results may vary, this prompt outputs a table of failed pipelines, with a follow-up suggestion to reference a specific pipeline to analyze.

Analyze my failed pipeline called “Dev Pipeline.”

This prompt results in an analysis of the failed pipeline with suggestions to fix. If there are multiple failures, additional questions will be asked of the user.

Troubleshoot pipeline execution 1234567

By providing an exact pipeline execution id, a pipeline analysis is performed.

Out-of-scope features out-of-scope-features

Pipeline troubleshooting operates on the Build & Unit Testing step and Code Scanning step in Full Stack Deployment and Code Quality pipelines. It also supports web tier config pipelines.

For other pipeline types and steps, debug failures by downloading and inspecting the logs. See Access and Download Logs for more information.

Replication Troubleshooting Job (Beta) replication-troubleshooting-job

Debug replication-related issues such as blocked queues.

Please email aem-devagent@adobe.com for access to the beta program.

recommendation-more-help

experience-manager-cloud-service-help-main-toc