Aura Trainer

Settings

Aura and Hermes

Connect the assistant, decide how Aura speaks, and keep the website free of secrets.

Environment

Development shows sample records marked Demo data. Production hides them. Status is never invented in either mode.

Hermes connection

This is the existing Hermes connection. It uses https://hermes.hartcoaurum.co.uk and does not start a second Hermes.

Press Save, then Test connection. The test calls GET /health on that address. Hermes is marked connected only when that check returns a healthy Hermes response and the API key is already stored. The key is not shown. Leave the key box empty to keep the saved key.

Preview uses a separate server variable named AURA_TRAINER_BRIDGE_KEY. Do not type that key into this page or into chat. Set it on the server that runs Aura Trainer, then press Preview again. The page never shows the value.

Aura settings

Personality and style shape replies written with Hermes. An approved answer is used in your words, unchanged.

Personality

Switches here are the same voice as Voice in the menu. Compare them before you save.

Open the voice bench

Conversation style

Master instruction

Connect website

The site at hartcoaurum.co.uk sends the customer's words here. This app talks to Hermes. The website is never given the Hermes key.

Aura API endpoint

Open this page to see the address.

Connection status follows the checks below. Website status is not connected until you test it.

<!-- Hartco Aurum — Aura chat connection.
     Call HartcoAura.send when a customer sends a message.
     Show data.reply to the customer.
     Keep data.conversationId and send it with the next message.
     Do not put a Hermes key, or any other secret, in the website. -->
<script>
  window.HartcoAura = {
    endpoint: "https://YOUR-AURA-TRAINER-ADDRESS/api/aura/chat",
    send: async function (message, conversationId, customerName) {
      var response = await fetch(window.HartcoAura.endpoint, {
        method: "POST",
        headers: { "Content-Type": "application/json" },
        body: JSON.stringify({
          message: message,
          conversationId: conversationId || null,
          customerName: customerName || "Website visitor"
        })
      });
      return response.json();
    }
  };
</script>

System status

A service is marked connected only after a check succeeds. Untested is not the same as connected.

Audit log

Knowledge, takeover, Hermes and instruction changes are recorded. Sign-in is not switched on, so opening this screen is not recorded as a login.

No actions recorded yet.

Setup guide

Step 1 — Publish Aura Trainer

You are in Aura Trainer now. This is the control centre.

When you want a permanent address, publish this app from Grok.

After it is published, open the published Aura Trainer and use that address from then on. Do not put the preview address on the live website.

Stay in Development until you have tested Hermes. Production hides the sample records.

Step 2 — Choose Development or Production

Click Settings in the left menu.

Find Environment.

Development shows sample records marked Demo data, so you can practise.

Production hides every demo record. Figures then come only from real conversations and knowledge you have approved.

Press Save environment.

You should see the word Saved under the button, and the mode named at the top of the screen.

Step 3 — Connect Hermes

“This device” in Hermes Desktop is not an address. Leave that connection as it is. Do not add another Hermes.

On the computer where Hermes already runs, the API server has to be switched on. Until then there is nothing for Aura Trainer to call. It listens only on that computer.

Aura Trainer is not on that computer. A private tunnel, such as Tailscale or an SSH tunnel, has to carry the existing API server out. Do not open it on the public internet.

Click Hermes Connection at the bottom of the left menu.

In Hermes API URL, paste the tunnel address of that API server. Do not paste 127.0.0.1. That address only works on the Hermes computer.

In Hermes API key, paste the API server key from that same installation.

In Hermes session ID, paste the existing Hartco Aurum Aura session. It cannot be discovered until the address and key work.

Press Save, then Test connection.

You should see Saved. The key stays on the server. After saving, the page shows only that a key is stored, plus the last four characters.

Hermes stays Not configured until the test succeeds. A desktop “Reachable” result does not change this.

Preview needs one more value, and it is not typed into this page.

On the server that runs Aura Trainer, set an environment variable. The name is AURA_TRAINER_BRIDGE_KEY. The value is the bridge key Hermes already uses. Do not paste it here.

Restart or republish Aura Trainer so the server can see that variable.

Open Settings, Hermes connection, and press Preview.

You should see Preview succeeded. If the variable is missing, Preview says it was not sent. If the value is wrong, Hermes answers 401. The key is not shown.

Step 4 — Test Hermes

On the same Hermes section, press Test connection.

You should see Connected, with the time of the check.

If you see Connection error, the address or the key was not accepted. The note under the button says which, and it does not put the key back on screen.

Hermes is never marked connected until this test succeeds.

Step 5 — Connect the website

In Settings, find Connect website.

Copy the Aura API endpoint shown there. It is your Aura Trainer address followed by /api/aura/chat.

Copy the code block under it.

On hartcoaurum.co.uk, that code is what the existing Aura chat should call when a customer sends a message. If someone else edits the site, send them the block.

The website sends the customer's words to Aura Trainer. Aura Trainer talks to Hermes. The website is never given the Hermes key.

Press Send test message.

You should see Aura's reply on this page, and a conversation named Connection test under Live Conversations.

Step 6 — Test Aura

Click Test Aura.

Type a question a customer might ask.

Press Ask Aura.

Read the reply, Knowledge used, and Source.

If it is right, press Good answer.

If it is wrong, press Needs improvement, type the answer she should give, press Save correction, then Approve & teach Aura.

Step 7 — Test a live-agent request

Click Test Aura, or use the chat on the website.

Type: I would like to speak to someone.

Open Live Conversations. You should see a banner: Live agent requested.

Press Take over chat.

You should see Human agent active, and a box where you can type. Aura will not answer this conversation while you have it.

Type a reply and press Send.

When you are finished, press Mark complete.

Press Yes — train Aura if the conversation should improve her, or No — close if it should not.

Step 8 — Correct Aura

Open the conversation and press Mark complete, then Yes — train Aura.

Check the customer question, Aura's original answer, and your answer.

Choose a category and a source.

Press Approve & teach Aura.

You should see the status Approved.

Nothing from a conversation becomes permanent knowledge until you press that button.

Step 9 — Approve knowledge

Click Knowledge Base.

Press Add knowledge.

Type the question a customer might ask, and the answer Aura should give.

Choose a category and a source.

Set status to Approved if Aura may use it now, or Draft if you are still writing it.

Press Save knowledge.

Approved entries can be used immediately. Draft entries are stored and are not used.

Step 10 — Check that Aura has learned it

Click Test Aura.

Ask the same question, in the words a customer would use.

Press Ask Aura.

Under the reply, Source should say Approved knowledge, and Knowledge used should name the entry you saved.

If it does not, the wording may be too different. Open Knowledge Base, press Edit, and phrase the question the way a customer would.

Step 11 — Check system status

Look at the bottom of the left menu, or open Settings and find System status.

Aura shows Online when this control centre can read its records.

Database shows Connected when that check succeeds.

Hermes shows Connected only after a successful test.

Website shows Connected only after you press Test website and hartcoaurum.co.uk answers.

If a line says Connection error, press Test connection on that line and read the note. The customer never sees that note.

Social media links

These links appear in the Trainer header and can be used by the API. Fill in your Hartco Aurum accounts.