‹ Back to notes

Field Note

Don't Stock the Tank Before You Finish the Build

别急着养虾,先装修

How I understand OpenClaw foundation work: installing it just hands you the keys; the workspace is the renovation plan.

OpenClawAgentWorkspace个人知识系统
Watercolor sketch: a top-down view of a desk — scattered sticky notes on the left, tidy notebooks and a filing cabinet on the right

OpenClaw foundation notes

Installed just means you have the keys.

There are already lots of tutorials on how to install it, how to plug in models, how to add skills. What I think no one's spelled out clearly is: stock OpenClaw is more like a bare-shell apartment.

Livable doesn't mean nice to live in; able to chat doesn't mean smooth to work with. Walking in right after a fresh install with "hi, introduce yourself" is a bit like grabbing the keys and going straight in to sleep on the floor.

OpenClaw is like a bare-shell apartment that hasn't been renovated

01 / Usable and smooth

A lot of people aren't bad at using it — the foundation isn't built

People using "the lobster" easily fall into one illusion: it can chat, it can call tools, it can hold a bit of context — so the system is built.

That's "usable," sure. But between "usable" and "I'd hand it the real thing" there's a long stretch. Having to re-explain every time, the style drifting, the boundary not steady — that's not on the model alone.

The way I think about it: model and skills are the furniture; the workspace is the renovation plan.

The difference between OpenClaw usable and smooth
The workspace is the foundation structure of OpenClaw
AGENTS.md

Site rules

What's allowed, what isn't, what has to stop and check with me.

SOUL.md

Speaking temperament

How it expresses a judgment, admits uncertainty, flags risk.

USER.md

Knows who I am

What I care about, what I dislike, what actually counts as done.

TOOLS.md

Tool brakes

The stronger the tool, the more it needs to know where to let go and where not to touch.

MEMORY.md

Long-term shelf

Not every chat is worth keeping — what matters is judgment reusable later.

skills/

Workshop

Put the recurring flows in here so next time we don't have to improvise.

AGENTS and TOOLS are OpenClaw's rules and brakes

02 / Brakes first

An over-eager agent breaks things too

Ask it to take a look, it goes ahead and edits; ask it to analyze, it starts refactoring. AGENTS and TOOLS have to hold the boundary first.

The relationship between OpenClaw's memory folder and MEMORY.md

03 / Memory has to be accurate

Memory isn't a favorites folder

`memory/` can hold the running log; `MEMORY.md` should hold long-term assets. Save everything and you find nothing.

skills are OpenClaw's workshop and process sediment

04 / Skills are craft

Install less, sharpen more

Writing one article can be done on the fly. After ten, the flow should sediment: audience, angle, structure, draft, check, publish.

Multi-agent is a small team with a division of labor

05 / Multi-agent

Not just stocking more lobsters

Multi-agent is more like a small team. Research, writing, execution, audit need their own roles — and they need to actually hand off through handoff files and outputs.

06 / Where I land now

Actually good means continuable

What you did today, tomorrow can still pick up; the judgment from this session, the next session can still find; what one agent finishes, another agent can take over.

Chat is like air — it flows past and it's gone. Files are like the floor — you can put weight on them.

So I'd rather go back and fix the workspace first: get the rules, personality, user preferences, tool boundaries, memory, and skills lined up. Otherwise you're buying expensive furniture inside a bare-shell apartment — it looks pricey, but it's awkward to use.
The maturity path of OpenClaw from booting up to being handoff-able and auditable

Turn this note into a route

After reading, ask a follow-up, return to the curated archive, or use the tag index to follow the same thread.

Ask about this Open archive Browse tags