> 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/getting-started/connect-with-telegram.md).

# Connect with Telegram

**Telegram is the no-extension sign-in path — OAuth through your existing Telegram account, no wallet plug-in required upfront.**

Telegram sits among the social options in the GraphDex sign-in modal. Pick it when you don't have Phantom or MetaMask installed, or when you'd rather authenticate through the Telegram account you already use. After the Telegram flow completes, the terminal lands you back signed in.

A wallet is still required to actually trade — but you can attach one later from inside the connected session.

{% hint style="success" %}
**Sign in with one tap**

Open the modal, pick Telegram, finish the authorization in Telegram, and you're back in the terminal signed in.
{% endhint %}

## HOW TO START

1. Open the GraphDex Terminal.
2. Click `Connect wallet`.
3. Choose **Telegram** in the sign-in modal.
4. Complete the Telegram authorization flow.
5. Return to GraphDex when Telegram or the browser sends you back.

## BEFORE YOU CONTINUE

Telegram remembers the last signed-in account in your browser — make sure it's the right one before you start.

* Confirm the Telegram account is the one you want connected to GraphDex.
* If the wrong account opens, switch accounts inside Telegram first and restart the flow.
* If Telegram opens the desktop app instead of the browser, finish authorization there and return to the GraphDex tab.

{% hint style="info" %}
If the Telegram flow doesn't complete: allow browser redirects from GraphDex, check whether Telegram opened in the browser or in the app, finish any pending confirmation prompt, and return to the original GraphDex tab. A fresh terminal tab usually resolves a stuck flow. If the issue persists, use the [Help Center](/graphdex-docs/help-and-feedback/help-center.md).
{% endhint %}

## FAQs

<details>

<summary>Do I still need a wallet if I sign in with Telegram?</summary>

For account-only features (Tracker watchlists, Referrals progress, Earn information), no. For actually trading, you'll need to attach a wallet — you can do that after signing in. See [Connect a Wallet](/graphdex-docs/getting-started/connect-a-wallet.md).

</details>

<details>

<summary>The wrong Telegram account opened — how do I switch?</summary>

Switch accounts inside Telegram (Telegram → Settings → Accounts), then restart the GraphDex sign-in flow from `Connect wallet`.

</details>

<details>

<summary>The flow doesn't complete — what should I check?</summary>

* Browser redirects are allowed for GraphDex.
* Telegram opened where you expected (browser or app) and you finished any pending prompts.
* You returned to the original GraphDex tab after authorization.
* A fresh terminal tab usually clears a stuck flow.

If it still fails, send a report through the [Help Center](/graphdex-docs/help-and-feedback/help-center.md).

</details>

<details>

<summary>Is Telegram sign-in different from Google sign-in?</summary>

Mechanically they're parallel OAuth flows — different provider, same outcome. See [Connect with Google](/graphdex-docs/getting-started/connect-with-google.md) for the Google variant.

</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/getting-started/connect-with-telegram.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.