Hands-On OpenClaw: Build Your Own Telegram AI Bot on Ubuntu with Juju and LXD
- Time
- 2026-08-09 13:20 ~ 14:20
- Speaker
- 李世元 / Shih-Yuan Lee / FourDollars / $4
- Room
- TR210
- Co-write
Abstract
This is a bring-your-laptop workshop designed to help every participant get OpenClaw running on their own Ubuntu machine within 50 minutes using Juju and LXD—and receive their first AI reply over Telegram. This workshop uses a free API key from Google AI Studio (ai.dev) as the AI source, so all you need is a Google account—no paid subscription required. The session covers four segments: (1) Environment setup—Ubuntu 24.04, LXD snap, Juju installation, and local cloud initialization; (2) Deploying the OpenClaw Charm—running juju add-model, juju deploy openclaw, and setting the free API key obtained from Google AI Studio; (3) Telegram integration—creating a bot via BotFather, applying the token with juju config telegram-bot-token, and chatting with the bot live; (4) Advanced tweaks and observation—using openclaw tui to interact with the AI assistant directly from the terminal and observe the conversation in real time.
All steps come with a pre-prepared command cheat sheet, and the instructor (and helpers, if available) will assist on the floor. Prerequisites: A machine running native Ubuntu 24.04 (laptop, desktop, or VM)—WSL2 is not supported as an LXD host; please use native Ubuntu or an Ubuntu VM—internet access, a Google account, and a Telegram account.
More info: https://events.canonical.com/event/146/contributions/931/
Speaker
李世元 / Shih-Yuan Lee / FourDollars / $4
用 Linux 超過 26 年、從事 Linux 相關工作 21 年，其中 16 年在 Canonical。主要在做「讓 Ubuntu 能順順在各種筆電上跑起來」這件事。日常工作包括跟硬體廠商打交道、追各種奇怪的驅動程式 bug，以及建一堆自動化讓大家不用手動做重複的事。閒暇之餘會貢獻開源專案，有時候是修 kernel，有時候是跟上游維護者吵架然後說服對方接受你的 patch。是 Debian 開發者，主要意義是對套件命名有很多意見。
目前正在尋找新機會。如果你在找一個能把 Linux 跑好、跟硬體廠商打過交道、又會把重複的事自動化掉的人，歡迎聊聊。
A Linux user for over 26 years and professional for 21, Shih-Yuan has spent the last 16 of those at Canonical making sure Ubuntu actually works on the laptops people buy. That means working with hardware vendors, chasing down driver bugs, and building the automation that keeps everything running quietly in the background. He contributes to open source projects when he can — sometimes patching the kernel, sometimes getting into a good argument with upstream maintainers. He's a Debian Developer, which mostly means he has opinions about package naming.
He's currently open to new opportunities. If you need someone who can make Linux behave on real hardware — and automate away the parts that don't — he'd be happy to talk.