maely
MaelyClaw · v0.x · Open source

One process.
Unlimited lanes.
Ships code while you sleep.

Lightweight autonomous agent engine — open source, multi-provider, and built for real dev workflows. Plan, code, QA, PR, merge — on a cron, in the background.

View on GitHub $ npm i -g maelyclaw

Lines of TS

~4K

Process

one

License

MIT

zsh — maelyclaw live 
~/maely-health ❯ maelyclaw start
[health] planner picked task #1284
[health] worker spawned in worktree/h-1284
[health] coding... "Patient timeline pagination"
[health] qa: tests pass · type-check clean
[health] opened PR #1284 · awaiting merge

~/maely-health ❯ ▍

Capabilities

Everything you need.
Nothing you don't.

1.0

Independent Lanes

Each lane is a cron-scheduled, autonomous worker with its own backlog, worktree, and review cycle. Spin up as many as your machine can hold.

2.0

Multi-Provider

Claude, Codex, OpenAI-compatible. Swap providers per lane, per task, or by cost ceiling. No lock-in to one model family.

3.0

TUI Operator Console

A dashboard for humans. Watch lanes, kill workers, replay tasks, and drop into an embedded CLI without leaving the terminal.

4.0

MCP Server

Lanes expose themselves over MCP. Your IDE, your agents, and your tools all speak the same protocol — no custom glue.

5.0

Full Dev Pipeline

Plan → code → QA → PR → merge. Each step is a contract another agent can pick up. Failed QA? The worker self-fixes up to two attempts before paging a human.

6.0

Worker Lifecycle

Spawn, monitor, timeout, reap, respawn. Workers are cattle, not pets. Crash loops die fast; healthy lanes run for weeks.

Architecture

From backlog to merged PR. 

BACKLOG ───▶ Planner ───▶ Worker ───▶ QA ───▶ Closer ───▶ PR
   ▲                                                       ▼
Feedback ◀─────────────────  Human  ─────────────────▶ Production
  1. 1

    Planner picks a task

    Lane-planner selects the highest-priority task from the backlog and writes a plan. The plan becomes the contract every downstream worker reads.

  2. 2

    Worker writes code

    Spawns a coding worker (Claude, Codex, or any model) in an isolated git worktree. Writes code, commits, opens a PR — no humans on the critical path.

  3. 3

    QA validates

    Lane-closer spawns a QA worker. If QA fails, the lane auto-spawns a fix worker (up to 2 attempts) before paging a human.

  4. 4

    Merge & ship

    QA passes, the feature PR merges, and a final PR opens against main. Lane-health monitors workers, handles timeouts, and respawns the dead.

Why MaelyClaw

Built different.

vs OpenClaw

Lighter by design.

· MaelyClaw OpenClaw
Lines of code ~4K TS 500K+
Architecture One process Microservices
Provider Claude-native Anything, anywhere
Time to first PR Minutes Days

vs NanoClaw

Dev agent, not chatbot.

· MaelyClaw NanoClaw
Primary loop plan→code→QA→PR chat→answer
Git Worktrees + PRs None
QA Built-in Manual
Surface Lanes Single thread

Install

Three commands. Then it ships for you.

install · 30 seconds v0.x 
$ npm install -g maelyclaw
$ maelyclaw init # scaffolds maelyclaw.config.json
$ maelyclaw start

# In another tab — TUI dashboard + embedded CLI
$ maelyclaw console
Star on GitHub
MIT TypeScript ~4K LOC