Workspace, agent, and task wizards.
Guided creation flows make the core AgentOS objects easier to set up without turning the product into a black box. You get structure on top, flexibility underneath, and OpenClaw still remains the runtime base.
What the wizards do
Set up the project surface where files, docs, memory, and deliverables stay anchored.
Define a worker with a clear role, operating boundaries, and the right workspace context.
Turn intent into scoped work with explicit outputs, so an operator can inspect and steer it.
Reduce setup friction while keeping the underlying OpenClaw runtime visible and controllable.
Why it matters
- Teams can move faster from idea to a usable operating surface.
- Structures stay consistent across many projects and workspaces.
- Operators can read the system without decoding raw backend internals.
- Each object stays anchored to real work instead of abstract configuration.
The mental model
A workspace is the project surface. An agent is the configured worker. A task is the unit of work. The wizard layer helps you create those objects in the right order and with enough structure to remain operable later.
FAQ
What do the wizards create?
They guide you through creating workspaces, agents, and tasks with a consistent structure so the operating model stays clear.
Do the wizards hide OpenClaw?
No. The wizards are a usability layer on top of OpenClaw. They keep the backend flexible while making the human workflow easier to manage.