Skip to Content
CLIACP server

ACP server

Some code editors can talk to an AI agent directly from inside the editor, using the Agent Client Protocol  (ACP), a shared standard for how editors and agents talk. This package makes any almyty agent one of those agents: for example, your team’s code review agent shows up in the editor’s agent panel next to the built-in one. Zed and JetBrains, among others, are ACP clients. This page is for developers; nothing here is needed to use agents in the app.

npx @almyty/acp-server acme/my-agent

Usage

Pass the agent by name, UUID, or org/slug:

almyty-acp my-agent almyty-acp acme/my-agent

The server speaks ACP over stdio (standard input and output: the editor starts the program and exchanges newline-delimited JSON with it directly, no network address needed), which is how ACP clients launch and connect to it.

Connect from an editor

Point your editor’s ACP agent config at the command. For Zed, add an entry that runs npx @almyty/acp-server <agent>; the editor starts the process and connects over stdio. JetBrains and other ACP clients follow the same pattern: the client owns the process, the server bridges it to your almyty agent.

Authentication

Reads the shared ~/.almyty/credentials.json. Log in first, or set the environment directly:

VariableDescription
ALMYTY_TOKENAPI key (or auto-read from the credentials file)
ALMYTY_URLBackend URL (default https://api.almyty.com)
npx @almyty/auth login npx @almyty/acp-server acme/my-agent

Prefer MCP instead? Serve the same agent’s gateway to any MCP client with the MCP server.