Feedback and support

Your feedback is essential to improving the Commerce Developer Agent. This guide explains how to report bugs, submit feature requests, share satisfaction ratings, and get help when you encounter issues.

Response times vary based on issue severity and team availability. For urgent access issues, escalate directly to your Adobe representative.

Before you report an issue

If you are unsure how to approach a workflow or prompt, try these resources before posting in the support channel:

Prompt crafting — covers effective prompting patterns for both workflows.
Capabilities and limitations — confirms whether what you want is supported.
Migration development
Net-new development

Support channel

For bugs, questions, and issues that are not resolved by in-product feedback, contact your Adobe support representative.

When posting in the support channel, include:

What you were trying to do — a brief description of your workflow.
What happened — the actual behavior.
What you expected to happen — the desired behavior.
Your session or project ID — ID that is visible in the Commerce Developer Agent URL or project header. This helps the support team find your session.
Screenshot or copy of the relevant output — if applicable.

Adobe representative

For access issues, escalations, or any urgent data or security concerns, contact your Adobe representative directly.

Report a bug

Reporting bugs helps make the Commerce Developer Agent better. Adobe considers a bug as any behavior that is incorrect, unexpected, or inconsistent with what is described in this documentation.

Include in your bug report:

Steps to reproduce - exact sequence of prompts or actions
What you expected to happen
What actually happened
Session ID or project ID - if available
Browser and OS - for UI bugs

Bug severity guidance:

Severity

Description

Examples

Critical

Completely blocks your workflow with no workaround

Cannot log in, blueprint approval crashes, no output is generated

High

Significantly impacts quality and the workaround is cumbersome or difficult

Generated workspace does not validate, incorrect App Builder extension structure

Medium

Impacts quality but functional

Minor generated-code issue with a workaround, a UI element not functioning as expected

Low

Cosmetic or minor issue

Typo in agent response, UI label inconsistency

For Critical or High-severity bugs, post a message in the support Slack channel and @ mention your Adobe representative, so your issue can be addressed quickly.

Submit a feature request

Feature requests can help shape the Commerce Developer Agent roadmap.

When submitting a feature request, describe:

The capability you want — what is the new functionality?
Your use case — what real project or scenario would this unlock for you?
Priority to you — how much would this improve your workflow?

Feature requests go into our backlog and are reviewed by the product team. Not all feature requests will be developed, but all feature requests will be considered.

What happens with your feedback

All feedback is reviewed by the Commerce Developer Agent team on a regular basis:

Bug reports — triaged based on severity. Critical and high-severity issues are prioritized.
Feature requests — reviewed monthly. High-frequency requests are flagged for the development roadmap.

You may be contacted by the product team to discuss specific feedback in more detail.