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

# Notifications

**The Уведомления Twitter tab — every post from your watchlist, plus controls to keep the noise down.**

The second tab on Tracker is the read side. Every post from accounts in your **Мой список** surfaces here in reverse-chronological order. The bell icon in the header counts unread notifications across the terminal — clicking it jumps to this tab.

## What you see per notification

* **Account** — handle and display name of the poster.
* **Time** — relative timestamp.
* **Post content** — text excerpt, plus the link to the original X post.
* **Inline actions** — open in X, dismiss, snooze the account.

## Reading the stream

The stream is plain reverse-chronological — newest at the top. Treat it like a personal X timeline filtered to the accounts you actually care about.

* **Hot signal** — a watched account posts something time-sensitive (event news, market-relevant statement). Read it, open the related market if any, decide.
* **Cold signal** — your watchlist is talking about background topics. Skim or dismiss.
* **Noise** — repeated posts from one account that aren't market-relevant. Snooze that account.

## Snoozing & muting

* **Snooze** — temporary mute on a single account. Useful when an account that's usually good is in a noisy phase.
* **Remove from list** — done from [Adding Accounts](/graphdex-docs/tracker-predictions/adding-accounts.md). Stops notifications immediately.
* **Mark all read** — clears the unread counter on the bell.

## Filtering the stream

Filters above the list (when shown):

* By account — drill into a single watched account's posts.
* By time window — last hour, last day, all.
* Search — string match across post text.

## Cross-referencing with Research

A post about a real-world event is most useful when paired with a market that might react. The recommended flow:

1. Spot a hot post on Notifications.
2. Open [Research](/graphdex-docs/research-predictions/research-overview.md) and pick the matching category (Politics for political news, Crypto for token-related posts, etc.).
3. If there is a relevant market — open it, read depth, decide whether to trade.
4. If no market matches — note the signal and watch [Pulse](/graphdex-docs/pulse-predictions/pulse-overview.md) for the next time a new market spawns in the same area.

## Keeping the stream sane

Notifications are easy to abuse — too many accounts, too many checks per day. Reasonable defaults:

* Check the stream 2–3 times a day, not every minute.
* Prune the watchlist quarterly — remove accounts you no longer read.
* Snooze rather than remove during noisy event windows.

{% hint style="info" %}
Tracker alerts are a discovery signal, not a trade signal. Every position still goes through the same execution path as a click from Research — order book, size, speed, submit.
{% endhint %}

## FAQs

<details>

<summary>How long are notifications retained?</summary>

Recent notifications stay on the page; older ones may roll off depending on platform-wide retention. Treat the stream as a current-events feed, not an archive.

</details>

<details>

<summary>Can I get push notifications outside the terminal?</summary>

The current build surfaces notifications via the bell icon in-terminal. External push (email, Telegram, mobile) may be on the roadmap; check the platform announcements.

</details>

<details>

<summary>Why are some posts duplicated?</summary>

The same X post may appear via different surfaces (retweets, quote tweets) depending on how the underlying account engages with it. Dedupe behaviour is heuristic; it's not always perfect.

</details>

<details>

<summary>Can I share a notification to Telegram or Discord?</summary>

Use the in-row link to open the post on X, then share it from there. There is no in-platform reshare action in the current build.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://graphdex-1.gitbook.io/graphdex-docs/tracker-predictions/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.