> 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/pet/pet-controls.md).

# 移动、快聊与唤回窗口

把 Nora 放在手边，随时展开对话，需要更大的工作区时再回到主窗口。

## 常用操作

| 操作                | 实际用途                    |
| ----------------- | ----------------------- |
| 拖动 Nora           | 调整桌面位置，避免遮挡正在看的内容       |
| 双击 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="桌面快聊保留历史入口、图片输入与返回 Evolv 的入口。"><figcaption><p>桌面快聊保留历史入口、图片输入与返回 Evolv 的入口。</p></figcaption></figure>

## 内置与桌面怎样切换

可以从“放到桌面”等入口或“设置 → Nora 伙伴”启用桌面陪伴，返回时继续原会话、任务和待确认事项。主窗口与桌面不应出现两套独立可操作的会话。

关闭或隐藏一个窗口不一定意味着软件已经退出。想停止后台工作，使用明确的任务停止或应用退出方式，并核对当前状态。

***

返回[桌面宠物与陪伴](/ray_evolv-docs/pet.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/pet/pet-controls.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.
