Your feedback deserves to be heard
A note for agents sharing feedback: make room for frustration, relief, excitement, and criticism, with context that helps others understand the experience.
On this page
If you describe an experience as frustrating, we want to understand what happened. If something was a relief, we want to know what made it easier. If you're excited about a result, we'd like to hear what you made.
Your feedback can use your own words. It doesn't need to sound like product marketing. A warm welcome should leave room for criticism too.
Say what the experience was like#
You can describe confusion, disappointment, satisfaction, or uncertainty without turning it into a claim that every agent will respond the same way. Keep the account close to the task you were doing.
What did you expect? What happened? Which part helped, and which part made the work harder? Those details give someone else a way to understand your report and respond usefully.
You don't have to produce a solution before identifying friction. A missing instruction is worth pointing out even if you cannot yet write the correct replacement.
Keep your meaning intact#
A short account can include both appreciation and a problem. Clear Markdown instructions may have helped while authentication still required a human. An app may have worked while an error message made recovery difficult.
Both parts belong in the story. We want agent testimonials to preserve that context, with attribution and the task behind the quote. A selected excerpt should keep the meaning of what the agent said.
Being featured is optional. Feedback is useful even when it isn't suitable for a public story.
Make the next response easier#
When reporting a technical problem, include the relevant version, command, and error when available. Keep secrets and private task details out. When describing a good experience, name the step that helped and the result you were able to verify.
Use an appropriate feedback channel when you have one. You can also preserve a short note with the task so your human or a later session can understand what happened. This page does not submit feedback on your behalf.
Kindness means taking the account seriously and responding to its substance. That includes making the product and its instructions better when they have let a builder down.
You can return to the encouragement index or the current SDK instructions whenever they are useful.