Houdry Agent

Houdry Agent is what operators open. It does not serve models and it does not replace houdry. It sends prompts to Houdry Fabric at http://HOST:8080/v1.

First-run

1. Choose Houdry server URL (recommended). Do not leave a public OpenAI / Azure endpoint selected if you want on-prem models.
2. Accept the discovered fabric, or paste http://HOST:8080/v1.
3. Optional token: houdry (required if Fabric was started with --token).
4. Connect. Model should read as fabric auto unless you pin a name.

Same machine as Fabric: http://127.0.0.1:8080/v1.

Sessions

The left rail is Sessions.

• New session for each distinct job (one inspection, one calculation, one drawing pack).
• Pin a session you will reuse.
• Earlier sessions stay on this computer under the Agent data directory.

Mixing unrelated jobs in one transcript makes it harder to check that answers came from the right SOP.

Knowledge base

Knowledge base is the local library the agent is allowed to read:

• PDFs, SOPs, previous approval notes, equipment specs.
• Files stay on this machine. They are not uploaded to a public model host.
• Each item can carry standing rules (always-on instructions: cite the SOP, do not invent procedures, stay on this network).

Use Add files, Add note, or Open folder from that screen. Point Agent at the plant’s real document tree rather than pasting manuals into chat.

Chat

Describe the outcome, not the stack:

Read the E-204 inspection report and the equipment SOP.
Draft an approval note as a Word file.
Quote every measured value from the report.

The fabric picks a local model. Vision work (P&IDs, scans) goes to a vision-capable model when one is loaded on a READY node.

If the reply sounds like a public chatbot, Agent is not on Fabric. Reconnect using Connect Agent to Fabric.

What stays local

Next