> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/communication-and-human-input/update-conversation-title.md).

# Update Conversation Title

Set a recognizable title for the current conversation so users can find it in their history.

## Name the conversation

1. Pass a concise description of the conversation to **Conversation Title**.
2. Run the action within that conversation.
3. Check **Success** and confirm the updated title in conversation history.

**Result:** The title of the current conversation changes when the update succeeds.

## Behavior and troubleshooting

The title is limited to 200 characters; longer text is truncated. This action renames the current conversation, not an arbitrary conversation selected by ID. Avoid putting sensitive content in titles that are visible in history.

## Inputs

| Field                         | Parameter | Description                                                                            |
| ----------------------------- | --------- | -------------------------------------------------------------------------------------- |
| Conversation Title (required) | `title`   | The new title for the conversation. Will be automatically truncated to 200 characters. |

## Outputs

| Field           | Parameter         | Description                                             |
| --------------- | ----------------- | ------------------------------------------------------- |
| Success         | `success`         | Whether the conversation title was updated successfully |
| Conversation ID | `conversation_id` | The ID of the conversation that was updated             |

## Related guidance

[Human Input and Approval Controls](https://docs.stackai.com/technical-reference/interfaces-and-conversations/human-input-and-approval-controls.md)


---

# 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://docs.stackai.com/stackai-tools/communication-and-human-input/update-conversation-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.
