[Part 2: Basics] OpenClaw.AI Master Class: A Smartphone Remote Assistant Completed with Telegram and Vision AI

📢 OpenClaw.AI Basic Part 2.5 Course Opening Announcement

Hello, I'm Kevin, the instructor for the OpenClaw.AI Master Class basic course.

I am finally posting an announcement as [Basic Part 2.5] Fundamentals of Multi-Agent Team Design and Role Separation has been released on Inflearn. :)

This Part 2.5 further expands the "AI Assistant in my PC" created in Parts 1 and 2,

This is a lecture focused on growing a single Telegram bot into a small AI team with divided roles.

👉[Go to OpenClaw.AI Basics Part 2.5 Lecture]

What we will build together in Part 2.5

- Using Telegram Forum Groups + Topic-based Routing

We will configure a multi-agent environment that operates two agents, content-planner and content-editor, with a single bot.

- To the /workspace/content/planning / /workspace/content/drafts folders

We will actually create a content workflow where planning deliverables and draft/edited versions are separated.

- Through the scenario of "generating ideas and outlines in the planner room → refining the writing in the editor room," we will complete a realistic multi-agent collaboration routine based on manual copy-pasting.

Especially recommended for these people

- Those who have followed OpenClaw Parts 1 and 2 but are still making a single agent do everything

- Those who want to develop a Telegram bot not just as a "single chatbot," but as an AI team divided into a Planner and a Writer/Editor

- Solo creators, newsletter/blog operators, and YouTubers who want to organize their workflow by delegating content planning, drafting, and refining tasks to role-specific agents.

- Developers, planners, and PMs who are interested in multi-agents but want to start light in their current OpenClaw + Telegram environment instead of using a massive framework

Part 2.5 Core Curriculum at a Glance

- Section 1: For both existing and new students

Part 2.5 Joining Route A (5-minute environment check) / B (Minimum setup onboarding) Guide + Super simple review of OpenClaw UI

- Section 2: Single-agent vs. Multi-agent concepts,

Understanding the structure of how multiple agents are deployed within openclaw.json, and checking the current configuration with openclaw agents list

- Section 3:

- Define content-planner / content-editor agents

- Separate workspaces for /content/planning and /content/drafts

- Telegram forum group & planner-planning / editor-editing topic creation

- Find Group ID / Topic ID → Complete agent routing by topic

- Section 4:

- planner ↔ editor semi-manual collaboration practice (based on human copy-paste)

- Preview of the 4-agent automated collaboration pipeline (Leader/Planner/Editor/QA) to be covered in Part 3

Checklist before taking the course

- It is best if you have the WSL2 + Docker + OpenClaw + Telegram Bot environment used in Parts 1 and 2 ready.

- Even if you haven't taken Parts 1 and 2, I have structured it so that you can set up the minimum environment required for the multi-agent practice by following the “Environment Check Route A / Minimum Setup Onboarding Route B” included in Part 2.5.

- You will need a Gemini API key issued by Google AI Studio.

If you have any questions or get stuck while taking Part 2.5, please feel free to leave them on the Q&A board at any time.

Based on your feedback, we will continue to strengthen the practice examples and troubleshooting guides.

I hope this Part 2.5 serves as an opportunity to expand your OpenClaw environment from "one smart assistant" into a "small AI team with divided roles."

Thank you.

[Notice] OpenClaw Latest Version Bonjour-related Error Guide and Solution

1. Symptom Information

As of today (2026-04-27), after updating the OpenClaw image to the latest version (2026.4.x) via docker pull, an issue where the Gateway container keeps restarting is occurring in some environments.

If the following messages repeat in the openclaw-gateway logs, it corresponds to this issue., thì có nghĩa là bạn đang gặp phải vấn đề này.

[plugins] bonjour: advertised gateway fqdn=... state=announcing

[plugins] bonjour: restarting advertiser (service stuck in announcing ...)

[openclaw] Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED

openclaw-gateway exited with code 1 (restarting)

In this case:

- The openclaw-gateway container starts up and immediately shuts down every few seconds,

- Dashboard access and Telegram integration may not function properly.

2. Cause – Bug in the Bonjour (mDNS) advertising process

By default, OpenClaw Gateway uses Bonjour (mDNS) to allow this instance to be automatically discovered (advertise) on the same network.

In some Docker / WSL / network (routers, corporate networks, etc.) environments:

- After the Bonjour advertise status gets stuck in the announcing stage,,

- An error CIAO ANNOUNCEMENT CANCELLED occurs, and

- There is a bug where this exception is not handled properly, causing the Gateway process to fall into a crash loop.

A patch is currently in progress, and until then, you can use the following workaround.

3. Solution – Disable Bonjour feature (Recommended)

The Part 1/Part 2 practice sessions use a structure intended for use on a single local machine only, so Bonjour is not strictly necessary.

Therefore, we recommend disabling Bonjour via environment variables.

3-1. When using docker-compose.yml

Add the following environment variable to the openclaw-gateway service..

services:

  openclaw-gateway:

    image: ghcr.io/openclaw/openclaw:latest

    environment:
      - OPENCLAW_DISABLE_BONJOUR=1

      # Other OPENCLAW related settings...

After making the changes, restart with the following command.

docker compose down

docker compose up -d

By applying this setting:

- The Gateway will no longer attempt Bonjour/mDNS advertisements,

- It will run stably without taking the CIAO ANNOUNCEMENT CANCELLED error path.

- It does not affect the browser access (dashboard) and Telegram integration used in Part 1/Part 2.

4. Future Guidance

- This issue is a compatibility problem between OpenClaw's Bonjour plugin and certain network/Docker environments, and it is expected to be improved in a future release.

- Even after the patch,

- If you are using it on only one local machine, you can continue to keep OPENCLAW_DISABLE_BONJOUR=1, and

- You only need to re-enable Bonjour when you need to automatically discover OpenClaw instances across multiple devices.

For those students in Part 1/Part 2 who are experiencing a sudden issue where the Gateway keeps shutting down after recently re-pulling the image,

Please apply the settings above to disable the Bonjour feature.

Thank you!