Multi-Framework Support: Choose Your AI Agent Orchestrator

Until now, Better OpenClaw generated stacks exclusively for the OpenClaw agent framework. That changes today. v1.3.0 introduces multi-framework support with 8 pluggable agent frameworks, companion framework multi-select, and framework-aware stack generation across the CLI, Web UI, MCP tools, and REST API.

The Problem: Framework Lock-In

The AI agent ecosystem is exploding. OpenClaw is powerful, but it's not the only game in town. Teams using CoPaw for cooperative multi-agent workflows, ZeroClaw for zero-config simplicity, or MemU for memory-first architectures were stuck writing Docker Compose files by hand. Better OpenClaw's infrastructure generation—dependency resolution, port management, secret generation, health checks, reverse proxy configs—was locked to a single framework.

We wanted to fix this without forking the codebase 8 times.

8 Supported Frameworks

Here's what's available:

Framework	ID	Best For
OpenClaw	openclaw	Full-featured stacks with gateway, mission control, and Tailscale networking
CoPaw	copaw	Cooperative multi-agent workflows with shared memory
NanoClaw	nanoclaw	Lightweight single-agent runtime for resource-constrained environments
NanoBot	nanobot	Minimal bot framework with plugin architecture
ZeroClaw	zeroclaw	Zero-config agent framework with convention-over-configuration
MemU	memu	Memory-first agent framework with persistent context (requires PostgreSQL)
Claude Code	claude-code	Anthropic's CLI agent for software engineering tasks
Codex	codex	OpenAI's CLI agent for code generation and editing

Each framework gets its own gateway container, CLI services, network configuration, and environment variables. Non-OpenClaw frameworks automatically skip Convex, Mission Control, and Tailscale—services that are specific to the OpenClaw ecosystem.

How to Choose a Framework

CLI

The interactive wizard now includes a framework selection step. Or use flags for non-interactive mode:

# Use ZeroClaw as primary
npx create-better-openclaw my-stack --primary-framework zeroclaw --yes

# Run multiple frameworks side-by-side
npx create-better-openclaw my-stack \
  --services postgresql,redis \
  --primary-framework memu \
  --companion-frameworks copaw,nanoclaw \
  --yes
		

Web UI

The new FrameworkSelector component in the visual stack builder at /new lets you pick a primary framework (single-select) and companion frameworks (multi-select) with a visual grid. Dependencies update in real-time as you switch frameworks.

MCP Tools

The generate-stack MCP tool now accepts primaryFramework and companionFrameworks parameters. AI agents can generate stacks for any framework through natural conversation:

"Create a ZeroClaw stack with PostgreSQL and Redis"

REST API

Both POST /validate and POST /generate endpoints now accept the framework parameters:

curl -X POST http://localhost:3456/api/v1/generate \
  -H "Content-Type: application/json" \
  -d '{
    "projectName": "my-stack",
    "services": ["postgresql", "redis"],
    "primaryFramework": "zeroclaw",
    "companionFrameworks": ["copaw"]
  }'
		

Companion Frameworks

The real power comes from hybrid stacks. Select a primary framework for your main orchestration and add companion frameworks that run alongside it. Each companion gets its own gateway container and CLI service, sharing the same backing infrastructure (databases, caches, search engines).

Use cases for companion frameworks:

• Run Claude Code for coding tasks while MemU handles long-term memory and context
• Use OpenClaw as your primary with NanoClaw running lightweight side agents
• Deploy CoPaw for multi-agent coordination alongside Codex for code generation

Technical Architecture

Under the hood, multi-framework support uses a registry pattern. Each framework is defined by an AgentFrameworkDefinition interface in core/src/frameworks/:

• Mandatory services: Framework-specific required services (e.g., MemU requires PostgreSQL)
• Excluded services: Services to skip for non-OpenClaw frameworks (Convex, Mission Control, Tailscale)
• Gateway/CLI config: Per-framework container names, images, ports, and environment variables
• Network naming: Each framework gets its own Docker network name derived from its ID

The resolver, composer, and README generator are all framework-aware. When you select a framework, the entire stack adapts—from dependency resolution to the generated documentation.

Getting Started

Update to the latest version and try it out:

npx create-better-openclaw@latest my-stack
		

The wizard will ask you to choose your framework. Or jump straight in with a non-OpenClaw framework:

npx create-better-openclaw my-stack \
  --preset researcher \
  --primary-framework zeroclaw \
  --yes
		

All 94+ services, 10 skill packs, and 9 presets work across all 8 frameworks. Your infrastructure, your choice of orchestrator.