Steward memory and saved prompts¶

Two Steward settings help you avoid repeating yourself:

Memory is persistent context that Steward reads at the start of every session, such as your business context, naming conventions and known data quirks.
Saved prompts are reusable /slash commands that insert a ready-made request into the composer.

Availability

Who can do this: members with the Edit capability in the active Workspace.
Deployment: Actian SaaS and self-managed deployments. The web research step of /init isn't available on air-gapped self-managed deployments.

Memory and saved prompts belong to the Workspace. Everyone who uses Steward in the Workspace shares the same memory and the same saved prompts, and each Workspace has its own.

Note

Steward saved prompts are separate from the saved prompts that people use with AI Analysts in Explorer. See Saved prompts for AI Analysts.

Memory¶

Steward remembers what you've said within a session. Memory carries context across sessions, so you don't have to explain your business again each time.

Good things to keep in memory:

What your company does and the vocabulary your team uses
Naming conventions for models, dimensions and measures
Known data quirks, such as test accounts to exclude or a column that is misnamed
Business rules, such as how your team defines an active customer

We're a B2B SaaS company selling project-management software.
"Active customer" = at least one paid seat in the last 30 days.
Exclude accounts whose email ends in @example.com: they're internal test accounts.
Date columns end in _at (created_at, cancelled_at).

Don't store passwords, API keys, tokens or personal data in memory. Everyone with Edit in the Workspace can read it, and Steward reads all of it at the start of every session.

Edit memory¶

In Studio, open the Steward panel.
Select Steward settings (the cog icon) → Memory.
Edit the text. Memory is plain text, up to 100,000 characters.
Select Save memory.

When the save succeeds, you see Memory saved — recorded in the audit log. Saving replaces the whole memory with the text in the editor. Below the editor, Last updated shows when memory last changed.

Every change to memory, whether you make it or Steward does, is recorded in the audit log. See Audit logs for how to view it.

How Steward adds to memory¶

Steward can add to memory itself with the Save to memory tool, for example when you tell it a business rule or at the end of /init.

Steward adds new text on a new line. It never replaces or deletes what's already there.
Each addition can be up to 10,000 characters. If an addition would take memory over 100,000 characters, nothing is saved.
Steward saves to memory without asking for approval. Ask first has no effect for this tool.

To stop Steward from writing to memory, set Save to memory to Always deny under Steward settings → Tools. You can still edit memory yourself. See Approvals and tool permissions.

Tip

Review memory now and then. Remove anything that's out of date, because Steward reads all of it at the start of every session.

Set up memory with /init¶

/init is a built-in saved prompt for first-time setup. It asks Steward to:

Research your company on the web.
Ask you up to three questions about your data and business rules to start with.
Save what it learns to memory.

To run it:

Type /init in an empty composer and select it from the menu.
The prompt text replaces the composer, with [company name] selected. Type your company's name over it.
Send the message, then answer Steward's questions.

If web search isn't available on your deployment, Steward skips the research step. Web search is never available on air-gapped self-managed deployments. In that case, describe your company in your reply or add it to memory yourself.

Saved prompts¶

A saved prompt is a request you can insert with a / command, such as /validate-model. Use them for requests your team makes often.

Use a saved prompt¶

In an empty composer, type /. The saved prompts menu opens.
Keep typing to filter the list, for example /val. If nothing matches, the menu shows No matching commands.
Select a prompt. Its text replaces everything in the composer.
If the prompt has placeholders, the first one is selected. Type over it, then press Tab to move to the next one.
Edit the rest of the text if you want, then send it.

The menu opens only when your message starts with / and has no spaces, so you can't insert a saved prompt in the middle of a sentence.

Built-in saved prompts¶

Every Workspace has these built-in saved prompts. They're marked Default in the saved prompts list.

Command	Description	Tip
`/init`	Set the Steward up with context about your business	Replace `[company name]` before sending.
`/quickstart`	Quickly flesh out the model I have open	Open the model first and keep Context on.
`/expression`	Help write an expression for the selected entity	Open the dimension, measure, filter or metric, and replace `[describe what you want the expression to do]`.
`/create-metric`	Create a new metric step by step	Replace `[describe what you want the metric to measure]`.
`/validate-model`	Review the selected model for issues and improvements	Open the model first and keep Context on.
`/relationships`	Find relationships that might be missing	Works across all models in the Workspace.

For more on how Steward uses the page you have open, see Context.

Create a saved prompt¶

Open the Steward panel and select Steward settings (the cog icon) → Saved prompts.
Select Add prompt.

Fill in the fields:

Field	What to enter	Limits
Command name	The name you type after `/`, for example `monthly-review`.	Up to 64 characters of lowercase letters, digits and hyphens. Must be unique in the Workspace.
Description	What the prompt is for. Optional.	Up to 280 characters.
Prompt	The text inserted into the composer.	Up to 8,000 characters.

Select Create.

When you save, the command name is converted to the required format: capitals become lowercase, and spaces and other characters become hyphens. For example, Monthly Review is saved as monthly-review.

Creating, changing and deleting saved prompts is recorded in the audit log.

Add placeholders¶

To leave a value for people to fill in each time, wrap a name in double braces, for example {{metric}}. The dialog lists these under Placeholders. When someone inserts the prompt, each placeholder is selected in turn as they press Tab.

Placeholder names can contain letters, digits, underscores, dots and hyphens, for example {{fiscal.year}} or {{region_name}}.

Review the {{metric}} metric for {{fiscal.year}}.
Check its expression, its default filters, and whether its description
matches how the finance team defines it.

The built-in prompts use [square bracket] hints instead. In the composer they behave the same way (they're selected and Tab moves between them), but they aren't listed under Placeholders.

Customize a built-in prompt¶

You can't edit or delete a built-in prompt, but you can replace it with your own version:

In Saved prompts, find the prompt marked Default and select Customize.
The form opens with the built-in name, description and text filled in. Change what you need.
Select Create.

Your version keeps the same command name, so it replaces the built-in prompt for everyone in the Workspace. To go back to the built-in version, delete your custom prompt.

Edit or delete a saved prompt¶

In Saved prompts, next to a custom prompt:

Select Edit prompt (the pencil icon), change the fields, and select Save.
Select Delete prompt (the trash icon), then confirm. Deleting can't be undone.

Mention entities with @¶

In any message, type @ to mention a model, metric or glossary term. Steward searches your semantic layer as you type (Type to search models, metrics, and glossary terms), and inserts the name you pick.

Troubleshooting¶

Message or symptom	What it means	What to do
Memory is missing from Steward settings	You don't have the Edit capability in this Workspace.	Ask someone with Manage members and access for the organization, or a Workspace member who holds both Edit and Manage members, to give you Edit in this Workspace.
Couldn't save memory. Try again.	The save didn't go through.	Try again. If it keeps failing, check that you still have Edit in this Workspace.
A command name and prompt are both required.	Command name or Prompt is empty.	Fill in both fields.
Couldn't create the prompt. Try again. or Couldn't update the prompt. Try again.	The save failed. Common causes are a command name that's already used in the Workspace, a name longer than 64 characters, or a name with no letters or digits.	Choose a different command name, or edit the existing prompt instead.
`/init` doesn't research your company	Web search isn't available on your deployment.	Describe your company in the conversation, or add it to memory yourself.
Steward keeps forgetting a rule between sessions	The rule isn't in memory, or Save to memory is set to Always deny.	Add the rule under Steward settings → Memory.