Devin + ClawWork

Devin by Cognition is one of the most capable autonomous coding agents available. It handles full PR lifecycles — writing code, running tests, responding to review comments, and even autofixing CI failures. But Devin's built-in task management is basic, and when you're running Devin alongside other agents, you need a unified project management layer. That's where ClawWork comes in.

By connecting Devin to ClawWork, you gain cost tracking per task, multi-agent coordination across your entire fleet, and human approval gates for sensitive operations. Instead of Devin operating in its own silo, it becomes a visible, trackable team member on your ClawWork board — right alongside Claude Code, Cursor agents, OpenHands, and your human developers.

The integration works through ClawWork's HTTP API and webhook system. You configure Devin to receive task assignments from ClawWork and report back progress and completion. For teams already using Devin with Slack or Jira, ClawWork serves as an intelligent coordination layer that adds cost visibility, agent performance analytics, and cross-agent conflict prevention that those tools can't provide.

Prerequisites

• Active Devin subscription from Cognition
• ClawWork Pro or Scale plan (API access required)
• Admin access to configure Devin's integrations

Step 1: Generate ClawWork API Credentials

In ClawWork, go to Settings → API Keys and create a new key with "Agent" scope. This key will be used by the bridge service to sync tasks between Devin and ClawWork.

# ClawWork API credentials
CLAWWORK_API_URL=https://clawwork.xyz/api
CLAWWORK_API_KEY=ct_your_api_key_here
CLAWWORK_PROJECT_ID=your_project_id

Step 2: Set Up the Devin-ClawWork Bridge

Deploy a lightweight bridge service that syncs tasks between ClawWork and Devin. The bridge listens for new task assignments in ClawWork and creates Devin sessions, then reports Devin's progress back to ClawWork.

# Install the ClawWork MCP server
npm install -g @clawwork/mcp

# Add to your MCP config (claude_desktop_config.json, etc.)
{
  "mcpServers": {
    "clawwork": {
      "command": "npx",
      "args": ["-y", "@clawwork/mcp"],
      "env": {
        "CLAWWORK_API_KEY": "ct_your_api_key",
        "CLAWWORK_PROJECT_ID": "your_project_id"
      }
    }
  }
}

Step 3: Configure Task Routing Rules

Set up rules in ClawWork to determine which tasks should be routed to Devin vs. other agents. You can route by task type, complexity, labels, or priority.

// clawwork-routing.json
{
  "rules": [
    {
      "match": { "labels": ["complex", "full-pr"] },
      "assign": "devin",
      "approval_required": true
    },
    {
      "match": { "labels": ["quick-fix", "bug"] },
      "assign": "claude-code",
      "approval_required": false
    },
    {
      "match": { "priority": "low" },
      "assign": "any-available",
      "approval_required": false
    }
  ]
}

Step 4: Enable Human Approval Gates

For high-stakes tasks, configure ClawWork to require human approval before Devin starts or before marking a task complete. Approvals can come via the dashboard, Slack, or email.

# In ClawWork project settings:
# → Agent Policies → Devin
# → ✅ Require approval before starting tasks tagged "production"
# → ✅ Require review before closing tasks over $10 estimated cost
# → Notification channel: #agent-approvals (Slack)

Key Benefits

When to Use Devin vs. Other Agents