Speaking instructions to Brainfish while you record

When you record a video and upload it to Brainfish to generate knowledge base articles, you can talk directly to Brainfish while you record. Those spoken lines are treated as instructions for the article, not as content to publish.

How it works

Record with any tool you already use (Loom, Zoom, OBS, your phone, etc.). Upload the file to Brainfish as usual. While you demonstrate, say what you want the article to do—for example:

• “Hey Brainfish, don’t include these steps in the article.”
• “Brainfish, only document the export flow.”
• “Skip the login section in the article, Brainfish”
• “In the article, call this feature ‘Quick Export’ instead of the name on screen, Brainfish”

Brainfish applies those directions when writing the article: what to include, what to leave out, and how to phrase things, even if that part still appears on screen in the video.

Best practices

Be clear and specific. Short, direct instructions work best. Say what to omit, what to focus on, or how you want something named in the article.

Say “Brainfish” when you mean the system. Addressing Brainfish (e.g. “Brainfish, skip…”) helps the brainfish system treat the line as an instruction, not as product documentation.

Give instructions when it matters. You don’t need to narrate every step. Use spoken directions when the video shows more than you want in the article (setup, internal tools, one-off troubleshooting, etc.).

Separate “for the article” from “for the viewer.” Explain the demo for your audience as normal; add a quick Brainfish line when you want the written article to differ from what’s on screen.

Use your Knowledge Creation Template when you have one. If your workspace has Article Format Instructions or a sample article, those still apply. Spoken instructions work alongside them; where they conflict, your template rules take precedence.

What this is not

• Spoken instructions are not a substitute for a good demo. The model still needs enough context in the video to write accurate steps.
• Spoken lines are not copied into the article as quoted dialogue unless that’s appropriate for your content.

Quick example

You record a full walkthrough including internal admin setup, then say:

“Brainfish, don’t include the admin setup—only document how customers export their report.”

The generated article should focus on the export flow and omit the setup section, without treating “Brainfish” as the topic of the article.