> 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/twitter-x-tracker.md).

# Twitter/X Tracker

**Follow the accounts that actually move markets — without tabbing into X every five minutes.**

<div align="center"><figure><img src="/files/OVXlon60XqRGRA8pZwho" alt="Twitter Tracker settings view"><figcaption><p>Settings tab with My List / Top Subscribed, Add Handle, and Import / Export controls.</p></figcaption></figure></div>

Twitter/X Tracker turns the noisy social feed into a curated alert stream. Add the handles you actually care about, optionally boost the ones you're tracking most closely, and let alerts surface inside GraphDex instead of inside the X feed.

{% hint style="success" %}
**Discovery, not advice**

A popular handle is one signal among many — never the whole picture. Always cross-reference with Research before acting on a tweet.
{% endhint %}

## Add Accounts

Twitter/X Tracker exposes several ways to manage handles:

* **Add Account** — single handle entry.
* **Add All** — bulk add from a list view.
* **Handle Import** — bulk import.
* **Handle Export** — export your current list for backup or migration.
* **Search** — find handles already in your list.

When adding a handle, the terminal validates input: required field, allowed characters, minimum / maximum length, and duplicate detection. Invalid input surfaces explicit feedback — fix it before retrying.

## My List

The **My List** mode shows the handles you're actively tracking. Each tracked-account row exposes:

* **Account identity** — handle and display name.
* **Follower information** — context for the account's reach.
* **Actions** — row-level controls (edit, boost, delete).
* **Tweets** — recent posts surfaced inline.
* **Delete control** — remove from the watchlist.

Keep My List trimmed to handles you actually read — a 200-handle watchlist isn't a watchlist, it's a fire hose.

## Top Subscribed

The **Top Subscribed** mode surfaces handles with the highest subscription interest across GraphDex users. Use it as a **discovery list**, not as a recommendation:

* Popular doesn't mean correct.
* A high-follow account can still post incomplete, promotional, or risky information.
* "Everyone is watching" is a crowding signal, not a trading thesis.

Treat Top Subscribed as a starting point for evaluation — not a substitute for your own filter.

## Boost

Boost prioritizes the handles you want to monitor most closely. The controls expose:

* **Current boost** — what's active on a handle.
* **Boost count** — how many boosts you've applied.
* **Minimum for top placement** — what level it takes for the handle to surface highest.
* **Maximum boost limits** — caps per handle or per account.
* **Success states** — confirmation when a boost is added or removed.

Use boost surgically — give it to the few handles whose posts you genuinely react to fastest. Boosting every handle defeats the prioritization.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/m1zZKHwtJxpa0f4cJYJD"><strong>Wallet Tracker</strong></a></td><td>The on-chain side of the same surveillance flow.</td><td><a href="/files/AnuIRgx3Ju4HdXa1cEG3">/files/AnuIRgx3Ju4HdXa1cEG3</a></td></tr><tr><td><a href="/pages/AVlBX9c7pQQjTospVQGB"><strong>Notifications</strong></a></td><td>How Twitter Tracker events surface as alerts.</td><td><a href="/files/OVXlon60XqRGRA8pZwho">/files/OVXlon60XqRGRA8pZwho</a></td></tr><tr><td><a href="/pages/XJTcByJsbupiZnUUjdb4"><strong>Using Tracker with Research and Trading</strong></a></td><td>From a tweet to a verified trading thesis.</td><td><a href="/files/JBN29ujDJykAmMONwLxK">/files/JBN29ujDJykAmMONwLxK</a></td></tr></tbody></table>

{% hint style="info" %}
A tweet is signal. A tweet plus on-chain verification is a thesis. Always pair social signals with [Research](/graphdex-docs/research/research-overview.md) before trading.
{% endhint %}

## FAQs

<details>

<summary>Does Twitter Tracker show every tweet from a handle?</summary>

The tracker surfaces tweets according to the current alert rules and your boost configuration. Routine posts may be filtered; high-priority handles surface more activity.

</details>

<details>

<summary>How is Top Subscribed ranked?</summary>

By subscription interest across GraphDex users. Treat the ranking as a popularity signal, not a quality endorsement.

</details>

<details>

<summary>Can a handle see that I'm tracking it?</summary>

No. Tracking is a local view — there's no public follow, like, or interaction triggered by adding a handle.

</details>

<details>

<summary>What's the difference between Boost and Follow?</summary>

A standard add puts the handle in My List. Boost raises its priority in the alert stream — Boost is a ranking lever, not a separate channel.

</details>

<details>

<summary>Can I export My List to back it up?</summary>

Yes — the Export control exposes the current My List. Useful before mass-edits or for moving the watchlist across accounts.

</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/twitter-x-tracker.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.
