> 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-life.md).
# 日常动作、注视与打盹
Nora 的日常动作让陪伴有变化，但不会因为一条未读消息持续占用某个表情。
{% columns %}
{% column width="50%" %}
清醒状态。
{% endcolumn %}
{% column width="50%" %}
打盹状态。
{% endcolumn %}
{% endcolumns %}
## 日常会看到什么
* 空闲时有张望、轻微点头等日常动作；不同性格影响节奏和幅度。
* 鼠标在附近时可以有注视反馈，离开后回到自然位置。
* 触碰或悬停可以获得短暂回应，结束后回到日常姿态。
* 打盹是陪伴状态，不代表任务失败，也不能据此判断同步已完成。
* 拖动、窗口不可见或系统要求减少动态效果时，表现会安静下来。
## 表情不是任务状态栏
思考、工作、撰写、审阅与完成提供短暂反馈，之后恢复日常姿态。待填写、待确认、失败或离线的具体信息从消息和未读标记查看。
看见 Nora 回到平常表情，不代表刚才的任务已经结束；看到打盹也不表示电脑已经完成“30 分钟同步待机”。同步状态有独立条件与提示。
这些动作自身不需要为每次张望调用模型，也不表示它持续截取桌面。视觉观察仍按你的请求及对应权限处理。
***
返回[桌面宠物与陪伴](/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-life.md?ask=&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.
