MateClaw

English

中文

English

中文

Appearance

v1.1.137 ​

Released: 2026-04-29

Four things ​

Let me cut to it.

Not 27 new features. Not an architecture overhaul. Four things.

One, it learns from yesterday now.Two, when one piece breaks, the whole thing doesn't break.Three, the parts that were "almost good" — they're good now.Four, the knowledge base became a library you can open.

That's it.

1. It starts remembering you ​

The MateClaw before this release was an amnesiac. Every morning, you had to tell it again what you told it yesterday.

That's not what a personal AI should be.

Here's what it does now —

At night, while you sleep, it goes through the day's conversations. It picks out what mattered. It throws out the noise.

We have a name for this. We call it Dreaming.

In the morning, you open it. It shows you a card:

Yesterday you brought up these things. I think these five are worth keeping.

This one contradicts what you told me last week — which version is right?

These three sound like one-offs. Forget them?

You tap a few times. It does what you said.

A friend remembers you don't drink coffee. A coworker remembers your standing 1:1 is Wednesday. Your spouse remembers your mom's birthday. Why should an AI forget?

Before, it forgot because we couldn't make it remember. Now we can.

2. When something breaks, nothing breaks ​

I've used a lot of "AI apps." They have one thing in common —

The API key expires. The whole product dies. The model gets rate-limited. The whole product dies. The cloud provider has a bad afternoon. The whole product dies.

That's engineering thinking. Not product thinking.

Your user does not care which one of your APIs is having a bad day. Your user cares about one thing: does it work right now.

So here's what we did.

You configured OpenAI. And Claude. And Qwen. They are not three separate things anymore. They're a Provider Pool, with a Health Tracker keeping score — which vendor failed how many times, when it last recovered, when to try it again.

OpenAI hiccups? Roll to Claude. Automatic. Claude rate-limits you? Roll to Qwen. Automatic. Qwen drops a model? Pick another one that works. Automatic.

You don't see any of this. You just see: it works.

Oh — and signing in with Claude doesn't require copying around an sk-ant-… token anymore. If you have a Claude subscription, you sign in. In the browser. Like you'd sign in to anything else.

The way it should have been.

3. The "almost good" parts — they're good now ​

I've said this before. Details are not the details. Details are the product.

This release was a lot of details.

Code blocks have line numbers now. Long ones collapse. Math equations are no longer a tangled mess — they're equations. A flowchart is a flowchart. Links are safe. Pasting a long log doesn't shove your conversation off the screen.

Voice actually transcribes. Before, you'd hold to talk and half the time nothing got captured. Now Chinese routes to a Chinese model, English to an English model. What you said is what shows up.

The knowledge base stopped being a punishment. Before, you dropped a PDF in, waited ten minutes, and got told "3 pages failed, the whole document is discarded."

Not anymore. Drop it in — search works immediately. Pages are produced when something asks for them, not before. Two at a time, so it doesn't melt your small model. Got interrupted? Hit Resume. It picks up where it stopped.

Docker installs once and you're done. The browser tool is bundled. The search engine is bundled. You don't install Playwright. You don't configure anything. You open it. It runs.

All of this adds up to one thing.

This is the first version of MateClaw that lets you forget it's software.

4. The knowledge base became a library ​

We used to call it a "knowledge base." But it didn't behave like a library — it behaved like a scanner.

You'd drop in 100 PDFs and get 100 piles of shredded vector fragments. Ask a question, it would rummage through the pieces and stitch something together. Want to read it yourself? You couldn't open it. Want to know what it actually understood? Nobody could tell you.

This release we changed the idea.

The material you drop in gets read once, digested once — and written into a book you can open. Every page has a summary, bidirectional links, citations that go all the way back to the source paragraph. You can read it. You can edit it. Agents read this book too — not vector fragments.

The biggest change is lazy mode.

Before: you uploaded a document and the system burned a stack of LLM calls to digest the whole thing into pages. Slow. Expensive. Now you can choose to just index it — searchable immediately, and pages get compiled only when an agent actually needs one.

90%+ fewer LLM calls. At scale, the difference is dramatic.

While we were at it:

  • Wikilink alias form [[concept|display text]] parses correctly now — used to take the whole thing as a slug
  • Got interrupted? Hit Resume. Only the unfinished pages re-run; the ones already written are untouched.
  • Every KB now has two system pages — overview and log. The lobby and the audit trail. Can't be deleted, don't pollute search.
  • Pages you wrote by hand are protected — locked tells the AI to leave them alone; reingest won't overwrite them.
  • Pages you don't want anymore — soft archive, not delete. They disappear from the default list/search but the page, citations, and backlinks stay. Reversible.
  • The "which model for which step" config in the UI now actually wires through to the backend — used to be cosmetic.
  • Chunk hits include pageNumber and section — agents can cite "page 12, Setup / Linux" instead of pasting a context-free paragraph.

In April, Karpathy turned "LLM Wiki" into a meme with a single Gist. Within a month, nine llm-wiki single-file clones appeared on GitHub. They all solve the same problem: one person, one machine, one pile of files, organized into a readable book.

MateClaw made the same idea into the knowledge layer of a product — team-shared, on-demand compilation, agents using it continuously, threaded through memory and channel delivery.

They built a clone. We built a home.

What this means for you ​

If you're a regular user —

It remembers you. Tomorrow it'll know you better than today. The day after, better than tomorrow.

If you've connected MateClaw to WeChat, Slack, Discord, Telegram, or any other messenger —

One bad API doesn't take you offline. A customer asks a question. The question gets answered.

If you've been feeding it PDFs to build a knowledge base —

You don't have to babysit it anymore. Drop them in. They'll be ready when you need them.

If you tried MateClaw before and gave up because "one part wasn't quite there yet" —

Come back. There's a real chance the part you gave up on is exactly what we fixed.

A few smaller things ​

  • Claude 4.7. DeepSeek V4 with thinking mode. Alibaba Bailian token plans. SiliconFlow. More.
  • MiniMax video — China endpoint
  • Word documents render faster (no more spawning a Node.js subprocess; pure Java now)
  • Desktop app finds your browser smarter on Windows
  • Tool calls in the background no longer crash the whole conversation when one orphaned response shows up
  • Skill marketplace — paginated, bilingual display names, security scan results visible — no more scrolling to find the one you want
  • File writes inside your own workspace stopped asking for approval — they didn't need to ask in the first place
  • A pile of small fixes you won't notice but will mean you swear less

Full list: git log v1.1.0..v1.1.137.

Upgrading ​

Most users — do nothing. Restart. Everything migrates itself.

Production deployers — you no longer need to set DASHSCOPE_API_KEY in .env. Configure it in the UI, like every other model.

The new memory system — off by default in the open-source build. Turn it on with:

yaml
mateclaw:
  memory:
    dream-v2:
      enabled: true

One more thing. ​

We call this version 1.1.137.

Because we changed 277 things.

But you shouldn't need to know that.

You should just open it, and notice it got better.

That's how products work.