docs.rs failed to build lingshu-acp-0.10.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

lingshu-acp

Why this crate? VS Code (and other IDEs) speak Agent Communication Protocol
— a JSON-RPC 2.0 stdio protocol that lets editors embed agents without shipping their own
LLM infrastructure. lingshu-acp wraps the full Lingshu agent as an ACP server, so
you get Lingshu's 30+ tools, persistent memory, and multi-provider LLM support directly
inside your editor sidebar — no browser, no separate terminal.

Part of Lingshu — the Rust SuperAgent.

Start the ACP server

lingshu acp

The process communicates over stdin/stdout using JSON-RPC 2.0. Your IDE connects to
the process directly — nothing to configure beyond pointing the IDE at the binary.

VS Code quick setup

Install the Lingshu VS Code extension (or add a manual ACP entry):

// .vscode/settings.json
{
  "acp.agents": [
    {
      "id": "lingshu",
      "name": "Lingshu",
      "command": "lingshu",
      "args": ["acp"]
    }
  ]
}

Open the Agent panel → select Lingshu → start chatting.

Protocol flow

IDE            lingshu-acp              lingshu-core
 │─ agent/run ──────────────────────────────▶│
 │              │─ Agent::run_conversation() ─▶│
 │              │◀── tool calls ──────────────│
 │◀ agent/run/token (streaming tokens) ───────│
 │◀ agent/run (final response) ───────────────│

Supported ACP methods

Method	Description
`agent/run`	Start a conversation turn (streaming via `agent/run/token` notifications)
`agent/list`	Return agent metadata (name, description, capabilities)

Embed in your own binary

[dependencies]
lingshu-acp = { path = "../lingshu-acp" }

use lingshu_acp::AcpServer;
use lingshu_core::Agent;

let agent = Agent::default_builder()?.build()?;
AcpServer::new(agent).run_stdio().await?;