# AI Assistant | HMI, Workflows and Custom Blocks

<figure><img src="/files/ESTocvz5xjG7tK7LC6tQ" alt="" width="250"><figcaption><p>AI Agent</p></figcaption></figure>

AugeLab AI is your in-app expert for features, troubleshooting, and workflow design. For the best results, always provide **Context** (Goal, Setup, Action, and Expected Result).

<details>

<summary>🛠️ Building Workflows &#x26; Scenarios</summary>

The AI builds better logic when it knows your environment and constraints.

* **Details to Include:** Input source (Camera/Folder), Output goal (Measurement/Detection), and Constraints (Target FPS/Accuracy).
* **Example Prompt:** > *Goal: Detect missing silver parts on a black conveyor belt moving at 0.2m/s. Setup: Windows 11, NVIDIA GPU, Basler camera. Expected: Recommended node sequence and tuning tips.*

<figure><img src="/files/ESTocvz5xjG7tK7LC6tQ" alt="AI Agent Interface" width="250"><figcaption><p>AI Agent Interface</p></figcaption></figure>

</details>

<details>

<summary>🧩 Designing Custom Blocks</summary>

Describe custom blocks like a "mini product spec" for the AI to generate the correct Python structure.

* **Details to Include:** I/O types (Image, Bool, etc.), user-adjustable parameters, and pass/fail logic.
* **Example Prompt:** > *Goal: Create a block that checks if a part is in a safe window. Input: Detection (x,y,w,h). Output: PASS/FAIL for HMI. Need parameters for tolerance and debounce.*

<figure><img src="/files/L9LDixmp9KKzP5u3J5KL" alt="Custom Block Creation" width="250"><figcaption><p>Custom Block Logic</p></figcaption></figure>

</details>

<details>

<summary>🖥️ Creating HMI Applications</summary>

Focus on **who** uses the screen and **what** decisions they need to make.

* **Details to Include:** Target device (Touchscreen/PC), essential glanceable data (Counters/Status), and required actions (Start/Stop/Reset).
* **Example Prompt:** > *Goal: Simple operator HMI for PASS/FAIL station. Needs a large status indicator and a reset button for alarms.*

</details>

<details>

<summary>🐞 Troubleshooting &#x26; Performance</summary>

To fix errors or "lag," the AI needs evidence.

* **For Bugs:** Provide exact error text, steps to reproduce, and logs.
* **For Performance:** Note which action is slow (e.g., "Inference taking 500ms") and your GPU usage.
* **Example Prompt:** > *Goal: Fix crash on Chat panel. Setup: Windows 11. Action: Clicked Chat menu. Result: App closed immediately. Log: \[Attached].*

<figure><img src="/files/pbxhkv9adlqwC0rzoLaL" alt="Troubleshooting with logs" width="250"><figcaption><p>Debugging with AI Agent</p></figcaption></figure>

</details>

<details>

<summary>📸 Effective Screenshots &#x26; Privacy</summary>

* **Capture the whole panel:** Show the selected node and the settings panel together.
* **Highlight:** Use arrows or circles to point at the specific error or missing button.
* **🔒 Privacy First:** Never share license keys, passwords, or sensitive customer data. Redact images before uploading.

</details>

***

### 💡 If the Assistant gets it wrong:

Don’t start a new chat. Provide a specific correction:

> *"That's not quite right. I'm specifically using the \[Panel Name] and the issue is \[X]. Please avoid using \[Node Y]."*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.augelab.com/key-features/ai-agent-usage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.