FluidExtension is a free, open source Chrome side panel that lets a FluidTalk character answer messages in the browser you already use. You sign in to Instagram normally, open the panel beside it, and the character reads the conversation on screen, writes the reply and sends it.
It works on Instagram, Threads, Telegram Web and WhatsApp Web, and it needs no phone, no proxy and no server.
FluidTalk and FluidExtension are both ours, and so is Onimator. FluidTalk is the engine that writes the messages. Onimator and FluidExtension are two different ways of delivering them: Onimator drives the real app on a real Android device, FluidExtension works inside your browser. The same character runs on either.
Overview
FluidTalk writes, a connector delivers. That split is the whole design, and it is why one character can work in several places at once.
| Onimator | FluidExtension | |
|---|---|---|
| Where it runs | Real Android devices | Your Chrome browser |
| Platforms | Instagram, Threads, TikTok, Snapchat, Reddit, Bumble, Tinder | Instagram, Threads, Telegram, WhatsApp |
| Needs hardware | Yes, a phone or cloud phone | No |
| Needs a proxy | One per account | No, it uses your browser session |
| Cost | Onimator licence | Free, MIT licensed |
The two are worth running together, not instead of each other. The extension covers Telegram and WhatsApp, which Onimator does not reach. Onimator covers TikTok, Snapchat, Reddit, Bumble and Tinder, which the browser cannot. One FluidTalk character, one funnel, both surfaces.
How do I install the FluidTalk extension?
Four steps, about two minutes.
- Download the folder from extension.fluidvip.com
- Unzip it
- Open
chrome://extensions, turn on Developer mode, and click Load unpacked - Paste your FluidTalk API key, then click Test connection
It runs on Chrome, Edge, Brave and the Chromium anti-detect browsers, with one account per browser profile.
The key is the character. Swap the key and a different character is answering. Keep it as private as a password.
The key never touches the page you are browsing. The extension's background worker holds it and talks to FluidTalk directly, so nothing is exposed to Instagram, Telegram or WhatsApp.
What can it actually do?
Everything in the inbox, not just the replies in front of you.
Direct messages on all four platforms ✅ Message requests, the queue sitting behind the main list that most operators never clear ✅ Follow-ups for leads who went quiet, on a ladder of 12, 24 and 48 hours ✅ Comment replies on Instagram and Threads, so people answering your comments get a response ✅ Public comments on posts ✅ Cold openers, conversations started with people who never messaged you
You never tell it which account you are on or which site you are using. It reads that from the tab and works from whichever switches you have enabled.
Three of these ship switched on: comments, comment replies and cold openers. They reach people who never contacted you, which is a different risk profile from answering your own inbox. One switch each turns them off. Decide before you connect a real account, not after.
WhatsApp follow-ups ship switched off, deliberately. Turn them on knowing that is the setting most likely to get a WhatsApp account signed out.
How do I control the pace?
Every pass has its own limits, and you set all of them.
- Hourly and daily caps, per pass, per platform
- Working hours, so the account is not answering at 04:00
- A four to twelve second pause before the first reply goes out
- The Activity tab logs every message sent and every refusal, with the reason
The Activity log is the part to check first when something looks wrong. A quiet run with no sends is usually a refusal with a reason attached, not a broken install.
Automating messages is against the terms of service of all four platforms, and accounts doing it can be rate-limited, restricted or banned. The caps, the delays and the working hours reduce the risk. They do not remove it.
Can my AI agent build the character for me?
Yes. FluidTalk exposes an MCP server, so you can point Claude Code, Codex, Gemini or any MCP client at it.
Describe the persona and the funnel in plain language and your agent builds them, then issues the connector key you paste into the extension. No forms.
It stays useful after launch, which is the part people miss. Your agent can read the conversations the character actually had, tell you which opener gets replies and where people go quiet, then rewrite the prompt or a funnel step and save it back. You ask rather than analyse.
Onimator has its own MCP server too, covered in how to connect Claude Code to Onimator via MCP and Onimator MCP prompts, reports and settings.
How do the extension and Onimator work together?
Through one character and one key. The connector is the only thing that changes.
A practical way to run both:
- Build the character once in FluidTalk, with its voice, funnel and gates. Setup is in how to set up FluidTalk for DMs and comments.
- Use the extension for the browser platforms, especially Telegram and WhatsApp, where Onimator does not operate.
- Use Onimator for the device platforms, where the real app on a real phone is the stronger signal and where TikTok, Snapchat, Reddit, Bumble and Tinder live.
- Route leads between them. A lead who starts in Instagram comments can be moved to Telegram and carry the same conversation, because the character is the same character.
Start on the extension if you are new. It costs nothing, needs no hardware, and shows you what the character does before you commit to devices.
Move to Onimator when the browser becomes the limit. One browser profile per account stops scaling before a phone does, and device automation reaches three more platforms.
What does it cost to test?
Nothing to install, and almost nothing to try.
The extension is free and MIT licensed, and the source is on GitHub, so you can read every line before trusting it with your inbox, or fork it.
Every new FluidTalk account starts with $1 in tokens, which is roughly ten conversations at the free rate. That is enough to watch the character work on a real inbox before spending anything.
Common Issues
Nothing sends. Open the Activity tab. Every refusal is logged with its reason, and the usual causes are an hourly cap reached, the current time falling outside working hours, or a pass that is switched off.
The panel does not detect the account. It reads the account and platform from the tab. Make sure you are signed in and on the right site, and that the profile in this browser is the one you intend to use.
Test connection fails. The key is wrong, or it has been rotated in FluidTalk. Issue a fresh one and paste it again.
Messages go out in the wrong voice. The key is the character. Check which key is in this browser profile, since a different profile can hold a different one.
A WhatsApp account got signed out. Check whether follow-ups were turned on. They ship off for this reason.
Tutorials & Support
- How to Set Up FluidTalk for DMs & Comments
- How to Connect Claude Code to Onimator via MCP
- Direct Message (DM) Tool
- Comment Tool
- FluidTalk in the glossary
FAQ
Is the FluidTalk extension free?
Yes. The extension is free and MIT licensed, and its source is public. What you pay for is FluidTalk conversation tokens, and a new account starts with $1 of them.
Do I need Onimator to use the extension?
No. The extension is a complete connector on its own and needs no phone, proxy or licence. Onimator matters when you want the device platforms or real-device delivery.
Do I need a proxy?
Not for the extension. It works inside your existing browser session, so it uses whatever connection that profile already has. Onimator is the one that wants one proxy per account.
Can I run several accounts?
One account per browser profile. Separate Chrome profiles, or anti-detect browser profiles, keep them apart. Each profile holds its own key.
Does the extension see my Instagram password?
No. You sign in yourself as usual, and the extension works inside the session you already have. It never asks for a password, and your FluidTalk key is held by its background worker rather than the page.
Which is safer, the extension or Onimator?
They fail differently rather than one being safe. Onimator drives the real app on a real device, which is the stronger signal to the platform. The extension runs in a browser, which is easier to start with and reaches Telegram and WhatsApp. Neither removes the risk of automating messages.
Can the same character work in both at once?
Yes, and that is the intended setup. One character, one funnel, delivered through whichever connector suits the platform.
Conclusion
- FluidTalk writes, a connector delivers. FluidExtension and Onimator are two connectors for the same character.
- The extension is the cheapest way in: free, no hardware, about two minutes to install.
- Onimator is the way out of the browser's limits: real devices and five platforms the extension cannot reach.
- Check the defaults before connecting a real account. Comments, comment replies and cold openers arrive switched on.
- The Activity tab explains a quiet run, because every refusal is logged with its reason.