What this artifact is for
The quick orientation layer before you go deeper upstream.
Summary
ACP adapter for pi agent
Seed description: ACP adapter for pi agent
Category: Providers & Integrations
Best for: Not yet synthesized.
How to read this page
Workflow tags: none captured
Integrations: none captured
Caveats: No caveats captured yet
Maturity: No maturity signals captured
README excerpt
More of the actual upstream surface so you can skim here before deciding to open the repo.
ACP (Agent Client Protocol) adapter for pi coding agent (fka shitty coding agent).
pi-acp communicates ACP JSON-RPC 2.0 over stdio to an ACP client (e.g. Zed editor) and spawns pi --mode rpc, bridging requests/events between the two.
This is an MVP-style adapter intended to be useful today and easy to iterate on. Some ACP features may be not implemented or are not supported (see Limitations). Development is centered around [Zed](https…
Preview source: captured upstream text ↗
Quick topics
Skim bullets
- Streams assistant output as ACP agentmessagechunk
- Maps pi tool execution to ACP toolcall / toolcall_update
- Tool call locations are surfaced when available for ACP clients that support opening the referenced file/context
- Relative file paths from pi are resolved against the session cwd before being emitted as ACP tool locations, which enables follow-along features in clients like Zed
- For edit, pi-acp attempts to infer a 1-based line number from a unique oldText match in the pre-edit file snapshot and includes it in the emitted tool location when possible
- For edit, pi-acp snapshots the file before the tool runs and emits an ACP structured diff (oldText/newText) on completion when possible
- Session persistence
- pi stores its own sessions in ~/.pi/agent/sessions/...
Sources and provenance
Everything on this page should be traceable back to the list seed or an upstream surface.
Discovery reason: Listed in the awesome-pi-agent README
Discovered from: seed artifact
Claim confidence: medium
Surface capture kind: repo-readme