> 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/adding-accounts.md).
# Adding Accounts
**Build your watchlist with intention — single-add, bulk-import, or copy from Top Subscriptions.**
The **Настройки** tab on Tracker is where the watchlist is built. Four entry points to add accounts; one search field to find what's already there.
## Single-add by handle
1. Click **Добавить аккаунт** in the toolbar.
2. Type the X handle (with or without the `@`).
3. Confirm. The account lands in **Мой список**.
Single-add is the right tool when you know exactly who you want to follow.
## Bulk-import
1. Click **Импорт**.
2. Paste a list of handles (one per line) or upload a CSV with a `handle` column.
3. Submit. Existing entries are deduplicated automatically.
Bulk-import is the right tool when you're migrating a list from elsewhere — a personal note, another tracker, an exported file.
## Discover via Top Subscriptions
The **Топ подписок** sub-pill on the Settings tab shows accounts that other Predictions users follow most. Each row has an Add button.
* Useful for picking up category-leading accounts you didn't know about.
* Treat it as a starter list, not a recommendation — popularity isn't quality.
* Combine with the search bar to filter the top list down to handles that match a keyword.
## Search & filter
The search bar (**Поиск по имени**) filters whichever sub-view you're on:
* On **Мой список** — narrows your watchlist.
* On **Топ подписок** — narrows the platform-curated list.
## Export & backup
Click **Экспорт** to download your current watchlist. Useful for:
* Backups before bulk-edits.
* Sharing curated lists with other accounts.
* Importing on a different account.
The export format is the same one **Импорт** accepts.
## Removing accounts
Open **Мой список** and use the per-row remove control. Removed accounts stop producing notifications immediately; historical notifications from them stay in the Notifications tab unless cleared there.
## Sizing the watchlist
* **Under 10** — manageable, signal stays clean.
* **10–50** — workable if you're disciplined about categories.
* **Over 50** — Notifications will overwhelm; consider splitting categories or pruning.
Quality beats quantity. A 7-account watchlist of high-signal accounts produces a better feed than a 70-account everyone-and-their-cousin list.
{% hint style="warning" %}
The accounts you add are visible to no one else in your account. Tracker is a private feed. But the export file is plaintext — handle it like any other personal data.
{% endhint %}
## FAQs
Are there platform-wide limits on watchlist size?
Practical limits come from notification volume, not from a hard cap. The platform may rate-limit very large watchlists in the future; the current build is permissive.
Can I add private/locked X accounts?
Tracker can only act on what X exposes publicly. Locked accounts' posts aren't visible to Tracker.
How fast do new posts surface after I add an account?
Near-real-time on active accounts; slower on accounts that post infrequently. The Notifications tab is the source of truth for what's been picked up.
Does importing duplicate handles double-add them?
No — the import dedupes by handle. Existing entries are preserved and the import skips them silently.
---
# 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/adding-accounts.md?ask=&goal=
```
`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.