Reslop 0.3.3: Support for Seven AI Agents via the ACP ProtocolBrief · digest for October 18
Brief1 section≈ 2 min

Reslop 0.3.3: Support for Seven AI Agents via the ACP Protocol

If you follow the rise of autonomous AI coding assistants, you have probably noticed the ecosystem's biggest headache: every new agent brings its own protocol, proprietary plugins, and custom way of passing file context. In the fresh Reslop 0.3.3 release, Timur Shemsedinov showed how the open Agent Client Protocol (ACP) cuts through that chaos.

I previously looked at Reslop 0.2.0 and terminal-based patch verification, where the tool evolved into a handy environment for validating AI-generated code. In the new PR #154, the project took a big step forward and wired up seven popular environments at once: JetBrains Junie, GitHub Copilot, Pi, AWS Kiro, Cline, Windsurf (via Devin CLI), and Kilo Code.

ACP Architecture and Declarative Manifests

The most impressive part of this update is the size of the codebase. All seven integrations combined took just 234 lines in the diff! The reason is that ACP solves the same problem for AI agents that LSP (Language Server Protocol) solved for compilers and static analyzers: it decouples the editor UI from the agent's compute engine.

Communication runs over standard JSON-RPC 2.0 using plain input/output streams (stdio). As a result, registering a new agent in Reslop comes down to a compact declarative manifest with zero imperative glue code:

{
  "name": "junie",
  "displayName": "JetBrains Junie",
  "protocol": "acp",
  "transport": "stdio",
  "command": "junie-agent",
  "args": ["--mode", "acp", "--stdio"],
  "env": {
    "ACP_VERSION": "1.0",
    "JETBRAINS_AI_WORKSPACE": "${workspaceRoot}"
  },
  "capabilities": {
    "tools": true,
    "fileDiffs": true,
    "multiFileEdits": true
  }
}

Once the manifest is registered, you can launch an agent orchestration session straight from the terminal:

reslop session start \
  --agent windsurf \
  --adapter devin-cli \
  --protocol acp \
  --workspace . \
  --task "Refactor authentication middleware to use Bearer token validation"

While the industry argues over which model reasons best, standards like ACP quietly do the real engineering work—turning scattered AI utilities into predictable building blocks of a single workspace.

Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 3