Skip to main content
Xcode 26.6’s coding intelligence can run Devin as an agent inside the coding assistant using the Agent Client Protocol (ACP). Devin isn’t one of the agents listed in Xcode’s Intelligence settings, so you add it manually as a custom ACP agent that runs from your local Devin CLI installation.
This integration uses Xcode’s built-in ACP support in the coding assistant. For the upstream reference, see Apple’s docs on setting up coding intelligence.

​
Prerequisites

  • Xcode 26.6 or later with the coding assistant available.
  • Devin CLI installed and authenticated. If you haven’t installed it yet, follow the Quickstart, then run devin auth login.
  • The absolute path to the devin binary. You can find it with:
    This typically resolves to something like /Users/you/.local/bin/devin.
Xcode requires an absolute path for the agent command — it does not expand ~ or use your shell’s PATH. If which devin prints a ~-prefixed path, expand it first (for example, run echo "$(cd ~ && pwd)/.local/bin/devin") and use the full /Users/... result.

​
Setup

Add Devin as a custom agent from the Intelligence settings.
1

Open Intelligence settings

Choose Xcode > Settings, then select Intelligence in the sidebar.
2

Add an agent

Under Agents, click Add an Agent. Xcode’s built-in ACP support lets you register any agent that speaks the Agent Client Protocol.
3

Configure the Devin agent

In the sheet that appears, enter the agent’s details:
  • Name — Devin (or any label you prefer).
  • Command — the absolute path to your devin binary (from which devin), for example /Users/you/.local/bin/devin. A relative path or a ~-prefixed path won’t work.
  • Arguments — acp (the only argument Devin needs).
Click Add. Devin now appears as a selectable agent under Agents.
4

Start chatting with Devin

Select Devin in the coding assistant and send a message to start a session. The first time you connect, you may be prompted to authenticate; Devin uses the credentials from devin auth login (or WINDSURF_API_KEY if set).

​
Give Devin CLI access to your Xcode project (MCP)

Separately from running Devin inside Xcode, you can point the standalone Devin CLI at your Xcode project so it can build, run tests, read and edit files, render SwiftUI previews, and search Apple’s documentation. Xcode ships an MCP server, xcrun mcpbridge, that exposes these Xcode tools to any external agent (the same mechanism Cursor uses). Add it to Devin like any other MCP server.
The Xcode MCP bridge requires Xcode 26.3 or later. Confirm the binary is available with xcrun --find mcpbridge (see Troubleshooting if it isn’t). See Apple’s docs on giving external agents access to Xcode.
1

Allow external agents in Xcode

Choose Xcode > Settings, select Intelligence, and under Model Context Protocol turn on Allow external agents to use Xcode tools.
2

Add the Xcode MCP server to Devin

Register xcrun mcpbridge as a stdio MCP server:
Verify it was added with devin mcp list. See devin mcp for scope and configuration options.
3

Open your project and prompt Devin

Open your project or workspace in Xcode (the bridge needs a running Xcode session with a project open), then prompt Devin from the CLI. Xcode alerts you when the external agent connects and while it’s active.

​
Troubleshooting

  • xcrun: error: unable to find utility "mcpbridge" — your system is pointed at the Command Line Tools instead of the full Xcode install. Fix it with:
    Then confirm with xcrun --find mcpbridge, which should print a path.
  • Devin can’t reach the Xcode tools — make sure Xcode is running with a project (not an empty window) open, and that Allow external agents to use Xcode tools is enabled in Intelligence settings.

​
Notes and limitations

  • The model can’t be selected from Xcode — Devin always runs with your team’s default model.
  • When you select an agent in Xcode’s coding assistant, it automatically gets access to Xcode capabilities such as building and testing your app. You can review and restrict which commands and tools agents may use under Agents > Permissions in Intelligence settings — see Apple’s docs on extending and customizing agents.
  • Devin CLI’s terminal/shell output is surfaced through Xcode’s ACP rendering, which differs from the native Devin CLI terminal UI. Some richer interactions are only available in the standalone CLI.
  • The devin acp subcommand is intended to be launched by an ACP-aware client (like Xcode’s coding assistant) as a subprocess — it speaks JSON-RPC over stdio and is not meant to be run interactively. See devin acp in the command reference.