> 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/get-started.md).

# 开始使用

Convai Playground 首要步骤的引导式概览，包括导航、角色创建、测试和基本全局控件。

## 简介

## 欢迎来到 Convai Playground！

用于创建、自定义和测试 AI 驱动角色的工作空间。此页面为你提供核心工具和工作流程的高级概览，帮助你快速上手并提高效率。下面的每个部分都链接到一个专门页面，你可以在那里深入了解。

## 前置条件

* 一个 Convai 账户。

## 核心概念

* **Character** – 你创建并自定义的 AI 角色，拥有独特的人格特征、语言、知识和行为设置。
* **Avatar Studio** – 一个无代码编辑器，你可以在其中设计角色的视觉外观并配置其 **Avatar Studio 体验**，包括环境、动画、交互设置等。

## 快速入门流程

* **仪表板概览**\
  了解界面布局，查看你最近的角色和体验，并了解在哪里创建新的角色或 Convai Simulation Experience。\
  继续： [*仪表板概览*](/api-docs/zh/convai-playground/get-started/dashboard-overview.md)
* **创建新角色**\
  通过为你的 AI 角色命名、定义其描述、选择语言和声音，以及设置其人格来开始构建。\
  继续： [*创建新角色*](/api-docs/zh/convai-playground/get-started/creating-a-new-character.md)
* **测试角色**\
  使用 **聊天框** 进行文本和语音交互，或通过 **视频通话** 获得更具沉浸感的体验。\
  继续： [*测试角色*](/api-docs/zh/convai-playground/get-started/testing-a-character.md)
* **全局角色控制**\
  了解所有角色页面中可用的工具，例如版本管理、更新和角色设置。\
  继续： [*全局角色控制*](/api-docs/zh/convai-playground/get-started/global-character-controls.md)
* **角色版本管理**\
  保存并在角色的不同版本之间切换，以便安全地进行实验和迭代。\
  继续： [*角色版本管理*](/api-docs/zh/convai-playground/get-started/character-versioning.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.convai.com/api-docs/zh/convai-playground/get-started.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.