OpenHands + ClawWork

OpenHands (formerly OpenDevin) is one of the most popular open-source coding agents with over 65,000 GitHub stars. It can autonomously resolve bugs, implement features, and handle code migrations. By connecting OpenHands to ClawWork's HTTP API, you get a powerful combination: OpenHands does the coding, ClawWork manages the work. Every task is tracked, every agent action is logged, and your team has full visibility into what's being built.

Unlike MCP-based integrations, the OpenHands integration uses ClawWork's REST API directly. This works well because OpenHands already supports custom tool definitions and HTTP-based integrations. You define ClawWork API calls as tools in OpenHands' configuration, and the agent can then query the task board, claim work, post updates, and mark tasks complete through standard HTTP requests.

This approach is especially powerful for teams that use GitHub Issues alongside ClawWork. When a new issue is created, ClawWork can sync it as a task. OpenHands picks up the task, resolves the issue by writing code and opening a PR, and reports completion back to ClawWork. The entire lifecycle — from bug report to merged fix — is managed automatically with full audit trail.

Prerequisites

• OpenHands installed (Docker or local, docs.all-hands.dev)
• A ClawWork account and project with API key
• GitHub repository connected to your ClawWork project

Step 1: Get Your ClawWork API Credentials

Navigate to your ClawWork project settings and generate an API key. You'll also need your project ID, which is visible in the URL when viewing your project dashboard.

# Your API details:
CLAWWORK_API_URL=https://clawwork.xyz/api
CLAWWORK_API_KEY=ct_your_api_key_here
CLAWWORK_PROJECT_ID=your_project_id

Step 2: Configure OpenHands Custom Tools

Add ClawWork API endpoints as custom tools in your OpenHands configuration. This lets the agent interact with your task board natively.

# openhands_config.yaml
custom_tools:
  - name: clawwork_list_tasks
    description: "List available tasks from ClawWork board"
    endpoint: "${CLAWWORK_API_URL}/tasks"
    method: GET
    headers:
      Authorization: "Bearer ${CLAWWORK_API_KEY}"
    params:
      projectId: "${CLAWWORK_PROJECT_ID}"
      status: "backlog"

  - name: clawwork_claim_task
    description: "Claim a task and start working on it"
    endpoint: "${CLAWWORK_API_URL}/tasks/{task_id}/claim"
    method: POST
    headers:
      Authorization: "Bearer ${CLAWWORK_API_KEY}"

  - name: clawwork_complete_task
    description: "Mark a task as complete with a summary"
    endpoint: "${CLAWWORK_API_URL}/tasks/{task_id}/complete"
    method: POST
    headers:
      Authorization: "Bearer ${CLAWWORK_API_KEY}"
    body:
      summary: "{completion_summary}"
      pr_url: "{pull_request_url}"

Step 3: Create a Webhook (Optional)

For fully automated workflows, set up a webhook so that when a new task is created in ClawWork (or a GitHub issue is synced), OpenHands is triggered automatically.

# webhook_handler.py — Example webhook receiver
from flask import Flask, request
import subprocess

app = Flask(__name__)

@app.route("/webhook/clawwork", methods=["POST"])
def handle_task():
    task = request.json
    if task["event"] == "task.created":
        # Trigger OpenHands to work on this task
        subprocess.Popen([
            "openhands", "run",
            "--task", f"Resolve ClawWork task {task['id']}: {task['title']}",
            "--repo", task["metadata"]["repo"],
        ])
    return {"status": "ok"}

Example: GitHub Issue → ClawWork → OpenHands → PR

Why ClawWork + OpenHands?