> For the complete documentation index, see [llms.txt](https://docs.bloombot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloombot.app/evm/basics/getting-started-new/bloom-manager.md).

# Bloom Manager

{% hint style="info" %}
Bloom Manager (manager.bloombot.app) is Bloom's website, and it uses the same account as the bot. You log in with Telegram.
{% endhint %}

## Log In

{% stepper %}
{% step %}
On manager.bloombot.app, click **Connect Telegram**.
{% endstep %}

{% step %}
Telegram opens Bloom's Solana bot, @BloomSolana\_bot. Tap <kbd>Start</kbd> if it asks.
{% endstep %}

{% step %}
Tap <kbd>Login</kbd> in the message the bot sends.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
On a phone, press and hold <kbd>Login</kbd> and choose **Open in Browser**, so the login reaches the browser you started from.
{% endhint %}

If you have no account on @BloomSolana\_bot yet, **Connect Telegram** starts sign-up there. Click **Connect Telegram** again once you are signed up.

## One Account

Your Telegram account is your Bloom account. The bot and Bloom Manager show the same wallets, settings and tasks, so a change in one shows in the other.

## Bloom Extension

The Bloom browser extension adds Bloom buttons to token sites such as GMGN, DexScreener, Axiom and Photon. On an EVM chain, its Bloom button can open @BloomEVMbot on that token's panel. The bot carries out buys and sells placed in the extension on an EVM chain, and their trade messages arrive in your chat with @BloomEVMbot.


---

# 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://docs.bloombot.app/evm/basics/getting-started-new/bloom-manager.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.
