← ClaudeAtlas

provider-driver-devlisted

Implement, test, and maintain external AI coding agent provider drivers in crates/padu-core/src/driver/, handling ACP (Agent Client Protocol) integration, subprocess lifecycles, streaming event demuxing, reasoning token normalization, and automated CLI verification.
wisnuwiry/padu · ★ 21 · Code & Development · score 71
Install: claude install-skill wisnuwiry/padu
# Provider Driver Development Skill This skill guides the implementation, event normalization, and validation of AI coding agent provider drivers in `crates/padu-core/src/driver/` across both **Agent Client Protocol (ACP)** and **Native Subprocess** architectures. --- ## 1. When to Use This Skill - Connecting a new coding agent CLI (e.g. from [paseo.sh/agents](https://paseo.sh/agents) such as GitHub Copilot, Cline, Goose, Gemini CLI, Qwen Code, etc.). - Implementing or updating a native driver (Claude Code, OpenAI Codex, OpenCode, Pi, Amp, DeepSeek). - Debugging subprocess lifecycles, signal handling, streaming token demuxing, or tool call event ordering. - Testing binary detection, live connection, model discovery, model switching, forking, and rollback using `bun run provider:test`. --- ## 2. Decision Tree: ACP vs Native Driver Before writing code, identify whether the agent CLI supports the **Agent Client Protocol (ACP)**: ```mermaid graph TD Agent["New Coding Agent CLI"] --> SpeaksACP{"Does it support ACP<br/>(stdio / JSON-RPC)?"} SpeaksACP -->|Yes (e.g. Cline, Goose, Gemini, Qwen, Cursor)| PathA["Path A: ACP Integration<br/>(Zero custom driver code needed)"] SpeaksACP -->|No (e.g. Claude, Codex, OpenCode, Pi, Amp)| PathB["Path B: Native Custom Driver<br/>(Implement DriverControl trait)"] ``` - **Path A (ACP Driver)**: Use Padu's unified `AcpDriver` (`crates/padu-core/src/driver/acp.rs`). The official `agent-client-protocol` SDK handles process s