To report incorrect results or bugs in DeepResearch, users can utilize built-in feedback tools, contact support directly, or engage with the community. The most straightforward method is using the “Report an Issue” feature within the DeepResearch interface, typically found in settings, help menus, or next to search results. This tool allows users to submit details about the problem, such as the query, unexpected results, and steps to reproduce the issue. For example, if a search returns outdated data, the user can flag the result and describe the correct information they expected. Submitting via this channel ensures the report is tagged with relevant metadata (e.g., browser version, query parameters), which helps developers diagnose the problem.
If the issue is complex or requires attachments (like screenshots or logs), users can email DeepResearch’s support team at a designated address (e.g., support@deepresearch.com). In the email, they should include a clear subject line (e.g., “Bug: Incorrect Citation Parsing in v2.1”), a detailed description of the problem, and any supporting files. For instance, if a user encounters a crash while exporting data, attaching console logs or error messages would help the team identify the root cause. Developers often prioritize reproducible bugs, so including steps like “1. Run query X, 2. Click Export PDF, 3. Error occurs” streamlines troubleshooting.
For technical users or open-source contributors, DeepResearch may host a public bug tracker (e.g., GitHub Issues) where issues can be reported and discussed. This platform allows transparency, collaboration, and status tracking. For example, a user might open an issue titled “API returns 500 error for large datasets” and include a code snippet to replicate the problem. The team (or community) can then propose fixes or workarounds. Regardless of the method, providing clear, specific details—such as software versions, user environment (OS, browser), and timestamps—ensures faster resolution.