support-acp

Document ACP integration with RARA over stdio using JSON-RPC framing.

15|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/linkerdog/rara --skill support-acp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: support-acp
Source: https://github.com/linkerdog/rara/tree/main/.agents/skills/support-acp
Command: npx skills add https://github.com/linkerdog/rara --skill support-acp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the guesswork of building external clients that connect to RARA using the Agent Client Protocol (ACP) by stdio, ensuring your IDE plugin or agent can reliably create sessions, submit prompts, and handle runtime events.

Core Features & Use Cases

  • ACP stdio transport integration: Connect external processes to RARA using JSON-RPC framed over stdin/stdout and implement the expected client lifecycle.
  • Session and prompt workflow: Create, resume, and control sessions while submitting prompts that flow through RARA’s event bus.
  • Event translation and control-plane extensibility: Correctly interpret how RARA translates internal AgentEvent variants into ACP SessionNotification messages, including tool progress, approvals, and error/warning surfaces.

Quick Start

Ask an AI assistant to generate a minimal ACP client that spawns rara acp, sends a session/create request with a working directory, then submits a session/prompt message and prints every incoming ACP notification.

Frequently Asked Questions about support-acp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate an ACP client with a control plane using stdio?

You integrate an ACP client with a control plane by spawning the agent process, sending JSON-RPC framed messages over stdin and stdout, and implementing the required session lifecycle methods like session/create and session/prompt.

What is the ACP session lifecycle and how do I manage session states?

The ACP session lifecycle involves creating, resuming, and controlling sessions via JSON-RPC. You manage session states by calling specific methods like session/create, session/resume, and session/prompt to submit prompts and handle runtime events.

How does RARA translate internal agent events into ACP notifications?

RARA translates internal AgentEvent variants into ACP SessionNotification messages over the control plane. This translation includes mapping tool progress, approval requests, and error or warning surfaces into structured ACP notifications for external clients.

Can I use ACP to build an IDE plugin that submits prompts and consumes tool events?

Yes, ACP is designed for building IDE plugins and protocol adapters. You can use it to spawn the agent, establish a stdio transport, submit prompts, and consume structured session, tool, and approval events through the JSON-RPC interface.

What JSON-RPC methods are required for an ACP stdio transport integration?

Required JSON-RPC methods for ACP stdio transport integration include session/create to initialize a working directory, session/resume to continue existing sessions, and session/prompt to submit messages and trigger agent responses.

Why are my ACP session notifications missing tool progress and approval events?

Missing tool progress and approval events in ACP session notifications usually indicate incorrect event translation or provenance handling. You must ensure your client correctly interprets RARA's AgentEvent variants and maps them to the expected SessionNotification messages.