> For the complete documentation index, see [llms.txt](https://university.mindstudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.mindstudio.ai/building-ai-agents/blocks-reference/set-run-title.md).

# Set Run Title

Update the title in the user's history

The Set Run Title block updates the title that appears in the user's run history for a given Run. This makes it easier for users to identify and organize previous interactions, especially when agents are used repeatedly with different content or contexts.

***

## Configurations

### New Title

Define the custom title that should appear in the user’s session history. **You may include variables** such as `{{user_input}}`, `{{summary}}`, or any previously defined step output to personalize the title.

***

#### **Examples**

**Example 1: Personalized Summary**\
`Summary of conversation with {{user_name}}`

**Example 2: Workflow Context**\
`Invoice generated for {{client_company}} on {{current_date}}`

***

## How It Works

1. When the block is reached during execution, it updates the title of the current run session in the user’s history.
2. The new title will immediately be reflected in the Workspace or Extension history views.
3. If no variables are present, the block will use the static text as-is.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://university.mindstudio.ai/building-ai-agents/blocks-reference/set-run-title.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.