Allure agent runs can now produce a human-readable report alongside the agent-focused artifacts. By default, allure agent and allure agent inspect use --report auto, which generates a single-file Awesome report for small result sets and skips it for larger runs to avoid excessive output.

Users can also explicitly disable report generation with --report off, force the single-file Awesome report with --report awesome, or run configured non-agent report plugins with --report config. Report status is recorded in the agent output so users and automation can tell whether a report was generated, skipped, disabled, or failed.

The CLI help, capabilities output, generated agent guidance, and docs now explain where to find the report from the most recent run. When a user asks for the report later, agents can recover the latest output directory and use manifest/human-report.json to open the existing report instead of regenerating it unnecessarily.