> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/convai-playground/character-customization/state-of-mind.md).

# 心境

了解“心境”功能如何在对话过程中实时可视化 AI 角色的情绪状态。

## 简介

该 **心境** 该部分提供了您 AI 角色当前情绪状态的可视化表示。这个动态情绪图可帮助您了解角色在对话中的内部反应，从而微调其个性和互动风格。

<figure><img src="https://2402152281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEtUJA212Zc1S9ACc8T4l%2Fuploads%2Fqddr79VtWV28ApwXffHo%2Fimage.png?alt=media&amp;token=cd4b16d1-5d0d-4019-8eca-d5bb24938995" alt=""><figcaption></figcaption></figure>

***

## 工作原理

* 心境界面显示一个 **按颜色编码的情绪轮**.
* 每个区块代表一种特定情绪，例如 **喜悦、愤怒、信任、恐惧、惊讶、悲伤、厌恶、** 和 **期待**，以及更细微的变化，如 **宁静、狂怒、钦佩、** 和 **惊奇**.
* **当前活跃情绪** ——即角色当前正在体验的情绪——会在图表上以更亮的颜色突出显示。
* 情绪会根据对话的上下文、语气和内容动态变化。

<figure><img src="https://2402152281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEtUJA212Zc1S9ACc8T4l%2Fuploads%2FKfyxRahyHKL0i4tDh2RX%2Fimage.png?alt=media&amp;token=5d2930e1-216d-4c16-908c-584e69322c5d" alt=""><figcaption></figcaption></figure>

***

## 实际使用场景

* **角色测试：** 观察实时情绪反应，以验证角色是否按预期作出回应。
* **个性调校：** 在以下部分中调整个性特征 **个性特征** ，并查看它们如何影响情绪模式。
* **故事叙述与角色扮演：** 确保交互式叙事中的情绪一致性。

***

## 结论

心境功能为您 AI 角色的情绪行为提供了宝贵见解。通过监控这些实时情绪变化，您可以确保角色以符合其设计个性和预期使用场景的方式作出回应。


---

# 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.convai.com/api-docs/zh/convai-playground/character-customization/state-of-mind.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.
