📢 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!

📢 Notice: OpenClaw.AI Basic Part 2 Course Now Open

Hello, I am Kevin, the instructor for the OpenClaw.AI basic course.

I am writing to inform you that [Basic Part 2] OpenClaw.AI Master Class: A Smartphone Remote Assistant Completed with Telegram and Vision AI has been released on Inflearn. ^^

I hope my lecture can be of even a little help in allowing you to utilize OpenClaw smartly in your daily life.

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

What we will create together in Part 2

- Build an environment to remotely control your agent anytime, anywhere using Telegram on your smartphone.

- Complete a household account book routine where a single receipt photo is automatically analyzed and recorded using Gemini 2.5 Flash's vision capabilities.

- Upgrade the Docker + workspace environment created in Part 1 into a real-world automation scenario.

Especially recommended for these people

- Those who say, "Now I want to use agents on my smartphone without a browser."

- Those who want AI to automatically classify and record receipt/image data instead of manually organizing it every time.

- Those who want to connect OpenClaw, which they only got a taste of in Part 1, to actual work/life automation.

Part 2 Core Curriculum at a Glance

- Section 1: Part 1 environment check and "Agent in My Pocket" scenario orientation.

- Section 2: Creating a Telegram bot with BotFather → Pairing → Real-time connection with OpenClaw agent.

- Section 3: Send receipt photos via Telegram → Automatic extraction of date, business name, amount, and items → Automation of cumulative storage in the expenses/ folder.

Pre-course Checklist

- It is best if you have the Docker container and Gemini API key used in Part 1 ready.

- Even if you haven't taken Part 1, you can set up the minimum required environment by following the “Hands-on Environment Pre-check List” provided in Part 2.

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

Based on student feedback, I will continue to reinforce the practice exercises and troubleshooting guides.

Hello, OpenClaw Part 1 students.

It seems that many people are getting stuck during the environment setup stage involving Docker, WSL2, macOS, etc., so I have created new full setup guide documents for each operating system separately from the main lecture content.

The following two documents have been newly added.

• Windows (WSL2) Dedicated Setup Guide

  • Install Docker Desktop

  • Installing WSL2 + Ubuntu and integrating with Docker

  • OpenClaw project folder / .env / docker-compose.yml / openclaw.json configuration

  • Connecting Gemini via onboarding

  • Accessing the dashboard → Pairing the device → First greeting in the chat window

• macOS Exclusive Setup Guide

  • Install Docker Desktop for Mac

  • OpenClaw project folder / .env / docker-compose.yml / openclaw.json settings

  • Connecting Gemini via Onboarding

  • From dashboard access → device pairing → to the first greeting in the chat window

Both documents aim for “a state where the first greeting message returns in the chat window without errors,” and include a compilation of frequently encountered error messages and checklists during the setup process.

👉How to check

• You can use the guide document corresponding to your OS via the link below.

  • Go to OpenClaw Full Setup Guide by OS

From now on

1. First, please follow the OS-specific setup guide thoroughly, and

2. If there are still parts that remain unresolved,

   • Current environment (Windows / macOS),

   • the command you executed,

   • If you provide the error message/screenshot
     , we can assist you more quickly.

If there are any changes, the setup documentation will be continuously supplemented and updated,
so if you get stuck at any point, please refer back to the newly uploaded guides.

Thank you!

Hello, I'm Kevin.

I have organized troubleshooting documentation for two issues that frequently occur in Windows + WSL2 environments and added them to the lecture materials.

• When the error The command 'docker' could not be found in this WSL 2 distro occurs in WSL2 Ubuntu

• If you get an "API Key Missing" error when leaving google_api_key / GEMINI_API_KEY blank in auth-profiles.json

If you have experienced the above situation even once, reading through the following document in the lecture materials will help you quickly resolve the same issue on your own if it occurs again.

docs/troubleshooting/03-openclaw-docker and Environment Variable Recognition Troubleshooting Guide.pdf

In the future, I will continue to document and share common points of confusion or frequently asked questions during the practice sessions in this format.

Thank you!

To all students of OpenClaw Basics Part 1,

Hello, I'm Kevin.

In response to your feedback requesting more systematic management of the lecture materials, we have completely reorganized the structure of the lecture materials for OpenClaw Basics Part 1 to make practice and code reproduction much easier!

Thank you so, so much for your feedback.

With this reorganization, we focused on minimizing the "confusion over what to download and from where" as much as possible, so please refer to the details below!

What has changed?

Now, the GitHub repository for downloading lecture materials is organized into the following major folder structure.

• docs/
  You can find documents corresponding to the [Free Guide] in one place, including the installation checklist, Docker/Linux cheat sheets, system prompt templates, and file auto-classification prompts.
  

• lesson-files/
  Contains the initial set of files needed right before starting each lesson.
  Open the folder corresponding to the lesson number (Section/Lesson), copy it to your working directory, and begin your practice.

• releases/
  This is a space where the
  **"step-by-step completed versions" of files such as docker-compose.yml and openclaw.json** are collected as they are developed throughout the course.
  You can use these for reference when you want to "jump" to a specific stage if you run into issues during the practice.

• samples/
  A folder containing answer keys and reference sample data, such as example inputs/outputs, reference IDENTITY/USER examples, and report examples.
  

• slides/
  The slide PDFs used in each lesson are organized here.
  The filenames follow the format basic-p1-sectionXX-lessonYY.pdf, so they match directly with the section/lesson numbers on Inflearn.

• templates/
openclaw.min.json, openclaw.json contains reusable default configuration templates such as templates, system prompts, and user profile templates.
  

How do I find the practice files for each lesson?

1. Check the section/lesson number you are currently taking on Inflearn.

2. Find the lesson-files/sectionXX-lessonYY/ folder on GitHub.

3. Read the README.md in the folder first, and copy the files to your working folder as instructed.

4. Proceed with the practice by modifying and executing the code as explained in the video.

5. If you need to check if everything is correct, you can compare it with the files in the releases/ folder at the same stage.

Where can I find the free guides, prompts, and slides?

• Free Guides (Checklists, Cheat Sheets, Prompt Collections)
  → These are organized in PDF/text format within the docs/ folder.

• IDENTITY / USER Profile Chat Prompts
  → These are also provided as text files within the lesson-files/sectionXX-lessonYY/ folder of the relevant lesson.
  (A copy-paste version has been added so you don't have to manually type out content that only appears in the slides.)

• Slide PDFs for each lesson
  → You can open the basic-p1-sectionXX-lessonYY.pdf files in the slides/ folder.

How should you use this moving forward?

The recommended flow is as follows.

1. Watch Inflearn videos

2. Prepare the initial set of files from the lesson-files of the corresponding lesson

3. Refer to guides/cheat sheets/prompts in docs if necessary

4. Compare the results with releases after the practice session

5. For additional practice, utilize the samples data.

This reorganization is based on actual student feedback.

“I wish the code provision was just a bit more systematic.”

In response to that, we focused on solving the problem of “having plenty of materials but being confused about where to start.”
If you have any inconveniences or think, “It would be great to have this kind of material,” please let us know anytime through questions or reviews.
We will actively reflect them in our updates.

Thank you.
Best regards, Kevin, the operator of [Basics Part 1] OpenClaw.ai Master Class.

Everyone!

A new “Project Spend Cap” feature has been added to Google AI Studio / Gemini API, which is used in the OpenClaw Part 1 lecture.

The method I explained in the lecture was a bit complicated, but now it can be set up easily.

By using this feature,

- prevent "situations where charges suddenly spike due to accidental excessive calls" in advance, and

- You can safely limit the maximum monthly usage amount for each practice session or project.

You can set it up right away by accessing Google AI Studio and going to the menu below! I'll also include a screenshot!

• Get API Key > Billing

[ Google AI Studio screen capture image ]

Notice: Updated to WSL2-based project path

Hello, students!

I have written two lesson updates below for studying the Part 1 Basics course, so

Please make sure to read the Key Announcement Details section!

Key Announcement Details

- Lesson 7: Replaced/added with the WSL2-based project creation practice video.

- Lesson 8: Before the actual class begins

A notice video has been added to inform you that “all explorer paths are based on the WSL2 Ubuntu home directory.”

- For those who previously understood it based on the D drive,

From now on, based on the WSL2 Ubuntu /home/<username>/... path

Please follow along with the lecture.

Announcement Details

1. Additional guidance on WSL2-based project creation video (Lesson 7)

The part in the existing Part 1 lecture where the demo project was created based on the Windows D drive,

It has been updated to a method of creating projects based on the WSL2 Ubuntu home directory.

- A new practice video for creating WSL2-based projects has been added to Lesson 7.

- The basic premise of this lecture is now as follows:

- Use the combination of Windows + Docker Desktop + WSL2 Ubuntu.

- All code and configuration files related to the demo project and OpenClaw

Create it under the WSL2 Ubuntu home directory, not D:\....

- Example path:

- /home/<username>/demo-p1

- /home/<username>/demo-p1/workspace

- Docker volumes should also be set based on the WSL2 path.

- Example:

    volumes:
        - /home/<username>/demo-p1/config:/home/node/.openclaw
        - /home/<username>/demo-p1/workspace:/home/node/workspace

If you set up the project again based on WSL2,

- You can avoid OpenClaw's permission hardening and Windows NTFS permission issues,

- With a structure that follows the recommended best practices for Docker + WSL2,

Afterward, you can also easily migrate to Linux server or cloud environments.

2. Notice on Explorer Path Notation (Lesson 8, before the start of the main class)

Also, at the beginning of the Lesson 8 lecture,

A notice video regarding "the Windows Explorer path notation shown in all subsequent learning videos" has been added.

- In the existing recordings, within the Windows File Explorer,

- D:\demo-p1\workspace

There are scenes where paths like the following are displayed on the screen.

- In reality, you should use the ~/demo-p1/workspace directory in WSL2 Ubuntu, not the D:\ drive.

- Example:

- WSL2 Ubuntu:

/home/<username>/demo-p1/workspace

- Windows Explorer:

\\wsl.localhost\Ubuntu\home\<사용자명>\demo-p1\workspace

Or enter the same location through the Linux menu

> Therefore, in the subsequent lecture videos, when you see the Windows File Explorer showing

> Even if there are scenes that look like D:\...,

> Please follow along keeping in mind that the actual intended path is the "project path in the WSL2 Ubuntu home directory."

In the Class 8 announcement video:

- How to open a demo project within WSL2 Ubuntu from Windows Explorer \\wsl.localhost\Ubuntu\home\<사용자명>\demo-p1\workspace),

- How to navigate by clicking in File Explorer: Linux → Ubuntu → home → <사용자명> → demo-p1 → workspace

is explained together, so please check this announcement video first and then

Watching the following main lesson video afterward will help reduce confusion.

3. Final summary once more

- Lesson 7: Replaced/added with WSL2-based project creation practice.

- Lesson 8: Before the actual class

An announcement video has been added to inform you that "all explorer paths are based on the WSL2 Ubuntu home directory."

- For those who previously understood it based on the D drive,

From now on, based on the WSL2 Ubuntu /home/<username>/... path

Please follow along with the lecture.

Thank you.