> For the complete documentation index, see [llms.txt](https://docs.xunda.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xunda.ai/documentation/xunda-browser-manual/features.md).

# 3. 软件功能说明

读表方法：每项均按「功能 → 作用 → 使用方法及对应截图 → 前提或限制」排列。入口名称随版本变化时，以页面实际文案为准。「待补」表示没有对应实拍；列出可参考的列表图不代表编辑、提交、删除已实测。

## 功能目录

* [3.1 团队与账号](/documentation/xunda-browser-manual/features/team.md)
* [3.2 AI 模型与任务默认设置](/documentation/xunda-browser-manual/features/models.md)
* [3.3 浏览器环境](/documentation/xunda-browser-manual/features/environments.md)
* [3.4 任务与对话](/documentation/xunda-browser-manual/features/tasks.md)
* [3.5 技能、连接器与扩展](/documentation/xunda-browser-manual/features/skills.md)
* [3.6 自动化与任务工作栏](/documentation/xunda-browser-manual/features/automation.md)
* [3.7 设置、数据与维护](/documentation/xunda-browser-manual/features/settings.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.xunda.ai/documentation/xunda-browser-manual/features.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.