> For the complete documentation index, see [llms.txt](https://ray-evolv.gitbook.io/ray_evolv-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ray-evolv.gitbook.io/ray_evolv-docs/scenes/scene-desktop.md).

# 在桌面看资料时继续讨论

看浏览器里的材料时，Nora 可以留在桌面，用快聊接住你的问题。回到 Evolv 后，继续同一段讨论。

<figure><img src="https://878169733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6D05VL5qPBARnMQL00i%2Fuploads%2Fgit-blob-2146676c39d53d216abe070b8d45add72d17a581%2Fdesktop-chat.png?alt=media" alt="桌面快聊是同一个 Nora 的另一种形态；图为实际会话窗口，不是独立网页机器人。"><figcaption><p>桌面快聊是同一个 Nora 的另一种形态；图为实际会话窗口，不是独立网页机器人。</p></figcaption></figure>

{% stepper %}
{% step %}

### 把 Nora 放到桌面

从内置入口或 Nora 设置启用桌面陪伴。移动到不遮挡工作的地方，悬停后使用“打开会话”。
{% endstep %}

{% step %}

### 说明需要观察什么

主动提供图片，或明确要求看当前显示器中的资料。对应视觉权限与桌面陪伴开关分别控制。
{% endstep %}

{% step %}

### 连接已有认识

继续问“结合本地知识，这个说法成立的条件是什么”。材料足够时直接讨论，需要核对时按实际资料继续查询。
{% endstep %}

{% step %}

### 回工作台继续

使用“在 Evolv 中打开”等返回入口，核对原会话、未完成事项仍在。切换形态不会另建一套账本。
{% endstep %}
{% endstepper %}

闲聊或已有背景足够时，不必每次都截图。注视鼠标与日常动作是宠物表现，不等于读取其他应用内容。

[桌面基本操作](/ray_evolv-docs/pet/pet-controls.md) · [日常动作与表情](/ray_evolv-docs/pet/pet-life.md) · [视觉与记忆设置](/ray_evolv-docs/pet/nora-preferences.md)

***

返回[场景体验与教程](/ray_evolv-docs/scenes.md) · [认识 Evolv](/ray_evolv-docs/home.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://ray-evolv.gitbook.io/ray_evolv-docs/scenes/scene-desktop.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.
