Development Agentic Capabilities development-agentic-capabilities
The Development Agentic Capability of Adobe Experience Manager (AEM) as a Cloud Service collaborates with Coworker Chat to help traditional AEM Java-stack developers and administrators create, debug, deploy, and optimize code more efficiently.
Use Cases use-cases
A range of use-cases are covered.
Manage Cloud Manager Pipelines aem-cloud-manager-pipeline-management
The AEM Cloud Manager Pipeline Management skill lets you manage your CI/CD pipelines directly through natural language, without switching between Cloud Manager screens to find the information or controls you need. You can list and create pipelines, kick off or cancel executions, and check status and history — all from a single conversation.
When something goes wrong, the skill goes beyond status checks: it can retrieve step metrics, logs, artifacts, and execution failures so you can diagnose an issue without downloading and searching through raw log files yourself. It also handles day-to-day pipeline configuration — managing pipeline variables, invalidating cached artifacts, and adjusting pipeline settings — so routine maintenance tasks that used to require several clicks through the UI can be done with a single request.
To find out why an execution failed, see AEM Cloud Manager Pipeline Troubleshooting.
AI can make mistakes so review suggested actions before applying them, particularly for destructive operations.
“What pipelines do I have in Main Program?”
“Set up a Code Quality pipeline for my dev environment”
“Start execution for pipeline 67890”
“Stop the running Code Scan step for execution 12345”
“Show me the last 5 executions of Dev Pipeline”
“How long did the Code Scan step take on my last run?”
“Pull the logs for the failed Code Scan step”
“Where can I download the build artifact from my last run?”
“List all failed executions for program 12345 this week”
“Update the API_ENDPOINT variable on pipeline 67890”
“Clear the build cache before my next run”
“Change the trigger branch for pipeline 67890 to release”
AEM Cloud Manager Pipeline Troubleshooting aem-cloud-manager-pipeline-troubleshooting
The AEM Cloud Manager Pipeline Troubleshooting skill helps you find out why a pipeline execution failed, without downloading and searching through raw log files yourself. Reference a failed execution by pipeline name or execution ID, and the skill confirms the failure in Cloud Manager, identifies the failed step, and explains in plain language what went wrong, why, and what to do next. If your request matches more than one pipeline, the skill asks you to choose one before it continues.
Note that this capability is implemented as a specialist agent and so does not visually appear as a listed skill in the Coworker Customizations interface.
The skill investigates failures in the following pipelines and steps:
- The Build & Unit Testing step and the Code Scanning step in full-stack Deployment and Code Quality pipelines.
- Build and code quality failures in web tier config pipelines, such as Dispatcher configuration validation errors.
- Deployment failures in config pipelines, such as an invalid CDN configuration.
For failures in other steps, such as the deployment step of a full-stack pipeline, the skill reports the failed step without diagnosing it. In that case, inspect the logs as described in Access and Download Logs, or contact Adobe Support.
You can also start troubleshooting without writing a prompt. Click Troubleshoot with AI on a failed pipeline execution in Cloud Manager, or in the Failed Pipelines widget on the Experience Manager home page, to open Coworker with that execution already referenced. See Troubleshoot a Failed Pipeline from Cloud Manager and Troubleshoot from the Failed Pipelines Widget.
AI can make mistakes so review the diagnosis before acting on it.
“Help me troubleshoot the last pipeline that failed in Main Program”
“Troubleshoot execution 1234567 of Dev Pipeline in program 12345”
“Why did my config pipeline deployment fail in program 12345?”
Permissions pipeline-troubleshooting-permissions
To use the AEM Cloud Manager Pipeline Troubleshooting skill, you must have either the Developer or the Program Manager role in Cloud Manager. See Role-based permissions.
Troubleshoot a Failed Pipeline from Cloud Manager troubleshoot-from-cloud-manager
Starting from the failed pipeline execution is the fastest way to troubleshoot, because Coworker receives the execution as context and you do not have to write a prompt.
-
Sign in to Adobe Experience Cloud, then open Experience Manager.
note tip TIP To troubleshoot without opening Cloud Manager, type a prompt such as Troubleshoot my failed pipeline in the Ask Coworker anything box on this page. -
In the left rail, click Cloud Manager, then select your program.
-
On the Program Overview page, in the Pipelines card, click the pipeline that failed.
-
On the pipeline execution page, note the Failed status next to the pipeline name, and the step that failed.
-
Click Troubleshoot with AI. The button appears near the upper-right corner of the page and in the Step errors box of the failed step.
Coworker opens in a panel on the right side of the page, with the failed execution referenced in the prompt. Coworker identifies the failed step, explains the root cause, and suggests a fix that you can apply manually.
-
Review the diagnosis. To ask follow-up questions or request more detail, type in the Ask Coworker anything box.
Troubleshoot from the Failed Pipelines Widget troubleshoot-from-experience-home-widget
The Experience Manager home page includes a Failed Pipelines widget that lists pipeline failures across your programs, so you can start troubleshooting without first opening Cloud Manager. Each row shows the pipeline name, the date and time of the last run, the duration, and the step that failed, along with a Troubleshoot with AI button.
-
Sign in to Adobe Experience Cloud, open Experience Manager, then scroll to the Failed Pipelines widget.
-
In the row of the pipeline that you want to investigate, click Troubleshoot with AI.
Coworker opens with the failed execution referenced and starts its analysis, identifying the root cause and suggesting a fix.
-
Review the diagnosis. To ask follow-up questions or request more detail, type in the Ask Coworker anything box.
AEM Cloud Manager Environment Management aem-cloud-manager-environment-management
The AEM Cloud Manager Environment Management skill lets you manage your Cloud Manager environments through natural language, without navigating through Cloud Manager’s UI screens to find the right program, environment, or configuration panel. You can list your environments, pull up details on a specific one, and create, clone, or delete environments as your project needs change.
Day-to-day environment upkeep is covered too: managing environment variables, downloading logs for debugging, resetting a Rapid Development Environment (RDE) when you need a clean slate, and configuring region deployments — all from a single conversation instead of several trips through Cloud Manager. When something needs to be rolled back, the skill can also restore an environment from a backup.
AI can make mistakes so review suggested actions before applying them, particularly for destructive operations.
“Show me all environments in Main Program”
“What’s the status of my production environment?”
“Set up a stage environment for testing”
“Duplicate the stage environment for program 12345”
“Remove the unused test environment”
“Set the API_BASE_URL variable on my stage environment”
“Download the dispatcher logs for my stage environment”
“Reset the rapid development environment for program 12345”
“Show me the region deployments for my production environment”
“Show me available backups for the stage environment”
AEM Cloud Manager Program Management aem-cloud-manager-program-management
The AEM Cloud Manager Program Management skill lets you look up and manage your Cloud Manager programs through natural language, instead of navigating Cloud Manager’s program listings to find the one you are looking for. You can list all the programs you have access to, pull up details for a specific one, and delete a program when it is no longer needed.
Since programs are the umbrella that pipelines and environments live under, this skill also acts as a quick entry point into those related resources — you can ask it to show the pipelines or environments tied to a given program without first tracking down the program ID yourself.
AI can make mistakes so review suggested actions before applying them, particularly for destructive operations.
“What programs do I have access to?”
“Show me information about Main Program”
“Remove the old-demo program”
“List pipelines for Main Program”
“What environments does Main Program have?”
AEM Cloud Manager Release Management aem-cloud-manager-release-management
The AEM Cloud Manager Release Management skill lets you control when Adobe applies automated maintenance updates to your program, without digging through Cloud Manager settings to find the right screen. You can check your current update schedule, set a daily Quiet Hours window — a recurring time each day when Adobe pauses updates — and schedule a multi-day Update-Free Period around events like a product launch or a holiday freeze, when you do not want any changes landing on your environments.
If your plans change, you can remove an Update-Free Period just as easily as you scheduled it. The skill can also show you Adobe’s own global Code-Freeze periods — the windows Adobe has already blocked off for planned maintenance exclusions — so you know upfront which dates are already off-limits before you try to schedule your own.
The skill also helps you avoid scheduling errors. As it guides you through a request, it flags the limits that apply, such as the maximum of three Update-Free Periods within a floating 365-day window, the mandatory one-week interval between periods, and Adobe’s planned maintenance exclusion windows. Instead of discovering a constraint after a configuration fails, you reach a valid schedule in the same conversation. This approach protects critical business windows from automatic maintenance updates and reduces back-and-forth and misconfiguration. See Quiet hours and Update free periods.
AI can make mistakes so review suggested actions before applying them — this is especially true for update-schedule changes, since an incorrectly scheduled or removed Update-Free Period could allow updates to land during a window you meant to protect.
“Show me the update schedule for program 12345”
“Update my Quiet Hours window to start an hour earlier”
“Block updates for program 12345 during launch week, March 3-10”
“Cancel the blackout window I scheduled for next week”
“Show me Adobe’s planned maintenance exclusion periods”
AEM Workflow Inspection aem-workflow-inspection
The AEM Workflow Inspection skill lets you check on workflow activity in plain language. Ask Coworker which workflows are running, what’s waiting in your inbox, or why a workflow failed, without opening the Workflow user interface.
You can look up a specific workflow, browse available workflow models, and ask follow-up questions as you troubleshoot. This skill is read-only: it helps you see and understand what’s happening, but it doesn’t start, change, or stop workflows.
AI can make mistakes, so review findings before acting on them.
“Are any workflows suspended?”
“Give me a quick breakdown of workflows by status.”
“Summarize the errors found in the workflows you inspected.”
“Explain the error on the second workflow in that list.”
“Has its status or current step changed since we last checked?”
“Who started it, when, and what work-item information is available?”
“Show only workflow steps, not Tasks.”
“Is a model named Editorial Review available?”
AEM Dispatcher Insights aem-dispatcher-insights
The AEM Dispatcher Insights skill helps you understand how your Dispatcher and Apache web tier handle requests in AEM as a Cloud Service. Ask Coworker to analyze cache performance, investigate traffic and delivery issues, and review security configuration without manually searching log files. Where supported by the available data, Coworker can present findings as charts and request-timing visualizations.
For environment-specific analysis, identify the environment and time period (within a seven-day log window) you want to investigate. Currently, the skill does not access your source repository so for configuration and code reviews, paste or upload the relevant files. Coworker can also inspect reachable URLs to check response status, headers, and redirects.
Across these topics, you can ask Coworker to propose changes, explain their potential impact, and provide validation and rollback guidance. After you apply and deploy a change, ask Coworker to reassess the available logs or live URL behavior.
Currently, the skill does not modify your repository, deploy changes, publish or unpublish content, or clear caches. CDN cache purges, edge traffic-filter rule authoring, and changes to Adobe-managed infrastructure settings are outside its scope.
AI can make mistakes, so review findings and proposed changes before acting on them.
Caching and Performance dispatcher-caching-performance
Understand cache effectiveness, investigate slow or stale responses, and identify opportunities to reduce requests to publish.
“Cache performance dropped after our latest deployment. Compare the log evidence with recent deployments and the configuration diff I’ve shared.”
“Review why these GraphQL persisted-query responses are not being cached.”
“Which parameters can I safely ignore without breaking search or pagination?”
“Recommend a caching policy for our versioned client libraries and DAM assets using the configuration I’ve shared.”
“How would changing statfileslevel or gracePeriod affect invalidation, and when should we refresh a page’s cache?”
“For representative page requests, show the observed Dispatcher and publish processing stages and where time is spent.”
“Check whether this page is included in our sitemap and explain how sitemap coverage affects warm-up.”
Traffic and Request Handling dispatcher-traffic-request-handling
Understand the traffic reaching Dispatcher and investigate how requests are filtered, routed, and served.
“Is automated traffic being absorbed by the cache, or increasing requests to publish?”
“Which paths account for today’s 403 and 404 responses, and what evidence helps explain them?”
“Explain how rule ordering affects requests to our GraphQL endpoint.”
“Requests to our new domain are serving the wrong site. Check the host aliases and farm mappings I’ve shared.”
“This vanity URL works on publish but returns 404 through Dispatcher. What should I check?”
“Explain which headers belong in clientheaders.any and which are handled in the vhost or cache configuration.”
“How can I enable Dispatcher or rewrite debug logging in stage without changing production logging?”
Security dispatcher-security
Ask Coworker for an overall security review, or focus on a specific concern in your customer-controlled Dispatcher configuration and related AEM code.
“Can this endpoint’s allow rule be narrowed while preserving the required requests?”
“Explain the security benefits and potential application impact of the Content-Security-Policy change you recommend.”
“What should we verify to prevent unauthorized access when caching authenticated content?”
“Review these OSGi CSRF and CORS configurations alongside the Dispatcher rules I’ve shared.”
“Prioritize the findings by severity and recommend improvements within our control in AEM as a Cloud Service.”