Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Back to the Future: Let me tell you about the A...

Back to the Future: Let me tell you about the ACP protocol

First there was the ChatGPT website with a copy paste button, then there was Cursor, now there’s the Claude or Codex CLI. The ACP protocol promises to be the next step in this evolution. Lets have a look.

Avatar for Benedikt Terhechte

Benedikt Terhechte

September 24, 2025
Tweet

More Decks by Benedikt Terhechte

Other Decks in Programming

Transcript

  1. Show of Hands • Cursor • Claude Code • Codex

    • Gemini Code • Copilot • “I just copy paste” • Other
  2. IRON Stablecoin API to move large sums of money internationally

    • Tx can easily be 100m • High security requirements • Bugs can have catastrophic outcomes • Can’t just yolo vibe code everything
  3. • can you write a javascript function that encrypts a

    string using the web crypto api? • How do I con fi gure a NSTextField to be multiline How we worked back then
  4. Agentic Editor Wars Cursor, Windsurf, PearAI, Kilo, Zed, Continue, Codeium,

    Cline, Roo Code, Kiro, Codel, Cody, Trae, Void, Aide
  5. • Cost Structure: OpenAI API wants to make money, so

    does Cursor • Cursor & Copilot might be using quantized models • Both can’t optimize prompts & retrieval as well as the owners of the models can • => Source > Third Party Economic Incentives https://arxiv.org/abs/2411.02355 Quantization (compression) E ff ect on Model Performance
  6. The Cli Wars • Claude Code • Gemini Code •

    Codex • Crush • OpenCode • Qwen Code • Z.ai • Cursor Code
  7. Also • The Cursor model of adding small bits of

    context can bene fi cial • Being able to easily see the changes is great • The actual Cursor editing experience is still very good
  8. Agent Client Protocol ACP • The Agent Client Protocol standardizes

    communication between code editors and coding agents. • Replace the agent (e.g. Z.AI instead of Codex) but all your work fl ows, shortcuts, commands and con fi gurations stay the same • Additional abstraction between editor & agent • Build tools that abstract over agents
  9. ELI5 • Keep all the editing facilities of your editor

    • Integrate CLI agents including • AI Context support • Editor Pane access • Di ff access
  10. Zed.dev • Written in Rust • Lightweight & Fast •

    Collaborative • Tab Completion • Free • ACP
  11. Advantages • Better visualization of Agent Changes / di ff

    s • Less Vibe, more control • Full Transparency • Better interaction with codebase • Custom Slash Commands are supported
  12. Disadvantages • Not all slash commands supported (e.g. / vim

    or /terminal-setup • Hooks are *not* supported • Checkpointing is not supported • Resuming threads from history is not supported
  13. Verdict • Good solution if you need to work together

    with AI • Better than buying into a single Agent ecosystem as the SOTA changes so often • Easily mix and match between agents • Limited Editor Support