Harvey integrates Spectre agent into Devin Desktop via ACP

CognitionCognition

· Updated

Harvey's engineering team has connected its internal background agent, Spectre, to Devin Desktop using the Agent Client Protocol. This allows proprietary company context to follow engineers across different AI agents within their primary development environment.

Harvey has integrated its proprietary background agent, Spectre, into Devin Desktop to maintain shared organizational context. The integration uses the Agent Client Protocol (ACP), an open standard for agent-to-editor communication. This allows Spectre to provide company-specific knowledge while engineers work with other agents in the Devin Desktop command center.
Protocol
Agent Client Protocol (ACP)
Compatible Agents
Codex CLI, Claude Agent, Gemini CLI, and others
Configuration
Local or Team registry files
Access Tiers
Pro, Max, Teams

This move highlights a shift toward multi-agent orchestration where specialized internal agents work alongside frontier models. By adopting ACP—which functions like a Language Server Protocol (standard for editor-tool communication) for agents—teams can plug in custom tools without building unique integrations. It ensures private context remains accessible regardless of which specific agent is executing a task.

Teams can now integrate custom agents or third-party tools like Codex CLI and Claude Agent into Devin Desktop. Configuration is managed via local or team registry files for organization-wide deployment. The feature is available for Pro, Max, and Teams users, with enterprise-level controls for managing third-party agent access.

View the full update on docs.devin.ai
Cognition
Cognition
@cognition
X

At @harvey, the engineering team integrated Spectre — their internal background agent — into Devin Desktop. Now Spectre's organizational context can live on every engineer's laptop and flow across their favorite agents. https://t.co/G2OqkM9Ncj

17retweets105likes
View on X

Still wondering? A few quick answers below.

The Agent Client Protocol (ACP) is an open standard that standardizes communication between code editors and AI agents. Similar to how the Language Server Protocol works for development tools, ACP allows any compatible agent to plug into Devin Desktop, enabling different AI models to share context and tools within a single interface.

To enable a custom agent, users must add the agent to their local or team registry file located in the .windsurf directory. Once configured, the agent can be toggled on within the Windsurf User Settings under the Agents tab. A restart of Devin Desktop is required for the new agent to appear.

Yes, team administrators can manage a shared ACP registry configuration through the Windsurf Settings on the web. This allows organizations to maintain a static list of approved third-party or internal agents that are automatically available to all team members, ensuring consistent tool access and security across the engineering department.

Every HeadsUpAI update is written based on its original source and reviewed before it's published. Read our editorial standards →

Cognition

See all AI news & updates from Cognition →

Share this update