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

# 在 GMGN 中查看消息

## 混排模式

打开 [GMGN](https://gmgn.ai/) 的推特监控面板。默认情况下，UniSignal 消息按消息时间与推特消息一起排列，频道名称帮助你识别消息来源。

扩展需要页面上的推特监控面板才能展示消息。刚安装或更新扩展后，先刷新 GMGN。

## 悬浮模式

在 GMGN 页面点击工具栏的 UniSignal 图标，可在混排和悬浮模式之间切换。

悬浮模式把频道消息放在独立窗口中，你可以：

* 拖动顶部工具栏，移动窗口。
* 拖动右下角，调整窗口大小。
* 在窗口内滚动查看消息。
* 点击右上角“×”，返回混排模式。

悬浮模式同样需要打开 GMGN 的推特监控面板。

## 打开原消息和代币页面

* **Telegram 原消息**：点击可在 Telegram 中查看原文。你需要有对应频道的访问权限。
* **合约链接或 CA 按钮**：CA 指代币的合约地址。点击消息中的合约链接或底部 CA 按钮，可打开 GMGN 对应的代币页面，支持 BSC、Ethereum 和 Base。

这些按钮会根据消息内容显示，并非每条消息都有。

## 编辑、删除和历史消息

频道消息被修改后，列表中的内容会随之更新并显示“已编辑”，不会再次响铃。频道消息被删除后，扩展收到通知时也会移除对应内容。

扩展会在当前浏览器中保留最近 **100 条**频道消息，重新打开页面后仍可查看。更早的消息请前往 Telegram 查看。首次安装时还没有消息记录，需要等待新消息。


---

# 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/messages.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.