Check that answers come from your files

When you're done, you've seen your Chirp answer from your files, and you know what to change if it doesn't.

Who can do this: the account owner on any plan, and workspace admins and editors.

Test it

1. Open the Chirp in the editor and click Save. The preview on the right uses your saved changes.

2. Ask the preview (beside the editor, or below it on a narrow screen) something only your files can answer, like a price, a policy or a step from your guide.

   

3. Check the answer against the file. The Chirp is told to mention the file name when it relies on one.

4. Ask something your files don't cover. It should say so rather than make something up.

The preview uses your OpenRouter key like any chat: see Test your Chirp in the preview.

The file labels under a reply

When a Chirp searches its files for passages, the names of the files it was given appear as labels under the reply. They show what the Chirp was given, not proof it used them. A Chirp that reads its files in full shows no labels. See How a Chirp uses its files.

If it doesn't use your files

• Tell it to. There's no separate setting: add a line to the instructions, such as "Answer only from the knowledge files. If they don't cover the question, say so and suggest contacting us." See Write instructions for your Chirp.
• Use your files' words. A Chirp with lots of text finds passages by the words in the question. Ask the way your visitors would, and add the words they use to your files.
• Check the file is there and readable. A scanned PDF or a picture of a price list has no text to read: see Which files work, and size limits.
• Publish what you tested. Visitors get changes to the instructions and the knowledge mode only after Publish changes (editors need the owner's permission to publish). Files apply right away.
• Try another model. Some models follow instructions and files more closely than others.