@victor-software-house/pi-acp 0.3.0 → 0.5.0
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 +14 -5
- package/dist/index.mjs +276 -316
- package/dist/index.mjs.map +1 -1
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -2,7 +2,15 @@
|
|
|
2
2
|
|
|
3
3
|
ACP ([Agent Client Protocol](https://agentclientprotocol.com/get-started/introduction)) adapter for [`pi`](https://github.com/badlogic/pi-mono/tree/main/packages/coding-agent) coding agent.
|
|
4
4
|
|
|
5
|
-
`pi-acp` embeds pi directly via the `@
|
|
5
|
+
`pi-acp` embeds pi directly via the `@earendil-works/pi-coding-agent` SDK and exposes it as an ACP agent over stdio. Each ACP session owns one in-process `AgentSession`.
|
|
6
|
+
|
|
7
|
+
## Specs and decisions
|
|
8
|
+
|
|
9
|
+
- [`docs/prd/PRD-001-acp-v013-zed-alignment.md`](docs/prd/PRD-001-acp-v013-zed-alignment.md) — active release PRD (v0.5).
|
|
10
|
+
- [`docs/architecture/plan-acp-v013-zed-alignment.md`](docs/architecture/plan-acp-v013-zed-alignment.md) — phased implementation plan.
|
|
11
|
+
- [`docs/adr/`](docs/adr/) — architecture decision records (ADR-0001..ADR-0004).
|
|
12
|
+
- [`docs/architecture/acp-conformance.md`](docs/architecture/acp-conformance.md) — ACP conformance reference.
|
|
13
|
+
- [`docs/architecture/claude-acp-comparison.md`](docs/architecture/claude-acp-comparison.md) — reference comparison against `claude-agent-acp`.
|
|
6
14
|
|
|
7
15
|
## Status
|
|
8
16
|
|
|
@@ -28,7 +36,8 @@ Active development. ACP compliance is improving steadily. Development is centere
|
|
|
28
36
|
- pi manages sessions in `~/.pi/agent/sessions/...`
|
|
29
37
|
- `session/list` with title fallback from first user message
|
|
30
38
|
- `session/load` replays structured history (text, thinking, tool calls)
|
|
31
|
-
- `
|
|
39
|
+
- `closeSession`, `resumeSession` (stable in ACP v0.12.2+)
|
|
40
|
+
- `unstable_forkSession` (preview)
|
|
32
41
|
- Sessions can be resumed in both `pi` CLI and ACP clients
|
|
33
42
|
- Usage and cost tracking
|
|
34
43
|
- `usage_update` emitted after each agent turn with context size and cost
|
|
@@ -43,8 +52,8 @@ Active development. ACP compliance is improving steadily. Development is centere
|
|
|
43
52
|
|
|
44
53
|
## Prerequisites
|
|
45
54
|
|
|
46
|
-
- Node.js
|
|
47
|
-
- `pi` installed globally: `npm install -g @
|
|
55
|
+
- Node.js 24+ (hard requirement, matches pi runtime)
|
|
56
|
+
- `pi` installed globally (v0.75.3+): `npm install -g @earendil-works/pi-coding-agent`
|
|
48
57
|
- Configure `pi` for your model providers/API keys
|
|
49
58
|
|
|
50
59
|
## Install
|
|
@@ -187,7 +196,7 @@ test/
|
|
|
187
196
|
- `configOptions` is the preferred configuration mechanism. Zed uses it exclusively when present.
|
|
188
197
|
- pi-acp uses direct filesystem access rather than delegating reads/writes to the ACP client. This means pi reads on-disk file versions, not unsaved editor buffers.
|
|
189
198
|
|
|
190
|
-
See [docs/
|
|
199
|
+
See [docs/architecture/acp-conformance.md](docs/architecture/acp-conformance.md) for detailed conformance status.
|
|
191
200
|
|
|
192
201
|
## Release
|
|
193
202
|
|