Forming Prompts
Here are some best practices for using Hai and forming your prompts:
Try to keep conversations focused on a single topic at a time. Hai remembers the history of a conversation and incorporates it into future responses. If you want to switch topics, it's best to start a new discussion with clear context.
Hai performs automatic context extraction to load relevant context when matched. For example, when referring to vulnerability reports, prefix the report ID with a #. For example: #123456. See automatic context extraction below for details on supported patterns.
By default, the report you are currently viewing is included in the context (the report ID is displayed in the blue bubble at the bottom of the Hai sidebar). You can add up to five reports to the context window.
You can query analytical questions regarding your HackerOne program to Hai, but only within the Hai Analytics Play. This Hai Play has a different context loaded and is the only place to ask these questions.
You can ask Hai to email a conversation to someone within your organization. Just ask Hai to “Email this to me” or “Email this to user@examplecompany.com.” When initiated, Hai allows you to select which messages you want to include in the email. After confirming, the email will be sent. Hai will never initiate an email without explicit approval to take action.
When you encounter an issue with Hai, it’s always helpful to tell us what the conversation ID is. To get this, you can open Hai in a new tab and copy-paste the ID that is in the URL.
Automatic Context Extraction
When text matching any of the following patterns is included in your Hai message, it automatically loads the relevant object into the conversation's context.
Reports
Patterns matched (case insensitive):
#<id>
report <id>
vuln <id>
vulnerability <id>
issue <id>
reports <id>
Example: report #12345
Programs
Patterns matched: @<team_handle>
Example: @security
CWEs
Patterns matched: cwe-<number>
(case insensitive)
Example: CWE-200
CVEs
Patterns matched: cve-<year>-<number>
(case insensitive)
Example: CVE-2024-38206