> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v20-zh-cn/parallels-desktop-for-mac-20-yong-hu-zhi-nan/zai-mac-shang-shi-yong-windows.md).

# 在 Mac 上使用 Windows

阅读本章来了解所有有关在 Mac 上使用 Windows 应用程序的信息。了解如何使用 Windows 应用程序，设定 Windows 应用程序如何与 macOS 协同工作，如何在 macOS 与 Windows 之间共享应用程序、文件与文件夹，如何连接设备、打印、自定义键盘，等等。


---

# 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.parallels.com/landing/pdfm-ug/v20-zh-cn/parallels-desktop-for-mac-20-yong-hu-zhi-nan/zai-mac-shang-shi-yong-windows.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.