Bambou Project – Onboarding

Maintained by BIPRO

1. What this work is for

We build AI-powered conversational marketing automations for public random-chat / dating-chat sites (Omegle-likes, etc.). The agents use Bambou's AI model (bambouaibot.com – custom AI chat companions like Lina, Louise) to introduce relevant services and share promotional links with interested users.

Your work as dev:

  1. Reversing websites
  2. Making automations (bots)
  3. General tasks
  4. Other developer work

Most of the work is done using AI – basically vibe coding. You don't have to do everything manually.

2. High-level marketing flow

chat site automation (you build) -> conversation powered by Bambou AI -> relevant promotional link -> interested user explores the service

The purpose is marketing and service discovery, not persuading users to buy a subscription. Users decide whether to visit a linked service or take any further action.

Where direct links are unavailable, an assigned Snapchat account may serve as an intermediate marketing channel.

3. Workflow per site – step by step

  1. Pick a site. Check the shared sheet CHAT ONLINE LIST for untaken sites. Then research the site you picked (SimilarWeb also works for traffic/session-time). After that, SKIP SITES WITH <~15 online users. Ask if unsure. Example starters: Camsurf (text-only), Chatrandom, Chat-fr, Whisperly, Chitchat.gg, Y99.in, etc.
  2. Manual research first – full steps on Research page. Open the site as a normal user. Understand:
    • signup vs guest-chat flow
    • how chat transport works (websocket / polling / HTTP)
    • skip/next behavior, rate limits, captchas, bans
    • average session time via SimilarWeb (Engagement Overview → Average Visit Time) – goal is ~1 real convo per session.
    • whether the site supports sharing promotional links in chat – the marketing flow needs a way for interested users to reach the relevant social profile or service. If links are unavailable and there is no assigned alternative channel, the site is not suitable for this workflow.
  3. Build automation – prototype first:
    • Get the very first working prototype as fast as possible before adding any extras.
    • Prefer pure HTTP (requests, httpx, socketio, beautifulsoup4) when possible.
    • Use playwright / headed browser via xvfb + extensions only as last resort.
    • Must handle skip/next, avoid bot-to-bot matches (e.g. scrape assigned IDs where available).
    • Multithreaded / parallel workers – Bambou calls this "multithreading". Target 50-100 simultaneous accounts per site.
  4. Wire to Bambou AI API (see §6). You will get the list of presets either in the docs or as a response to a specific API call. Use the preset assigned for your site.
  5. Integrate the Dashboard / HUB API as well (see setup, full documentation, and starter downloads). Use https://bamboubot.duckdns.org as HUB_URL, with the site's own agent token. Connect worker health, start/stop/restart, configuration/proxy sync, real statistics and telemetry, and backups. The HUB is separate from the Bambou AI API; both integrations are required.
  6. Proxies + hosting. Test with proxies from day one. Don't develop only on datacenter IP then wonder why it gets blocked.
  7. Get a VPS when script is ready. Tell BIPRO/Bambou – Bambou pays for VPS. "Dedicated VPS" here just means: a VPS meant only and only for that very specific site and not for anything else.
  8. Ask your AI agent for VPS specs. At the end of your AI coding chat, ask: "what specs are needed to run at least 50 workers and max 100 workers of this automation?" Send that estimate when requesting the VPS.
  9. Update sheets + handoff. Log progress in the shared sheet. When swapping AI chats, write a short .md handoff so context isn't lost.

Tracking managed by BIPRO / Bambou – you don't need to do anything for it

4. Done per site

A site is DONE when:

No manual demo with your own IP + hardcoded replies = not done.

5. Tech freedom

Bambou only cares about working automations for the sites. Devs have freedom for whatever they do / however they do it.

So one codebase per site, shared tooling, separate repo, whatever – never really thought of, just do what works. "He only wants it working. Doesn't matter how."

6. AI API & presets

Full reference is in the official docs – read those, don't guess:

6a. Dashboard / HUB API — required

Every site automation must integrate the Dashboard / HUB API as well as the Bambou AI API. The HUB manages worker health, lifecycle controls, runtime configuration/proxies, statistics, telemetry, and backups; it does not replace the AI API or implement your site's chat logic.

7. Proxies, VPS, accounts, captchas

All credentials provided separately gradually as you progress.

8. Hours, pay, reporting

9. How to start

10. Do / Don't

Do:

Don't: