The Hermes Catch-up release is MicroClaw's largest single-branch update so far: 37 commits, 8400 lines, 53 files. The headline number is misleading, though — what matters is which layers of the agent runtime got filled in.

The inspiration is hermes-agent v0.10.0. Hermes runs on Python; several of its design decisions land more naturally on a Rust + SQLite stack: FTS5 ships with bundled SQLite, cargo audit / cargo deny lock dependency posture at compile time, and the artifact pattern (large tool result on disk, fetch slices by id) costs almost nothing in a single-binary deploy.

So this isn't a port — it's a re-application of patterns hermes already validated, drawn against MicroClaw's engineering boundaries.

The latest maturity hardening pass in MicroClaw is not a flashy new model integration or another channel adapter. It is the kind of release work that makes the next ten releases safer: dependency audit gates, operator-visible risk checks, explicit support policy, and stricter release verification.

For an agent runtime, that matters. If your bot can execute tools, store memory, expose Web APIs, and run background work, "it compiles" is not enough. You also need repeatable checks around security posture, release shape, and operator safety defaults.

MicroClaw now includes a dedicated HTTP hook trigger surface for external automation.

This closes a common integration gap: webhook systems and scripts can trigger agent runs directly, without relying on chat-native ingress or static scheduler-only flows.

The old way to delegate work inside an agent was to nest another mini-agent loop inside one tool call.

MicroClaw is moving past that shape with session-native subagents: asynchronous runs with IDs, lifecycle state, limits, and follow-up controls.

Telegram forum groups are useful until every thread shares one agent memory buffer.

MicroClaw's Telegram topic mode fixes that by routing each forum topic as its own chat session, while still replying inside the original Telegram thread.

This weekly update summarizes what changed in MicroClaw during February 20, 2026 to February 26, 2026.

The pace was high: channel coverage expanded, runtime reliability was hardened, and setup/config workflows became much better for multi-account bot operations.

MicroClaw has moved quickly in February, with significant updates across ClawHub integration, voice handling, path compatibility, modularization, web/auth hardening, and release automation.

This post summarizes the direction and outcomes based on the 50 most recent commits on main.

MicroClaw is no longer just a channel bot. In its current form, it is a Rust multi-channel agent runtime with a shared agent engine, provider abstraction, durable session state, and layered memory.

It supports Telegram, Discord, Slack, Feishu/Lark, IRC, and Web through adapters, while keeping one core execution path for reasoning and tool use.

Source code: https://github.com/microclaw/microclaw Quick Start: https://microclaw.ai/docs/quickstart

If you are building a personal AI assistant around chat, you usually choose among three distinct paths:

1. Minimal and isolation-first
2. Broad platform with high feature surface
3. Balanced runtime with practical built-ins

This comparison is updated using publicly available docs/repos as of February 14, 2026.

MicroClaw is a Rust-based AI assistant that treats chat as an execution surface, not only a text interface.

It can run shell and file tools, browse the web, schedule jobs, and persist memory/session state so multi-step work can continue across turns.