Steadybase
OpenClaw Origin

The Fork Story

How and why Steadybase was forked from OpenClaw — and the vision behind the transformation.

The Fork Story

Steadybase began as a fork of OpenClaw, an open-source AI chat application. This page tells the story of why we forked, what we kept, and where we're going.

What is OpenClaw?

OpenClaw is an open-source AI chat application — a clean, well-built single-user chat interface for interacting with LLMs. It provides:

  • A React-based chat UI
  • Express backend for LLM API routing
  • Conversation history management
  • Basic authentication

It's an excellent starting point for anyone building an AI-powered application.

Why We Forked

OpenClaw solves one problem well: chat with an AI. But Steadybase needed to solve a fundamentally different problem: deploy autonomous AI workers to execute GTM workflows.

The gap between "chat with AI" and "run an AI workforce" is enormous:

RequirementOpenClawWhat Steadybase Needed
UsersSingle userMulti-user with roles
AI interactionChat (request/response)Autonomous workflows (multi-step, long-running)
StateStateless (per-session)Durable (survives crashes, persists across days)
MemorySession onlyHierarchical, persistent, compressed
AgentsOne (the chat model)8 specialized workers + coordinator
ModelsSingle providerMulti-LLM (Claude, GPT-4o, Gemini)
OrchestrationNoneTemporal Cloud workflows
Human oversightN/ASignal-based approval gates

What We Kept

From OpenClaw, Steadybase inherited:

  • React foundation — The dashboard UI builds on OpenClaw's React SPA structure
  • Express server — The API server uses OpenClaw's Express setup as its base
  • TypeScript — The entire codebase remains TypeScript
  • Chat interface — The Brain chat feature evolved from OpenClaw's core chat

The Vision

Steadybase transforms OpenClaw from a chat application into an agentic platform:

OpenClaw (Chat App)          Steadybase (Agentic Platform)
┌──────────────┐            ┌──────────────────────────────┐
│              │            │  8 Workers  │  6 Workflows   │
│  User ↔ LLM │     →      │  Memory     │  Multi-LLM     │
│              │            │  Nexus      │  Human-in-Loop │
└──────────────┘            └──────────────────────────────┘

The fork was not about fixing OpenClaw — it was about building something entirely different on top of a solid foundation.

Open Source Commitment

We respect OpenClaw's open-source roots. Our additions — Temporal workflows, hierarchical memory, multi-agent coordination — are architectural extensions, not replacements. The original chat capability still exists as the Brain API.

On this page