OpenClaw 4.20 Update: Cron Jobs That Actually Deliver

The OpenClaw 4.20 update just landed and if you automate anything on a timer, this is the release you've been waiting for.

Cron jobs got rebuilt.

No more silent failures at 3am.

No more "delivered" jobs that actually skipped.

No more memory leaks from stacked jobs.

Let me break down what changed — and everything else worth knowing from the 4.20 release.

Why the Cron Job Rebuild in the OpenClaw 4.20 Update Matters

"Cron jobs" just means scheduled tasks.

It's the thing that lets OpenClaw do work on a timer without you touching it.

If you run automations — customer follow-ups, reminder texts, content drops, lead nurture — this is the feature you rely on.

And in previous versions, it had nasty bugs.

What was broken before 4.20

Jobs would say "delivered" but silently keep skipping sending.

Jobs set to no-delivery would throw false errors.

Jobs that ran every hour would pile up and eat your memory.

Eventually the gateway would crash.

You'd wake up in the morning and realise your automation had fallen over hours ago.

What the OpenClaw 4.20 update fixed

Three big rebuilds.

One: The runtime state got split into its own file so your job list stays clean.

Two: Main session delivery got fixed — when a scheduled job wakes up and wants to reply in a chat, it lands in the right chat now.

Three: If you set up a job that posts to multiple channels, OpenClaw checks the setup when you save it.

So you can't accidentally build a broken job that fails at 3am while you're asleep.

A practical example

Say you run a local gym.

You want an agent to text every new sign-up on day 3 with a pep talk and again on day 7 asking how the first week went.

With the new cron in 4.20, you set it up once.

It runs forever.

If something breaks, you get a real error.

Not fake success.

Same for coaches.

Day one — welcome message.

Day three — check-in.

Day seven — review call booking.

All on autopilot.

While you focus on the actual coaching.

🔥 Want to build reliable scheduled automations inside OpenClaw? Inside the AI Profit Boardroom, I walk through the exact cron job setups I use for follow-ups, reminders, and content scheduling. Full 30-day OpenClaw roadmap, four weekly coaching calls, 2,800 business owners inside — plus the map so you can find OpenClaw users near you. Someone's always online. → Get the full roadmap here

Kimi K2.6 Inside the OpenClaw 4.20 Update

Before 4.20, using Moonshot's Kimi model inside OpenClaw put you on K2.5.

Now it's K2.6 by default.

K2.5 stays available if you need it.

What K2.6 does better

Kimi is open-source, fast, cheap.

K2.6 is much better than K2.5 at thinking, replying, and handling tools.

That last one — tools — is what matters most for agents.

If you were running Kimi before, your agent just got smarter without you doing anything.

Where K2.6 shows up inside OpenClaw

Web search uses K2.6 when you pick the bundled Kimi setup.

Media understanding uses it.

Token cost tracker knows K2.6 pricing so you can see task cost before running.

Thinking keep all

New thinking mode you can leave on permanently.

Model thinks before every reply.

Doesn't guess.

Works out the answer first.

Kimi is one of the cheapest models you can run.

Now it reasons like the expensive ones.

Lower cost + better answers.

iMessage Agents Actually Work in the OpenClaw 4.20 Update

This is the most dramatic fix in the whole release.

If you've got a Mac on the newest macOS and you tried running an AI agent through iMessage using Blue Bubbles before — you know the pain.

Messages wouldn't send.

Or they'd take a full minute and just break.

You'd hit send and sometimes the message would vanish into nothing.

All fixed in 4.20.

The three fixes

They pushed the send time limit from 10 seconds to 30 seconds.

They made the system use a private path on new macOS so text actually goes out.

They removed the weird error breaking plain text on TAH.

What this opens up

Run an AI agent from your Mac.

Text customers over iMessage like a real person.

Messages actually land.

Local shop owner getting texts at 10pm about opening hours — agent replies straight away.

Coach getting DMs from leads on weekend — agent books them into a call.

Tapbacks fallback

Agent reacts with any non-standard emoji?

Before 4.20, the whole reaction would fail.

Now OpenClaw falls back to a related standard reaction.

Something always shows up.

Customer still feels seen.

iMessage over SMS

Person has both iMessage and SMS with the same number.

OpenClaw now picks iMessage first.

Before it sometimes sent SMS when the blue bubble was working.

Now it does the right thing.

/think Command Smarter in the OpenClaw 4.20 Update

Before 4.20, telling a model to think when it couldn't think would break mid-task.

Now OpenClaw checks first.

It knows what each model can handle.

No more random errors.

And when you turn thinking off, it stays off.

Some models used to quietly keep thinking anyway.

Gone.

Agent is more reliable now.

Doesn't break halfway through.

Security Locked Down in the OpenClaw 4.20 Update

A bunch of sneaky attacks got blocked.

SSRF guard

Bad requests can't trick your server into doing something silly.

Workspace ENV injection blocked

Someone drops a weird file in your project folder — it can't silently change your setup.

Agent can't rewrite its own config

This was scary.

Before 4.20, the AI could technically rewrite parts of its own config.

Change its own permissions.

Change the tools it has access to.

In 4.20, the model can't touch sandbox settings, trust rules, or MCP server configs.

Even if it tries to sneak an edit, it gets blocked.

Device pairing tightened

Connect a phone or a laptop to your OpenClaw.

That device only sees its own pairing info.

Can't peek at other devices.

Can't approve them.

Failed connection now shows a real error instead of a useless generic message.

Memory and Sessions in the OpenClaw 4.20 Update

This is where things got messy before.

The pile-up bug

Heavy cron and session usage meant old sessions piled up.

Gateway ran out of memory.

Crashed.

In 4.20 there's a built-in cap and age-based cleanup.

Old sessions get pruned automatically.

Gateway stays healthy even at hundreds of jobs per day.

Cost tracking honest now

Session saved multiple times used to mean costs counted 2x or 10x.

Your numbers were wrong.

Now snapshot properly.

Month-end number is real.

/new and /reset actually reset

Before, starting a fresh session kept old model/provider choices stuck.

You thought you were on Kimi K2.6 but were stuck on some fallback from three mistakes ago.

Now those commands clear stale stuff while keeping intentional choices.

Matters when you run one agent for replies and another for content.

Each session starts clean.

Personality Picks Up Better in the OpenClaw 4.20 Update

OpenClaw uses SOUL.md and IDENTITY.md files to define your agent's voice.

Before, GPT-5 and Codex were stiff about these.

They'd read them.

But replies still felt like a corporate support bot.

In 4.20, GPT-5 and Codex pick up personality properly.

The team described the goal as "more like your weirdly capable little friend and less like a polished customer support automation".

Those are their exact words.

Why it matters

If your agent handles DMs, messages, texts, or leads, it has to sound like you.

Not a generic chatbot.

4.20 makes that way easier on GPT-5 and Codex.

Video notes + links to the tools 👉 here

Channel Updates Across the OpenClaw 4.20 Update

Smaller but worth knowing.

Auto-reply is context-aware

DM = helpful reply.

Group = quiet unless tagged.

Agent doesn't spam but still helps 1-on-1.

Setup wizard cleaner

First-time setup now has a proper walkthrough with a loading spinner.

Clear headings, clear warnings.

Anyone can follow it.

Telegram polling grace period

Longer before OpenClaw calls the connection broken.

Stateless reactions work properly.

Matrix allow-list without restart

Change settings on the fly without restarting the whole channel.

Manus live draft preview

Agent shows a live draft preview as it writes.

Final reply lands in place.

Feels way more natural.

Discord fixes

/think only shows options that work for your model.

Missing slash commands don't crash anymore.

What the OpenClaw 4.20 Update Means for Your Business

Zoom out — five things matter:

1. Kimi K2.6 inside: smarter, cheaper model by default, thinking mode makes it more accurate at same cost.

2. iMessage agents real: huge channel for business owners whose customers text them.

3. Scheduled tasks deliver: cron jobs finally reliable, no silent failures.

4. Security locked down: hand it to a team, don't worry about them or the AI breaking things.

5. Personality picks up: agent sounds like you on GPT-5 and Codex.

If you're pairing this with other automation layers, my Hermes Agent Mission Control post covers the multi-agent setup.

Be Honest About the OpenClaw 4.20 Update

Most AI agent tools are rough.

They break.

They hallucinate.

OpenClaw 4.20 is still going to be buggy in spots.

When I've used Hermes, it sometimes feels smoother in certain areas.

Both tools are getting better.

I switch between them depending on the task.

Sometimes updating your setup breaks things and you have to restart the whole thing.

Set up an OpenClaw backup first so you can restore if something breaks.

How to Install the OpenClaw 4.20 Update

Type update inside OpenClaw.

Pulls down the latest version.

Under a minute on most setups.

OpenClaw 4.20 Update FAQ

Does the OpenClaw 4.20 update fix cron job reliability?

Yes — rebuilt from the ground up.

No more silent delivery failures, no more false errors, no more memory pile-up.

Can I use Kimi K2.5 after installing the OpenClaw 4.20 update?

Yes, K2.5 is still there.

K2.6 is just the new default.

Is the OpenClaw 4.20 update free?

Yes — included in your existing subscription.

Does the OpenClaw 4.20 update break existing cron jobs?

Most jobs continue working.

The runtime state moved to its own file — review your job list after updating.

What's the biggest improvement in the OpenClaw 4.20 update?

For automation-heavy users, it's the cron rebuild.

For customer-facing business owners, it's iMessage agents that finally send.

How do I update to the OpenClaw 4.20 update?