Reference for the ChatClear Display action — clears the per-Display-panel conversation transcript for a named chat session without invoking the LLM.

AI Integration → Local AI → ChatClear Action Reference

Purpose

ChatClear is a Display Action that wipes the conversation transcript held for a specific (clientGuid, chatName) pair on the server side. No LLM call is made. The action is synchronous, returns immediately, and is idempotent — clearing an already-empty transcript is a no-op that still returns status="ok".

Use it to give operators a “Start new conversation” button: one press discards all prior turns so the next ChatRequest starts with a blank transcript rather than inheriting context from the previous session.

When to use

  • Shift handover — when a different operator takes over, clear the prior operator’s chat context before handing off the panel.
  • Topic switch — when the conversation has drifted off-topic and the operator wants to start fresh without carrying prior assumptions into the next query.
  • Testing and development — reset the transcript between test runs without restarting the runtime or reloading the Display.
  • Privacy — prevent the next operator from seeing the previous operator’s questions and replies in the same chat panel.

The login-change reset built into ChatRequest (lazy reset on the next turn after a user change) is distinct from ChatClear. ChatClear is operator-initiated and immediate; the login-change reset is platform-initiated and lazy. Both result in an empty transcript for the next turn.

How it works

When fired, ChatClear resolves the target chat session and removes its transcript from the server-side in-memory transcript cache:

  1. The Object field (if set) names the target TChatSession control. If the field is empty, the platform walks the visual tree of the active Display panel and targets the first TChatSession it finds.
  2. The resolved target provides the (clientGuid, chatName) key. The server drops the transcript entry for that key.
  3. The reply envelope is returned to the Return tag (if configured) with status="ok", text="", and empty toolTrace[] and warnings[] arrays.

Because no LLM call is made, the action typically returns in under a millisecond. It does not appear in tool traces and does not count against the tool-dispatch cap.

Configuration

On a Button (or any clickable control), add an Action dynamic with:

Field

Setting

Action type

ChatClear

Object

Name of the target TChatSession control on the same Display. Leave empty to auto-resolve to the first ChatSession control found in the visual tree.

Return

Optional tag that receives the reply envelope JSON. Useful for diagnostics or confirmation UI. May be omitted for a simple “clear and forget” button.

Result 1, Result 2, … (optional)

Tags computed from the reply via Expressions — for example, @Tag.ClearStatus.JsonString("status") to surface a confirmation badge.

Query

Not used by ChatClear. The action takes no user input.

The Action editor hides fields that do not apply to ChatClear. The Query field is hidden; Object, Return, and Result/Expression rows surface.

Reply envelope

The reply envelope follows the same JSON schema as ChatRequest and AI.Execute — see Local AI Reply Envelope Schema for the full field reference. For ChatClear specifically:

{
  "text":      "",
  "status":    "ok",
  "toolTrace": [],
  "latencyMs": 0,
  "warnings":  []
}

text is always an empty string — there is no LLM output. latencyMs reflects the wall-clock time for the transcript-drop operation, which is normally sub-millisecond. toolTrace and warnings are always empty arrays on a successful clear.

Gates

ChatClear checks a single gate before executing:

  • SolutionCapabilities[LocalAI].Enabled must be true — the master Local AI kill-switch. When disabled, ChatClear returns status="disabled" without touching the transcript cache.

Unlike ChatRequest, ChatClear does not inspect ModelOptions tool-surface bits. Those bits control LLM dispatch; transcript management is independent of the LLM configuration.

Target resolution

ChatClear resolves the target chat session in two steps:

Path

When used

Behavior

Path A — explicit name

Object field is set to a non-empty value

The platform resolves the named element on the active Display panel. If no control with that name exists, the action returns an error envelope.

Path B — visual-tree walk

Object field is empty

The platform walks the visual tree of the active Display and targets the first TChatSession control found. Sufficient for Displays with a single chat control. On Displays with multiple ChatSession controls, always use Path A to avoid ambiguity.

See also

In this section...