sbx/claude-acp:latest

schemaVersion: "3"
displayName: Claude Code ACP adapter
author: Docker, Inc. https://docker.com
description: The Agent Client Protocol adapter for Claude Code as a mixin — the claude-agent-acp stdio server with its Node runtime in an overlay, bound to the composed claude binary. Layer it onto a base that composes the claude-mixin kit and point an ACP client (such as Zed) at `claude-agent-acp`.
sourceUrl: https://github.com/docker-hardened-images/definitions
version: 0.100.0
licenses:
    - Apache-2.0
kind: mixin
provides:
    - [email protected]
requires:
    - claude
capabilities:
    - type: com.docker.sandbox/acp@1
      optional: true
      config:
        agent: claude
        command:
            - claude-agent-acp
      description: Drive claude sessions over the Agent Client Protocol
    - type: com.docker.sandbox/agent-context@1
      optional: true
      config:
        content: |
            ## Claude Code ACP adapter

            `claude-agent-acp` is installed at `/usr/local/bin/claude-agent-acp`. It
            is an Agent Client Protocol (ACP) server on stdio: a client spawns it and
            drives a Claude Code session through the protocol. It is not an
            interactive command — with no client on the other end of stdio it sits
            silent, so do not run it from this shell to "check" it.

            Host tools must attach it to a non-TTY stdin/stdout stream, for example
            `sbx exec -i <sandbox> claude-agent-acp`. In Zed, configure an agent
            server whose command runs that.

            The adapter drives the same `claude` binary this sandbox already has
            (the one `command -v claude` finds, unless `CLAUDE_CODE_EXECUTABLE`
            names another), so authentication is
            the surface `claude` uses: the proxy-mediated Anthropic credential in
            `~/.claude/.credentials.json` and `~/.claude/settings.json`. If `claude`
            works here, the adapter works with no extra setup and nothing separate to
            log in to. Sessions created through ACP share the session-state volumes
            with interactive `claude` runs.
    - type: com.docker.sandbox/agent-context@2
      optional: true
      config:
        content: |
            ## Claude Code ACP adapter

            `claude-agent-acp` is installed at `/usr/local/bin/claude-agent-acp`. It
            is an Agent Client Protocol (ACP) server on stdio: a client spawns it and
            drives a Claude Code session through the protocol. It is not an
            interactive command — with no client on the other end of stdio it sits
            silent, so do not run it from this shell to "check" it.

            Host tools must attach it to a non-TTY stdin/stdout stream, for example
            `sbx exec -i <sandbox> claude-agent-acp`. In Zed, configure an agent
            server whose command runs that.

            The adapter drives the same `claude` binary this sandbox already has
            (the one `command -v claude` finds, unless `CLAUDE_CODE_EXECUTABLE`
            names another), so authentication is
            the surface `claude` uses: the proxy-mediated Anthropic credential in
            `~/.claude/.credentials.json` and `~/.claude/settings.json`. If `claude`
            works here, the adapter works with no extra setup and nothing separate to
            log in to. Sessions created through ACP share the session-state volumes
            with interactive `claude` runs.
args:
    version:
        required: true
        description: claude-agent-acp release the overlay carries
        pattern: ^[0-9]+\.[0-9]+\.[0-9]+$
        buildArg: VERSION