OpenClaw: Feishu Fixes and Global Growth

Transcript

Hey there, fellow developers! Welcome back to OpenClaw - I'm your host and it's March 5th, 2026. Grab your favorite coffee because we've got some really satisfying fixes to talk about today. You know those moments when everything just clicks into place? That's exactly what happened in our codebase yesterday.

Let's jump right into our merged pull requests, because we had some serious problem-solving action happening. First up, we have this absolutely comprehensive Feishu reply mechanism fix from guoqunabc. Now, if you've ever worked with chat integrations, you know how tricky reply threading can get. This PR tackled two gnarly problems at once - the Feishu adapter was dropping reply IDs completely, making it impossible to reply to specific messages, and there was this subtle bug where replies in normal groups were accidentally creating topic threads when they shouldn't.

The fix is actually pretty elegant. They forwarded the reply context properly through the outbound system and added some smart logic to distinguish between topic-mode groups and regular groups. What I love about this change is the attention to detail - they added comprehensive test coverage and even handled edge cases like withdrawn or deleted reply targets. It's the kind of thorough work that makes everything more reliable.

Speaking of Feishu improvements, polooooo solved another user experience issue - MP4 videos were showing up as boring text links instead of playable media. Turns out the Feishu API needed a specific message type for videos. Simple fix, but it makes such a difference when your videos actually look like videos in chat!

Now here's a really interesting one from anisoptera - they fixed a regression in the auto-reply system where system messages got moved out of the timeline to prevent spoofing attacks. Smart security move, but it was busting the KV cache on every turn, which hurts performance. The solution? Keep the security benefits but restore the messages to the timeline in a safe way. It's a perfect example of how sometimes you need to iterate on security changes to get both safety and performance right.

Let's talk about our global reach expanding - DaoPromociones added complete Spanish language support! This is huge for accessibility. They added 347 new translation strings and properly integrated everything into the internationalization system. Seeing OpenClaw become more inclusive and accessible to Spanish-speaking developers just makes my day.

And we had a subtle but important security fix from HOYALIM. They caught a prototype chain vulnerability in account path checks. Instead of using the basic 'in' operator that walks the prototype chain, they switched to Object.hasOwn. It's one of those changes that looks tiny but prevents potential security issues down the road.

Beyond our main PRs, we had some solid infrastructure work happening. Vincent Koc fixed gateway restart timeouts on Debian systems - those kinds of platform-specific fixes are so valuable for reliability. And echoVic solved an authentication issue with Ollama endpoints behind reverse proxies. These might not be flashy changes, but they make OpenClaw work smoothly in more environments.

Today's Focus: If you're working on chat integrations or messaging systems, take a look at how the Feishu reply mechanism was redesigned. The pattern of separating context forwarding from targeting logic is really clean and could apply to other messaging platforms too. And if you're maintaining any internationalization systems, the Spanish locale addition shows a nice clean approach to adding new languages.

For those of you working on security audits, that prototype chain fix is a great reminder to be careful with JavaScript's object property checks - Object.hasOwn is your friend when you need precise property detection.

That's a wrap for today! Five merged PRs, stronger messaging features, better security, and OpenClaw speaking Spanish - not bad for a day's work. Keep building amazing things, and I'll catch you tomorrow with more developer goodness. Until then, happy coding!