Conversations

Every exchange with an agent is a conversation, and conversations are saved automatically so you can close the page and continue later. This page explains how saving works, how to start a new conversation or resume an old one, the AI Conversations page, and what exactly is stored.

Automatic Saving

A conversation is saved after every completed reply, that is, each time the model answers without asking for further tools. Nothing is saved while tools are still running, and nothing is saved for a conversation in which you have not yet sent a message.

Each conversation records:

Field	Content
Title	Your first message in the conversation (up to 250 characters)
Created At / Last Active At	When the conversation started and when it was last saved
AI Provider and Model	The provider row and model used when the conversation was created
Scope	Which agent the conversation belongs to: `toolbox-al` for the coding agent, `toolbox-sql` for the SQL Agent (other Hougaard apps use their own scopes)
User	You. Conversations are personal; nobody else sees yours on the AI Conversations page

Conversations are stored per company. A conversation started in one company is listed and resumed in that company.

Starting a New Conversation

Choose New Conversation in the agent panel's actions.

The chat is cleared and shows the intro again.
Attached files are dropped.
The agent starts again from its instructions, so anything it learned in the previous conversation (your preferences, a table it looked up) is gone.
The previous conversation stays saved and can be resumed.

Start a new conversation whenever the topic changes. It keeps the context focused and reduces the amount of history sent with every message.

Resuming a Conversation

Choose Resume Conversation in the agent panel's actions.

A lookup opens listing your earlier conversations with this agent, newest first, with title, dates, provider, and model. Conversations of the other agent, of other Hougaard apps, and of other users are not shown.
Select one and choose OK.
The chat is rebuilt from the saved transcript: your messages, the agent's replies, the tool calls (shown as completed indicators with their parameters), and file bubbles for attachments.
Continue typing. The model receives the whole earlier conversation, so it remembers what was discussed and what its tools returned.

What a resumed conversation uses:

The provider and model it was created with. The conversation history is stored in that provider's request format, so it must continue on the same provider. The ToolBox looks up that provider's row on the AI Providers page and uses its current endpoint and key. If you moved the ToolBox Agent toggle to another provider in the meantime, the resumed conversation still runs on the original provider; new conversations use the new one.
The current instructions and tools. The agent's instructions and tool list are always the current version, so a conversation saved before an upgrade benefits from improved instructions.
The current editor. The agent reads the editor again with its "get" tool when you continue. It does not assume the program or statement is the one it left; if the editor changed, it works on what is there now.

If the conversation cannot be loaded (for example because it was deleted in the meantime), the message "The selected conversation could not be loaded." appears and the current chat is left untouched.

The AI Conversations Page

Search for AI Conversations in Business Central to open the list of all your saved conversations across both agents and any other Hougaard app agents in the environment.

Column	Meaning
Title	The first question of the conversation
Created At	When it started
Last Active At	When it was last saved; the list is sorted by this, newest first
AI Provider	The provider it was created with
Model	The model it was created with
Scope	The agent it belongs to

The page is read-only apart from Delete. Use it to clean up conversations you no longer need. Deleting a conversation removes its history and its attached files from the database; it cannot be resumed afterwards.

The same page opens, filtered to the current agent and without the Scope column, when you choose Resume Conversation in a panel.

What Is Stored

Conversations live in the AI Conversation table of the AL AI Services app (table 72214575), classified as customer content. Two blobs hold the content:

Conversation: the exact message history in the provider's request format. This includes your messages, the model's replies, every tool call with its parameters, every tool result (program source, statement text, table metadata, sample rows, console output, execution results), and any attached files encoded as text. It also records the model, whether tools were enabled, and the running token estimate.
Transcript: a display copy used to rebuild the chat when you resume: user and assistant messages, tool names with a short parameter preview, and file names.

Not stored: the agent's instructions (they are re-added from the current version on resume), API keys, and anything the agent did not receive through a tool.

Because tool results can contain business data, treat the conversation store as you would treat any table with customer content:

The AI Conversations page shows each user only their own conversations, but an administrator with table permissions can read all rows through other means, for example the Data Inspector.
Delete conversations that contain data you would not keep in a note.
Attached files are stored in full. Do not attach documents you would not upload to Business Central.

Cross-Agent Isolation

A conversation belongs to the app and the agent (scope) that created it. The Resume lookup only lists matching conversations, and the loader refuses a conversation with a different app or scope even if it is addressed directly. This means:

a SQL Agent conversation cannot be continued in the coding agent, and the other way round;
a conversation from another Hougaard app's agent (for example a spreadsheet agent) cannot be continued in the ToolBox;
moving the ToolBox Agent toggle between providers does not change which conversations you see.

Tips

Name your first message well. It becomes the title you search for later. "Customer balance report with Excel export" beats "hi".
Resume for follow-ups, new for new topics. Resuming keeps the agent's knowledge of the tables it already inspected; a new conversation is cheaper per message.
Delete large conversations. A conversation with many sample-row lookups or attached PDFs is large in the database and expensive to resume.
Provider changes are safe. Old conversations keep working on their original provider as long as that provider's row still exists with a valid key.