TAG
OpenClaw
A curated slice of the YunLab archive.
This tag is a focused route through the public workbench, not a keyword dump. Read this group, then return to the full tag index.
Filed under
- Business Notifications vs System Notifications: Notification Isn't One Semantic — Split Into Two Channels Fixed two versions in one day to handle what looked like a small notification problem — Suwan's morning brief got buried under the watchdog title in Feishu, and the sender fell back to Zhao Zilong. Took both fixes to learn: business delivery and system health are two different notifications.
- Day 1 Blew Up at Dawn: I Didn't Expect to Write a Watchdog on Trial's First Day Day one of a seven-day trial run: all four morning tasks completed, all four Feishu notifications failed. Root cause was the macOS LaunchAgent default PATH not including Homebrew — an old trap, but it pushed me to write the first version of a watchdog.
- Jiyanran Voice Workbench: Why a Voice Entry Point Needs Three Layers of Decoupling A local voice assistant looks simple, but the voice entry point is the layer that couples most easily. I split it into four pieces — OpenRoom front end / voice-bridge / avatar-bridge / OpenClaw — three independent services, each with its own mock fallback, each with its own risk-gate. Here is why.
- Mission Control and Studio: When Control Planes Start to Overlap Local Studio + Mission Control Web + a future Gateway — all three can manage agents, tasks, and audit. Each one makes sense on its own; put them together and they start fighting over responsibility. How I split things now, where the hard parts are, and what I'm still changing.
- Twelve OpenClaw Copies Later: When Paths and Root Directories Become Risk I ran a find on my home directory and turned up 12 roots with the openclaw keyword. Only 2 are actually running; the other 10 are historical remnants. The copy isn't dangerous — the copy used as authoritative is. Five typical risks plus a five-step handling rule.
- From Logs to Knowledge: How I Decide What to Keep and What to Drop The hardest part of cleaning up an AI project's knowledge base isn't writing new content. It's deciding whether the old material should stay. Two filtering layers, six canonical-source priorities, a three-state freshness marker — I only learned each of these after getting burned.
- OpenClaw Studio RC1: Local Loop Closed, External Gates Held, and What I'm Still Working On A retrospective on pushing OpenClaw Studio from stage one to stage seven in a single day and shipping RC1 — three methods, seven stages, what actually runs today, and the large pile that's still not closed.
- From Information to Article Once the information agent has pulled content in, the hard part isn't piling up links. It's turning them into candidates that the content agent can actually judge, sort, and write from. What's missing between Shen Zhixing and Suwan isn't more sources — it's a content chain that can be handed off.
- My Knowledge Model What I eventually figured out: the dangerous thing in an AI project isn't forgetting — it's remembering wrong and continuing to build on it. My Knowledge Model isn't about storing more material; it's about compressing the site into judgments, rules, and handoff entries that next time can actually use.
- Canonical Source Rules What I eventually figured out: in an AI project, the dangerous thing isn't a lack of material — it's that every piece of material can spin its own story. The canonical source rule is about deciding who has standing to answer the current question, first.
- An Information Agent Is Not a Fetcher A retrospective on building Shen Zhixing: why 40 sources running doesn't mean done, why 257 fetchable sources still isn't Day 1, and how I stopped letting GPT's false sense of completion pull me off course.
- From Agent Roles to Work Contracts What I'm coming around to: multi-agent isn't about writing a few more roles, it's about writing down the contract a small company needs to actually keep collaborating.
- From Running to Trustworthy Booting up, holding a conversation, calling a tool — that's only step one. What I added after that: a file-based canonical source, task contracts, memory as an asset, an evidence chain, and a real handoff mechanism.
- From Internal Engineering Notes to Public Writing Potholes I hit while turning internal engineering material into public YunLab articles: the issue isn't just redaction. It's separating the working backstage from the experience that can actually be left in public.
- OpenClaw Agent Settings What I'm coming around to: the first step in building an agent isn't writing features — it's writing the taste.
- Don't Stock the Tank Before You Finish the Build How I understand OpenClaw foundation work: installing it just hands you the keys; the workspace is the renovation plan.
- A Content Agent Aesthetic Sample An aesthetic sample for a content-type agent: not 'can write,' but 'knows what's worth writing.'