Skip to main content
Book a demo

Connect Devin to Cline CLI

Give Cline CLI governed access to Devin’s 24 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add Devin to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 1

    Add Devin to Runlayer

    Devin isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Devin’s 24 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to Devin

    Sign in the way Devin requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Devin from Cline CLI

    Devin’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

24 Devin tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call.

  • Ask wiki question

    Ask any question about a GitHub repository's codebase and get an AI-powered answer grounded in its DeepWiki.

  • Automation manage

    Manage Devin automations.

  • Billing tag manage

    Manage Devin billing tags (groupings of Devin sessions for usage tracking) with a single action-based tool: list/get/create tags, assign sessions one at a time or in bulk (up to 500 per call, sent in…

  • Blueprint test

    Test a candidate blueprint YAML in an authoring VM: start → run initialize → fix → run initialize again (clean VM) → run maintenance → then persist with update_environment_config.

  • Campaign manage

    Read and publish a bot's campaign: its plan, its append-only readings and its status.

  • Code scan manage

    Manage Devin code scans (sometimes referred to as "security scans" or "Devin Security Swarm").

  • Find setting

    Find a Devin webapp setting and get a deep-link URL to it.

  • Knowledge manage

    Manage Devin knowledge notes and suggestions via a single action-based tool.

See all 24 Devin tools

Control

What Runlayer can see and stop in Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Devin call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination