> 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/manager/deploy/overview.md).

# Overview

Dev Features bring token deployment inside Bloom. You launch coins directly from the Twitter tracker in the Manager, on the launchpad you pick, with the wallet you control, without leaving Bloom.

### Deploy

Launch a new token in a few clicks. Pick a creator wallet, set name, symbol, image, and post, choose a launchpad, set the amount, and click Deploy Token. The wallet you selected deploys the token and performs the first buy.

#### Vamp

Clone the metadata of an existing token into a new launch.

* Paste a contract address.
* Bloom prefills name, symbol, image, and description.
* The rest of the flow is identical to Deploy.

{% hint style="info" %}
You see a coin trending and want to launch a variant in seconds without typing every field. Vamp gets you there in two clicks.
{% endhint %}

### Bundle modes

Pick how the early buys land:

* **None:** Clean deploy and creator buy.
* **Packed:** Extra buys bundled inside the deploy transaction.
* **Non-Packed:** Parallel buys that land before anyone else.
* **Sniper:** Parallel buys that avoid bundle detection.

Add the wallets that buy and the wallets that receive distributed tokens. Bloom handles the sequencing.

{% hint style="info" %}
You want first buys guaranteed before the public: Non-Packed. You want the buys to look organic and stay off bundle detection: Sniper.
{% endhint %}

### AI-assisted token image

Four sources, one editor:

* **From Tweet:** Image pulled from the source tweet.
* **Library:** Images you uploaded.
* **AI Generated:** Image generated from tweet content and coin context.
* **Default:** Image attached to a preset.

Open the Studio to crop, recolor, apply templates, add emoji, and add custom text.

### Three launchpads

* **Pump.fun**
* **Bonk.fun**
* **Bags.app**

Each launchpad has its own settings. Deploy on one, two, or all three at once.

***

### Where you use it

Right now, everything lives inside the Twitter tracker on the Manager. You see a tweet, you click Deploy or Vamp, and the modal opens with the relevant context already loaded.

Next, the Bloom Chrome extension will inject the Twitter tracker directly into the terminals you already use, including Axiom, Padre, and GMGN.

{% hint style="info" %}
You trade on Axiom every day. With the injected tracker you don't switch tabs anymore. You deploy a token, watch its chart, and buy or sell with Bloom's execution speed, all on the terminal you already use.
{% endhint %}


---

# 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://docs.bloombot.app/manager/deploy/overview.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.