> For the complete documentation index, see [llms.txt](https://unisignal.gitbook.io/unisignal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unisignal.gitbook.io/unisignal/installation.md).

# 安装扩展

请使用电脑上的 Chrome 浏览器（116 或以上版本）。

## 添加到 Chrome

1. 打开 [UniSignal Telegram Feed 商店页面](https://chromewebstore.google.com/detail/unisignal-telegram-feed/hcbiofphajciknflaghdkneniajhjkgg)。
2. 点击“添加至 Chrome”，在弹出的窗口中确认“添加扩展程序”。
3. 等待 Chrome 提示安装完成。

## 把图标固定到工具栏

1. 点击 Chrome 右上角的拼图图标，打开扩展菜单。
2. 找到 **UniSignal Telegram Feed**，点击旁边的图钉。
3. 工具栏上出现 UniSignal 图标后，就可以直接点击它了。

接下来[获取连接凭证并连接](/unisignal/connection.md)。如果已经打开 GMGN，请在连接完成后刷新页面。

## 更新扩展

通过商店安装后，Chrome 会自动更新扩展，通常不需要手动操作。

更新后刷新 GMGN 页面，再打开推特监控面板即可。遇到问题时，查看[常见问题](/unisignal/faq.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://unisignal.gitbook.io/unisignal/installation.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.