Asset Debugger

On the Assets page, you’ll find a Debug button — clicking it opens the Asset Debugger. This tool allows you to test the knowledge stored within your assets by entering keywords or specific questions. The debugger will return a list of relevant content pulled from the assets, along with their exact sources.

This feature is especially useful for ensuring Aissistant responds accurately and consistently. Below are common scenarios where the Asset Debugger can help:

🔍 Key Use Cases for the Asset Debugger

Verify Content Availability Ensure Aissistant is actually able to access and retrieve information from your assets. Some websites or documents may be restricted by firewalls or permissions. The debugger reveals what content is retrievable so you can adjust sharing settings if necessary.
Check Information Accuracy Test questions like "What is our return policy?" to see if Aissistant provides the correct response. If the answer is outdated or incorrect, you can update the source document accordingly.
Spot Conflicting Information Ask something like "What’s the price of Product X?" If multiple sources return different prices, the debugger helps you trace where the discrepancies are and resolve them.
Identify Inconsistent Responses Try entering "What are the troubleshooting steps for Setup A?" If different sources give varying (but technically correct) answers, you can unify the instructions to improve consistency in responses.
Audit Asset Coverage Check whether specific topics (e.g., refund eligibility, warranty details) are covered at all. This helps identify knowledge gaps that need to be filled.
Pre-test Sub-Agent Assets If an asset is linked to a sub-agent, use the debugger to confirm the asset includes all the necessary context for that scenario before deploying it live.
Improve Response Clarity Review how information is structured in the retrieved content. If responses feel cluttered or unclear, consider editing the asset to be more concise or reorganized for better readability.

PreviousDocuments NextCreate Sub Agents

Last updated 1 month ago

This feature is especially useful for ensuring Aissistant responds accurately and consistently. Below are common scenarios where the Asset Debugger can help:

🔍 Key Use Cases for the Asset Debugger

Verify Content Availability Ensure Aissistant is actually able to access and retrieve information from your assets. Some websites or documents may be restricted by firewalls or permissions. The debugger reveals what content is retrievable so you can adjust sharing settings if necessary.
Check Information Accuracy Test questions like "What is our return policy?" to see if Aissistant provides the correct response. If the answer is outdated or incorrect, you can update the source document accordingly.
Spot Conflicting Information Ask something like "What’s the price of Product X?" If multiple sources return different prices, the debugger helps you trace where the discrepancies are and resolve them.
Identify Inconsistent Responses Try entering "What are the troubleshooting steps for Setup A?" If different sources give varying (but technically correct) answers, you can unify the instructions to improve consistency in responses.
Audit Asset Coverage Check whether specific topics (e.g., refund eligibility, warranty details) are covered at all. This helps identify knowledge gaps that need to be filled.
Pre-test Sub-Agent Assets If an asset is linked to a sub-agent, use the debugger to confirm the asset includes all the necessary context for that scenario before deploying it live.
Improve Response Clarity Review how information is structured in the retrieved content. If responses feel cluttered or unclear, consider editing the asset to be more concise or reorganized for better readability.