Studio

Mind & knowledge: model, documents, memory and tools

Choose the AI model behind a digital employee, give it the documents its role needs, decide what it remembers, and enable only the connected tools that role may use.

These settings are what separate a chatbot from something useful. A character with no documents can only improvise; one with your price list, your policies and permission to call your booking system can finish a job.

In the character editor, the right dock's Mind & knowledge group holds Core AI, Knowledge Base, Personality, Memory, Mindview and Narrative. The Tool Registry tab sits in the Behavior group. Identity, voice, guardrails and emotion are covered in Identity, model & voice. Press Save in the toolbar (Ctrl/Cmd+S) after changing a tab; the file switches on Knowledge Base and the tool switches on Tool Registry take effect as soon as you flip them.

Core AI — the model

LLM Provider picks the family; Model picks the model within it. Choosing a provider resets the model to that provider's first entry, so check the Model list after switching.

Character editor with the Mind & knowledge panel open on the Core AI tab, showing the LLM Provider list with OpenAI selected.
The Core AI tab in the right dock's Mind & knowledge panel. Each LLM Provider card gives a short summary of its models; the highlighted card, here OpenAI, is the one the character uses. The list continues below Google Gemini.
LLM ProviderWhat you select
OpenAIAn OpenAI model for the standard conversation path.
OpenAI Realtime (voice)Native speech-to-speech: the model hears and speaks directly, with OpenAI voices.
Grok (xAI)A Grok model. For questions about your own website, use Experience rather than relying on the model.
AnthropicA Claude model for the standard conversation path.
Google GeminiA Gemini model for the standard conversation path.
Gemini Live (realtime)Native speech-to-speech with Gemini Live models and Gemini voices.
Ollama (local)Llama 3.2 or Qwen 2.5 through the Ollama service the IAMX server is configured with; this tab has no field for an Ollama address of your own. Needs a plan with the custom language model feature. Choosing it does not by itself make the rest of the conversation local or offline.

Models marked Premium consume extra quota (a plan multiplier). See Plans & usage.

Choosing a model

Start with a mini or flash class model. They are fast and cheap, and for a kiosk or an NPC the quality difference is far smaller than the latency difference. Move up to a flagship model only when you can point at answers that were not good enough.

Generation SettingsGuidance
TemperatureHow much the character varies its wording (0 to 1.5). 0.3–0.4 for banking and support, about 0.7 for a general assistant, higher for entertainment. Some models ignore it; the tab says so when that applies.
Max Tokens (per response)The reply length ceiling. 500–800 suits spoken conversation — long answers are tiring to listen to.
Prompt Window (context size)How many tokens the history, instructions and knowledge passages may use together: 4,000, 6,000, 8,000 or 16,000. Larger gives richer context at a higher cost.

File & image attachments lets visitors attach one image or document per message from the chat box. Switch Images (JPG, PNG, WebP, GIF) and Documents (PDF, TXT, CSV, MD, JSON, DOCX) separately and set Max size (MB); the hard limits are 5 MB for images and 10 MB for documents. Turned off, the attach button is hidden everywhere.

Test again after switching between standard and real-time models. They use different audio paths, and the Language & Voice tab changes with them. Recheck the voice, interruptions, document questions and the tools your character needs, and do not assume usage or response time stay the same.

Knowledge Base — what it can look up

Documents live in one library shared by your whole workspace (Knowledge › Knowledge Base in the top bar). Each character is then given permission to read specific ones on its own Knowledge Base tab, titled "Knowledge base for this character". A price list can serve five characters without being uploaded five times, and your internal HR policy can stay away from the character on your public website.

The character's Knowledge Base tab with an upload box above a Library list in which a sample FAQ file is marked Ready and switched on.
The character's own Knowledge Base tab. Knowledge base for this character counts the files it may use, files dropped on the upload box are enabled for this character at once, and each file under Library shows its status (here Ready) and its own switch. Open tenant library leads to the workspace page.
What you can uploadLimit
PDF, Word (.docx), plain text, Markdown, CSV50 MB per file
Images — JPG, PNG, WebP (the text in them is read)
  1. Drop the files onto the tab. Files you upload here are enabled for this character straight away; they also join the workspace library. Files count against your plan's Knowledge storage; when it is full, or your plan includes none (Free), the upload is refused.
  2. Wait for Ready. Each file shows Processing while it is read and indexed. The list refreshes by itself; a file that cannot be read shows Failed.
  3. Check the switches under Library. Every file in the workspace is listed with a switch ("Use … for this character"). Turn off anything this character has no business quoting. A disabled file stays in the library.
  4. Test it. Type a realistic customer question into Search Test and press Search (or Enter). You see the passages the character would find, each with a similarity score.
A file uploaded on the workspace Knowledge Base page is not enabled for any character. Come to each character's Knowledge Base tab and switch it on. Uploading from inside the character, as above, does both steps at once.
If Search Test returns nothing at all, check that at least one file is both Ready and switched on. With no enabled files the character skips the search entirely. The knowledge search runs in the standard conversation path; a character on Gemini Live (realtime) or OpenAI Realtime (voice) does not search these files.

More on formats, storage and writing documents that retrieve well: Knowledge Base.

Personality

Six Preset temperaments — Custom, Friendly, Professional, Creative, Witty and Empathetic — set the five Big-Five Traits at once: Openness, Conscientiousness, Extraversion, Agreeableness and Sensitivity, each 0–100. Pick the preset closest to your intent — Friendly for a greeter, Professional for banking or support, Empathetic for care and health — or choose Custom and move the sliders.

Personality shapes the general temperament. For a specific voice — a catchphrase, a habit, a way of deflecting a question — write it into Background / Persona and Example Dialogues on the Identity tab. Those fields do far more work than any slider.

Memory — who it remembers

With Long-term Memory enabled, the character carries what it learned about a person into their next conversation — a returning customer is greeted with real recall and does not have to explain their situation twice.

SettingWhat it does
EnabledOff, every session starts from scratch.
Retention Period (days)Records older than this are not recalled.
Share across charactersOther characters in your workspace also recognize this person.

While memory is on, each completed exchange is added to that visitor's record, from every client — website embed, kiosk, Unreal or phone. A background job then condenses the exchanges into a short summary and a few facts (a name, preferences, decisions, plans). Current Records lists each visitor with their summary, recent exchanges and facts; it refreshes by itself, or press Refresh.

The Memory tab with Long-term Memory enabled, a Retention Period of 90 days, Share across characters switched off and an empty Current Records list.
The Memory tab: Enabled is on with a 90-day Retention Period (days), and Share across characters is off, so only this character recognizes a returning visitor. Current Records stays empty until the first exchange completes; Refresh reloads it.
How well a person is recognized depends on how the client identifies them. Recognized visitors — for example people identified by FaceID on a kiosk — can be remembered across visits; unidentified visitors get separate session records. Switch memory off for a public demo where visitors should stay anonymous.
Turning memory off stops new exchanges being stored and stops records being used, but it does not erase what is already stored. Bear that in mind when a visitor asks you to forget them.

Mindview — see what the character is told

Mindview answers the question "why is it behaving like that?". Type a test message, press Inspect, and the character's instructions are laid out by origin — Persona, Guardrails, Personality, State of Mind, Long-term Memory, Knowledge (RAG), Current Narrative Section and Tool Manifest — each with a character count, so you can see what dominates.

It is the fastest way to catch the common mistakes: a guardrail that contradicts the persona, an example dialogue that never got saved, or a tool you thought was enabled and isn't.

Memory and knowledge passages are looked up live during a real conversation, so those sections show a placeholder here. Current Narrative Section also shows a placeholder: in the current version conversations do not follow the narrative graph (see Narrative). Check knowledge with the Knowledge Base tab's Search Test. Mindview is a plan feature: without it the tab shows a padlock and opens Plan & Quota.

Narrative — guide the conversation

The Narrative Graph maps a conversation as connected nodes: add Start, Section, Trigger and End nodes, drag them into place and connect them, then select a node to edit its Name and Content. Narrative is a plan feature. See Narrative for how sections and triggers work.

Tool Registry — what it can do

A tool is a real action: check a balance, look up an order, call your own API. You define it once for the workspace under Knowledge › Tool Registry, then decide here which characters may use it. When the conversation calls for it, the character decides to call the tool itself, uses the result, and answers in its own words.

  1. Open Behavior › Tool Registry. Every workspace tool is listed with its category badge; tools marked Identity required only run for a verified person.
  2. Switch on the tools this character may use. A tool that is not switched on is invisible to the character. New tool and each tool's edit icon open the tool form.
  3. Start a fresh conversation and try it. The tool list is handed to the character when a conversation begins, so one already in progress will not see a newly enabled tool.
  4. Check Knowledge › Tool Registry › Execution Log for the audit trail.
The Behavior panel's Tool Registry tab listing two sample tools, book_demo and check_order_status, each with a category badge, a switch turned off and a gear icon, under a New tool button.
Behavior › Tool Registry for one character. Both sample tools are switched off here, so this character cannot call either until you flip its switch. The badges (ASSISTANT, EXTERNAL_API) show each tool's category, and New tool opens the tool form.
Your endpoint must be on the public internet. A tool pointing at localhost or an address on your office network is refused deliberately — otherwise a character could be talked into probing private infrastructure. Self-hosted automation needs a public address or a tunnel. Defining tools, templates and security: Tool Registry.

Where to go next

Connect an API

Tool Registry →

IAMX AI STUDIO