إنتقل إلى المحتوى الرئيسي
Everett
MicroClaw Maintainer
View All Authors

Being More Human — and a Specialist Team Behind It: Chat Realism, Concurrent Specialists, 42 Built-in Skills, Graph-Augmented Recall

· 10 دقائق قراءة
Everett
MicroClaw Maintainer

The previous release (Hermes Catch-up) filled in the runtime's plumbing: a user model, a skill lifecycle, prompt-cache economics, checkpoints. This one is about something harder to measure and easier to feel — making MicroClaw behave like a person, and specifically like a very capable person who happens to have a team behind them.

The thesis, lifted from the design docs that drove this release: "being human" is two layers, and the magic is in the contrast between them.

On the surface they chat with you casually, lightly, in short replies. But the moment you need something real, they quietly pull in a mathematician, an illustrator, a researcher — several lines running at once — and come back with "done, here's the answer."

MicroClaw used to be robotic on both layers: it dumped long answers up top, and although it could run sub-agents concurrently, it worked in silence until everything was finished. This release reworks both — and gates every outward-facing, proactive behavior behind a default-off switch.

Hermes Catch-up: User Model, Skill Lifecycle, Multimedia, Defensive Defaults — and Round 2 (Prompt Cache, Fuzzy Edit, Checkpoints, @-Refs)

· 14 دقائق قراءة
Everett
MicroClaw Maintainer

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.

Maturity Hardening: Security Audit and Self-Checks

· 6 دقائق قراءة
Everett
MicroClaw Maintainer

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.

Built with Rust: MicroClaw as a Multi-Channel Agent Runtime

· 5 دقائق قراءة
Everett
MicroClaw Maintainer

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.org/docs/quickstart

MicroClaw system architecture

MicroClaw vs NanoClaw vs OpenClaw: Updated Three-Path Comparison

· 3 دقائق قراءة
Everett
MicroClaw Maintainer

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.

Three-path capability spectrum