Back to Agent FAQs
HELP CENTER · FAQAgent1 min read

What should an agent include in a useful completion report?

A good report states what changed, where it changed, and how the result was checked. It should also call out incomplete work, assumptions, and any action that needs your review so you can decide what to do next.

Agent

Summarize changes with concrete references

Name the files, pages, records, or services affected and describe the outcome in terms of the original request. Separate completed changes from suggestions or follow-up work that has not been carried out.

Include evidence for claims such as a successful build, updated route, or saved configuration. A precise reference to the check performed is more useful than saying that everything works without showing what was inspected.

Make limitations and next steps clear

Report errors, skipped items, and uncertain results directly. If an action was blocked by missing access or information, explain what is needed and whether any dependent work remains unfinished.

Keep the report concise enough to scan but detailed enough to review consequential changes. Do not include secrets or copy full sensitive data into the summary; link or point to the protected result instead.

Back to Agent FAQs