Overview

ElasticClaw is an open source workflow system for coding agents: issue tracker triggers, workflow stages, scoped GitHub credentials, and self-hosted execution.

What is ElasticClaw?

ElasticClaw turns external events into repeatable coding workflows. A workflow can watch Linear, GitHub Issues, Shortcut, webhooks, GitHub releases, or any other signal you want to use as a trigger; start the right agent from the right workspace; grant scoped GitHub access; drive the pull request through review and CI; and tear down the workspace when the work reaches a terminal state.

Sandboxes are a critical part of the workflow: they give each agent an isolated place to clone, test, build, and push code. ElasticClaw adds the workflow layer around that execution environment: triggers, workflow gates, credentials, context, and lifecycle policy that let teams run dark workflows and software workflows from their existing work queues.

The core components are:

ElasticClaw Server

The self-hosted control point: web dashboard, API, hub.yaml, workspace-managed GitHub Apps, MCP servers, issue tracker settings, and workflow state.

Workflows

Workstream definitions that decide when to start work, which workspace to use, what access to grant, and which stages drive the work through PR review, CI, merge, and cleanup.

Workspaces

Reusable bootstrap definitions for a class of work: repos, files, instructions, secrets, MCP tools, model defaults, and provider settings.

Sandboxes

Isolated execution environments from providers like Daytona, Replicated CMX, or exedev where agents clone, test, build, and push code.

Models and tools

Named LLM keys, model defaults, and MCP servers that give agents the reasoning model and external tools required for the work.

Work sources

Issue trackers and event sources such as Linear, GitHub Issues, Shortcut, webhooks, releases, and manual triggers.

Quick Start

Install the CLI:

bash
brew tap elasticclaw/elasticclaw
brew install elasticclaw

From there, set up the pieces your workflow needs:

  1. Deploy ElasticClaw Server so workflows, credentials, and agent lifecycle state have a home.
  2. Configure a sandbox provider so agents have an isolated place to clone, test, build, and push code.
  3. Configure a GitHub App so agents can receive scoped repo credentials and open pull requests.
  4. Create a workspace that defines the workspace, repos, instructions, tools, secrets, and model defaults.
  5. Connect an issue tracker such as Linear, GitHub Issues, or Shortcut if the workflow should start from ticket events.
  6. Connect a workflow to an issue tracker, webhook, release event, or manual trigger.

Help the Launch

ElasticClaw is open source and early. If it looks useful, starring the GitHub repo helps other developers find it.

If you try ElasticClaw, post honest feedback or a short demo and tag @elasticclaw. For stickers, send the link to marc@elasticclaw.ai. Useful feedback matters more than reach.

Next Steps

  • Installation — all install methods, upgrade, remote server setup
  • CLI Reference — complete command reference
  • Server Config — configure providers, workspaces, auth, secrets, MCP servers
  • Workspaces — build your own agent workspace
  • Workflows — define triggers, stages, access, and lifecycle rules
  • Concepts — architecture, workflow stages, agent lifecycle
  • MCP Servers — external tool servers for agents
  • Sandbox Providers — configure where agents run: Daytona, Replicated CMX, or exedev