[Basic Part 2.5] OpenClaw.AI Master Class: Fundamentals of Multi-Agent Team Design and Role Separation
If you follow OpenClaw Parts 1 and 2, you eventually end up making a single agent do everything. As you do this, there comes a moment when prompts get tangled, memory gets mixed up, folders get messy, and you feel stuck, not knowing how to organize things anymore. This lecture is the "Introduction to Multi-Agents (Part 2.5)," designed to help you move one step further from that point. While maintaining a single bot, we will separate roles into two agents—planner and editor—and connect each agent to different workspaces and Telegram forum topics. You will personally build a structure where "different agents respond depending on which room you speak in." By following the hands-on practice, you will have the following in your environment: - A configuration file defining two agents: `content_planner` and `content_editor`, - A content folder structure where planning and drafting are separated, - A Telegram group chat where different agents are attached to specific forum topics, - And one actual draft of an Inflearn course introduction created through the collaboration of the two agents. In short, this is a practical class that helps you design the first step of upgrading your Telegram bot from a "single AI assistant" into a "small AI team with divided roles."
48 learners
Level Basic
Course period Unlimited
News
2 articles
Hello.
In recent versions of OpenClaw since
v2026.7.1-beta.5, the onboarding method has changed from the existing menu-type screen to a Crestodian-based interactive onboarding method.Since it looks different from the original lecture screen, you might find it confusing, so we are providing the following guidance.
Target Audience
- Students who pull and install/practice with the latest Docker image
- Unlike the previous lecture screen, students who see the Crestodian TUI screen first when running
openclaw onboardIf you do not fall under the following:
- Students who are still using the old Docker image
It can proceed almost identically to the existing lecture screen, so
Please follow along with the lecture content.
What has changed in the latest version
Previously, the model selection menu often appeared immediately after running
openclaw onboard, butIn the latest version, a system agent for setup and repair called Crestodian runs first.
For example, you may see a guidance screen like the one below first.
- "Hi, I'm Crestodian — let's hatch your agent."
- "Say yes and I'll set all of that up now."
- "No usable model provider is configured, so the agent cannot answer yet. Configure a model provider now? Say yes or no."
In other words, in the latest version, there are cases where you must enter
yestwice to proceed to the existing model selection flow.How to proceed with onboarding in the latest version
When running
openclaw onboardin the latest version, please proceed as follows.1. When the first Crestodian screen appears, type
yesWhen you first see a phrase similar to the following:
- "Hi, I'm Crestodian — let's hatch your agent."
- "Say yes and I'll set all of that up now."
Enter the following into the terminal here.
yes2. If asked again whether to configure a model provider, enter yes one more time.
Next, a phrase similar to the following may appear.
- "No usable model provider is configured, so the agent cannot answer yet."
- "Configure a model provider now? Say yes or no."
Enter it once more here as follows.
yesIn other words, in the latest version, there are cases where you must type
yes→yestwice in a row and press Enter to proceed to the model selection and key entry stage.3. From this point on, it is the same as the lecture flow.
From then on:
- Select the model to use
- Enter Gemini API key
- Basic agent settings
It continues with a flow such as,
This part is not significantly different from the onboarding purpose explained in the lecture.
## Onboarding Completion Criteria
Once you have finished entering the Gemini API key and completing the settings, you may see a message similar to the one below.
- "Your agent is ready."
- "Model: google/gemini-2.5-flash."
- "Gateway: running at ws://127.0.0.1:18789."
- "Say talk to agent to meet your agent right here, or help for everything I can do."
If you see this screen, it means onboarding has been completed successfully.
In other words:
- Model setup complete
- Gateway connection complete
- Basic agent ready
You can consider it to be in that state.
How should I exit after completing the onboarding?
In the latest version, the Crestodian TUI screen may remain as is even after onboarding is complete.
In this case:
-
Ctrl + C- Press
Ctrl + Conce moreYou can exit the TUI by pressing Ctrl + C twice, as shown.
In the lecture, this part may not appear directly as the screen is based on an older version, but
Students using the latest version can exit by pressing
Ctrl + Ctwice after completing the onboarding.Summary
Students using the latest version only need to remember the following.
1. Run
openclaw onboard2. When the Crestodian information screen appears, type
yes3. If asked whether to configure the model provider, enter
yesagain4. Enter the Gemini API key and proceed with the setup
5. When you see the message
"Your agent is ready.", onboarding is complete6. Finally, press
Ctrl + Ctwice to exitExisting students / Old version users?
- Students who have not pulled the latest image
- Students who are still using the old version of the Docker image
may be similar to the existing lecture screen, so
You can proceed exactly as shown in the lecture.
Conclusion
To summarize,
In the latest version, the onboarding UI has changed to a Custodian-based interactive method, and accordingly, you can understand that the flow has changed to entering
yestwice, proceeding with model selection/key input, and finally pressingCtrl + Ctwice to exit.Students using the latest version, please refer to this notice to proceed.
Hello.
OpenClaw is still undergoing frequent version updates. There are about two changes that would be good for you to know, so I am sharing them with you.
Regarding the system configuration files automatically generated in the config folder before onboarding
In our lecture, the config folder was completely empty before OpenClaw onboarding, and the OpenClaw system configuration files were automatically generated once onboarding was complete. However, after the update, even before onboarding, running the docker-compose.yml file just once will cause OpenClaw to generate the basic required system configuration files in the config directory. Even if files generated before onboarding exist, you can proceed with the practice following the sequence shown in the lecture.
Regarding changes to the options selected by users during the onboarding stage
There are some options where the names or other details selected by users during the onboarding stage have been slightly changed or removed, so I will list the changes below.Section 3 > Lesson 11: Hello OpenClaw First Boot and System Check
Changes in the OpenClaw Onboarding Hands-on Practice
4 minutes 40 seconds
Config handlingconfiguration option(Existing) Select Update values -> (Changed) Select Review and update
How do you want to provide this API Key?configuration option(Changed) This option itself has been removed, so you can ignore it in the lecture video.
Default modelconfiguration option(Previous) You could select directly from all models -> (Changed) Select Browse all models, then manually enter the text 'google/gemini-2.5-flash' in the next step
How do you want to hatch your botconfiguration option(Existing) Select Do this later -> (Change) Select Hatch later

