> 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/v27-zh-tw/parallels-desktop-for-mac-27-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/she-ding-windows-ru-he-shi-yong-macos.md).

# 設定 Windows 如何使用 macOS

Parallels Desktop for Mac 讓您可以在 Windows 與 macOS 之間無縫操作。例如，您可以在兩個系統之間剪下和貼上文本以及共用檔。

您可以用許多種方式設定 Windows 與 macOS 之間集成的程度。例如，您可能希望 Windows 應用程式可以表現得像 Mac 應用程式一樣，並且一同出現在 Mac 桌面上。或者您也可能希望將 Windows 桌面與應用程式保持在一個單獨的視窗中。

請繼續往下閱讀，瞭解更多有關設定 Windows 如何與 macOS 協同工作的資訊。


---

# 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/v27-zh-tw/parallels-desktop-for-mac-27-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/she-ding-windows-ru-he-shi-yong-macos.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.