pi-acp 0.0.26 → 0.0.28
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/dist/index.js +326 -202
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# pi-acp
|
|
2
2
|
|
|
3
|
-
ACP ([Agent Client Protocol](https://agentclientprotocol.com/overview/introduction)) adapter for [`pi`](https://github.com/
|
|
3
|
+
ACP ([Agent Client Protocol](https://agentclientprotocol.com/overview/introduction)) adapter for [`pi`](https://github.com/earendil-works/pi) coding agent (fka shitty coding agent).
|
|
4
4
|
|
|
5
5
|
`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.
|
|
6
6
|
|
|
@@ -34,7 +34,7 @@ Expect some minor breaking changes.
|
|
|
34
34
|
Make sure pi is installed
|
|
35
35
|
|
|
36
36
|
```bash
|
|
37
|
-
npm install -g @
|
|
37
|
+
npm install -g @earendil-works/pi-coding-agent
|
|
38
38
|
```
|
|
39
39
|
|
|
40
40
|
- Node.js 22+
|
|
@@ -195,7 +195,7 @@ Project layout:
|
|
|
195
195
|
## Limitations
|
|
196
196
|
|
|
197
197
|
- No ACP filesystem delegation (`fs/*`) and no ACP terminal delegation (`terminal/*`). pi reads/writes and executes locally.
|
|
198
|
-
- MCP servers are accepted in ACP params and stored in session state, but not wired through to pi
|
|
198
|
+
- MCP servers are accepted in ACP params and stored in session state, but not wired through to pi in this adapter. If you use [pi MCP adapter](https://github.com/nicobailon/pi-mcp-adapter) it will be available in the ACP client.
|
|
199
199
|
- Assistant streaming is currently sent as `agent_message_chunk` (no separate thought stream).
|
|
200
200
|
- Queue is implemented client-side and should work like pi's `one-at-a-time`
|
|
201
201
|
- ~~ACP clients don't yet suport session history, but ACP sessions from `pi-acp` can be `/resume`d in pi directly~~
|