@agentproto/adapter-pi 0.2.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/MCP-BRIDGE.md

@@ -0,0 +1,132 @@
+# MCP → pi-tools bridge
+
+Pi ships **no MCP client**. This adapter still lets the host inject
+`mcpServers` into a pi session — including the daemon's `agent_start`
+orchestration gateway — by bridging every MCP tool into a native **pi tool**
+through pi's own TypeScript **extension** system. Pi never speaks MCP; the
+bridge extension does, on pi's behalf.
+
+## How it works
+
+```
+host connect({ mcpServers })
+        │
+        ▼
+adapter (client.ts)                         ┌─ pi child process ────────────┐
+  1. enumerate each server: tools/list      │  pi --mode rpc                 │
+  2. write config JSON  ───────────────────▶│    -e mcp-bridge-extension.mjs │
+     (PI_MCP_BRIDGE_CONFIG)                  │    PI_MCP_BRIDGE_CONFIG=…      │
+  3. spawn pi with -e + env                  │                               │
+                                             │  extension registers one pi   │
+                                             │  tool per MCP tool; execute →  │
+                                             │  @modelcontextprotocol/sdk →   │
+                                             │  callTool() on the MCP server  │
+                                             └───────────────────────────────┘
+```
+
+1. **Enumerate (adapter, `src/mcp-bridge/enumerate.ts`).** On `connect()`, for
+   each injected `AcpMcpServer` the adapter opens a short-lived MCP client,
+   `tools/list`, and closes it. Enumerating host-side surfaces connect/list
+   errors early and keeps the extension's registration synchronous.
+2. **Config JSON (`config.ts` / `parse-config.ts`).** The enumerated tools +
+   server specs are written to a per-session temp file
+   (`{ servers:[…], tools:[{ toolName, server, remoteName, description,
+   inputSchema }] }`). Path is passed via `PI_MCP_BRIDGE_CONFIG`.
+3. **Spawn.** The adapter adds `-e <dist>/mcp-bridge-extension.mjs` to the
+   `pi --mode rpc` argv (additive — pi's own extension discovery is untouched)
+   and sets `PI_MCP_BRIDGE_CONFIG` in the child env. The extension path is
+   resolved from the adapter's own module URL (`import.meta.url`), not cwd.
+4. **Register (extension, `src/mcp-bridge/extension.ts`).** At load, pi calls
+   the extension's default export; it reads the config and calls
+   `pi.registerTool(...)` once per tool — **synchronously**. Each tool's
+   `execute` lazily connects (memoized per server) and proxies via
+   `@modelcontextprotocol/sdk` `callTool`, mapping the result back to pi's
+   tool-result shape.
+
+## Tool namespacing
+
+Bridged tools are named `mcp__<server>__<tool>`, sanitized to `[a-zA-Z0-9_-]`
+and capped at 64 chars (provider tool-name limits). Collisions after
+sanitizing/truncation get a `_2`, `_3`, … suffix. Namespacing avoids clashing
+with pi's built-in tools (`read`, `bash`, …).
+
+## Result mapping (`map-result.ts`)
+
+MCP `callTool` returns `{ content: ContentBlock[], isError? }`. The bridge maps
+**text blocks directly**; every **non-text block** (image / audio / resource /
+resource_link) is **stringified** into a labeled text block
+(`[non-text MCP content] …`). An `isError: true` result is surfaced as text the
+model can read and recover from (MCP's tool-error convention), prefixed
+`MCP tool error (<server>/<tool>): …`, with `details.isError` set for logs. A
+thrown/rejected SDK call is caught and returned as an error tool result (pi
+never sees an uncaught throw).
+
+## The two make-or-break details (verified against pi 0.80.3, in source AND live)
+
+- **Synchronous registration at extension load works.** pi's loader awaits the
+  extension factory (`core/extensions/loader.ts` — `await factory(api)`) and
+  `registerTool()` is valid during load (loader comment: "registerTool() is
+  valid during extension load"). The bridge registers synchronously in the
+  factory (like pi's own `hello.ts` example), so it does not depend on any
+  async-load timing. Proven live: pi called `mcp__echo__echo` in a `--mode rpc`
+  session.
+- **Import resolution "just works" — because the extension imports NO pi
+  package.** pi loads extensions with **jiti**; in a Node install (the global
+  `pi` bin is a `#!/usr/bin/env node` script, not the Bun binary) jiti aliases
+  `@earendil-works/*` + `typebox` to pi's own install
+  (`loader.ts` `getAliases()`), so an extension living outside pi's tree still
+  resolves them. The bridge sidesteps the question entirely: it uses pi's
+  **structural** runtime contract (a `registerTool` method; a plain JSON Schema
+  as `parameters`) and imports nothing from `@earendil-works/*`
+  (`grep -c "@earendil-works" dist/mcp-bridge-extension.mjs` → `0`). The MCP SDK
+  is **inlined** into the extension bundle (pi's process can't resolve it
+  otherwise); only node builtins stay external.
+
+### Why a raw JSON Schema is a valid pi `parameters`
+
+pi expects a TypeBox `TSchema`, but validates tool arguments with
+`Compile(tool.parameters)` (`pi-ai/utils/validation.ts`). A raw MCP JSON Schema
+compiles + validates unchanged (verified: `Compile({type:"object",…}).Check`
+respects `required`/types), and pi additionally runs JSON-Schema-aware coercion
+when the schema carries no TypeBox `Kind` symbol. So the bridge passes the MCP
+`inputSchema` through verbatim — no `Type.Unsafe`, no `@earendil-works/pi-ai`
+import, no cast.
+
+### ESM/CJS interop
+
+The inlined MCP SDK pulls in CJS deps (e.g. `cross-spawn`) that `require()` node
+builtins. The bundle banner injects a real `require`
+(`createRequire(import.meta.url)`) so esbuild's `__require` helper uses it
+instead of throwing "Dynamic require … is not supported".
+
+## Limitations / known gaps
+
+- **Image & binary content** returned by an MCP tool is stringified to text, not
+  passed to pi as an image block (pi supports image tool results, but mapping
+  binary payloads through faithfully is deferred). Text tools (the common case)
+  are lossless.
+- **No MCP sampling / elicitation / roots.** The bridge is one-directional
+  (pi → MCP tool call → result). MCP servers that request LLM sampling back from
+  the client are not supported.
+- **Cancellation** — pi passes an `AbortSignal` into `execute`; the bridge
+  forwards it to the SDK `callTool({ signal })`. Whether the remote server
+  honors it depends on the server.
+- **Brokered credentials.** Only static `headers` on an `AcpMcpServer` are
+  honored for http/sse servers. A `credentialRef` must be resolved into headers
+  by the host **before** injection (the bridge does not call the credential
+  broker).
+- **Double connect for stdio.** The adapter probes each stdio server once to
+  enumerate, then the extension re-spawns it for live calls (two spawns total).
+
+## Live e2e
+
+`e2e/echo-mcp-server.mjs` is a ~30-line stdio MCP server exposing one `echo`
+tool; `e2e/run-e2e.mjs` injects it via `piRuntime().start({ mcpServers })`,
+prompts pi to call it, and asserts the stream shows a `tool-call` for
+`mcp__echo__echo`, a `tool-result` carrying the echoed text, and a completed
+`turn-end`. Run (needs `ANTHROPIC_API_KEY` + a global `pi`), after a build:
+
+```bash
+pnpm --filter @agentproto/adapter-pi build
+node adapters/pi/e2e/run-e2e.mjs
+```

package/PI-RPC.md

@@ -0,0 +1,158 @@
+# Pi RPC wire profile
+
+Reverse-engineered from pi source at **0.80.3**
+(`github.com/earendil-works/pi`, package `@earendil-works/pi-coding-agent`):
+
+- `packages/coding-agent/src/modes/rpc/rpc-types.ts` — command + response unions
+- `packages/coding-agent/src/modes/rpc/rpc-mode.ts` — the event loop (the
+  decisive file: `session.subscribe((event) => output(event))`)
+- `packages/coding-agent/src/modes/rpc/jsonl.ts` — framing
+- `packages/coding-agent/src/core/agent-session.ts` — `AgentSessionEvent`
+- `packages/agent/src/types.ts` — base `AgentEvent`, `AssistantMessageEvent`
+- `packages/ai/src/types.ts` — `StopReason`, `Usage`, `ToolCall`, message shapes
+
+## Transport & framing
+
+`pi --mode rpc` is a persistent duplex:
+
+- **stdin** — one command per line: `JSON.stringify(command) + "\n"`.
+- **stdout** — one record per line, **LF-only framing** (`\n`). Payloads may
+  contain U+2028/U+2029, so records MUST be split on `\n` only (pi deliberately
+  avoids Node `readline`). The client mirrors this with a `StringDecoder` +
+  manual `\n` scan.
+
+The process stays alive until stdin ends (pi then shuts down) or it receives
+`SIGTERM`/`SIGHUP`. `close()` calls `stdin.end()` then `SIGTERM`.
+
+## stdout carries three kinds of record
+
+1. **Responses** — `{ type: "response", command, success, id?, data?, error? }`.
+   `id` echoes the command's `id` for correlation. `success:false` carries
+   `error: string`.
+2. **Session events** — pi's `AgentSessionEvent` union, emitted verbatim by
+   `session.subscribe`. These are the stream this adapter maps.
+3. **Extension-UI requests** — `{ type: "extension_ui_request", ... }` (and
+   `extension_error`). This adapter ignores them (classified as `other`); pi's
+   RPC mode does not require a response for the fire-and-forget ones.
+
+Note: `--mode rpc` does **not** emit the `{ type: "session", version, id, ... }`
+header that `--mode json` emits. The client obtains the session id via a
+`get_state` command instead.
+
+## Commands this adapter sends
+
+| Command | Shape | When |
+| ------- | ----- | ---- |
+| `get_state` | `{ id, type: "get_state" }` | right after spawn — readiness probe + captures `data.sessionId` |
+| `set_thinking_level` | `{ id, type: "set_thinking_level", level }` | after connect, when an `effort` is set (`level ∈ off\|minimal\|low\|medium\|high\|xhigh`) |
+| `prompt` | `{ id, type: "prompt", message }` | each turn (fire-and-forget; events follow) |
+| `abort` | `{ id, type: "abort" }` | `cancel()` |
+
+Model + resume are passed as **spawn argv**, not RPC commands:
+`pi --mode rpc [--model <provider/id>] [--session <resumeSessionId>]`
+(flags verified in `packages/coding-agent/src/cli/args.ts`;
+`--model` accepts `provider/id` and an optional `:<thinking>` suffix).
+
+### `prompt` is fire-and-forget
+
+Pi acks `prompt` as soon as preflight succeeds
+(`{ command:"prompt", success:true }`) — the real work streams as events. A
+`{ command:"prompt", success:false, error }` means **no events will follow**, so
+the client synthesizes an `error` + `turn-end{error}` on the active turn so
+`events()` terminates instead of hanging.
+
+## Session events (`AgentSessionEvent`) and their fields
+
+Base `AgentEvent` (`packages/agent/src/types.ts`):
+
+```
+{ type: "agent_start" }
+{ type: "agent_end"; messages; willRetry }        // session-extended
+{ type: "turn_start" }
+{ type: "turn_end"; message: AgentMessage; toolResults }
+{ type: "message_start"; message }
+{ type: "message_update"; message; assistantMessageEvent }   // streaming
+{ type: "message_end"; message }
+{ type: "tool_execution_start"; toolCallId; toolName; args }
+{ type: "tool_execution_update"; toolCallId; toolName; args; partialResult }
+{ type: "tool_execution_end"; toolCallId; toolName; result; isError }
+```
+
+Session-only additions: `agent_settled`, `queue_update`, `compaction_*`,
+`auto_retry_*`, `entry_appended`, `session_info_changed`,
+`thinking_level_changed`.
+
+`AssistantMessageEvent` (carried on `message_update.assistantMessageEvent`):
+
+```
+{ type: "text_delta"; delta; contentIndex; partial }
+{ type: "thinking_delta"; delta; contentIndex; partial }
+{ type: "done"; reason: "stop"|"length"|"toolUse"; message }
+{ type: "error"; reason: "error"|"aborted"; error }
+  ... plus start/text_start/text_end/thinking_start/thinking_end/toolcall_* (ignored)
+```
+
+`StopReason = "stop" | "length" | "toolUse" | "error" | "aborted"`.
+`Usage = { input, output, totalTokens, cost: { total, ... }, ... }` (on the
+assistant message).
+
+## Event → StreamEvent mapping table
+
+| pi event | condition | StreamEvent |
+| -------- | --------- | ----------- |
+| `message_update` / `text_delta` | — | `text-delta { text: delta }` |
+| `message_update` / `thinking_delta` | — | `thought { text: delta }` |
+| `message_update` / `done` | — | *(no event)* — records `stopReason` for turn-end |
+| `message_update` / `error` | `reason === "error"` | `error { message: errorMessage }` + records `stopReason` |
+| `message_update` / `error` | `reason === "aborted"` | *(no event)* — records `stopReason` |
+| `tool_execution_start` | — | `tool-call { toolCallId, toolName, arguments: args }` |
+| `tool_execution_end` | — | `tool-result { toolCallId, result, isError }` |
+| `turn_end` | assistant `message.stopReason` present | records `stopReason` |
+| `turn_end` | assistant `message.usage` present | `usage_update` (see note) |
+| `agent_end` | `willRetry !== true` | **`turn-end { reason: mapStopReason(lastStopReason) }`** — the turn terminator |
+| `agent_end` | `willRetry === true` | *(no event)* — an auto-retry cycle; the turn continues |
+| `agent_start` / `turn_start` / `agent_settled` | — | *(no event)* |
+| anything else (queue_update, compaction, extension_ui, …) | — | ignored |
+
+### `stopReason` → `turn-end.reason`
+
+| pi StopReason | turn-end reason |
+| ------------- | --------------- |
+| `stop` | `completed` |
+| `aborted` | `cancelled` |
+| `error` | `error` |
+| `length` | `max_turns` *(closest "hit a budget limit"; see gap below)* |
+| `toolUse` | `completed` *(never the settled reason; defensive)* |
+| *(absent)* | `completed` |
+
+**Terminator choice.** A prompt turn's RPC stdout sequence ends at `agent_end`
+(verified empirically against pi 0.80.3):
+`response/prompt → agent_start → turn_start → message_* → turn_end → agent_end`.
+Pi's `agent_settled` event is emitted to in-process **extension** listeners
+(`_emitAgentSettled`) but is **not** written to the RPC stdout stream, so it
+cannot be the terminator. This adapter therefore terminates on `agent_end`,
+honoring `willRetry`: an `agent_end{willRetry:true}` (auto-retry) is ignored and
+only the final `agent_end{willRetry:false}` emits `turn-end`.
+
+## Known gaps / assumptions
+
+- **`usage_update.size` / `.used`** — pi's per-message `Usage` reports token
+  totals + cost, but **no context-window size**. The mapper surfaces
+  `usage.totalTokens` as both `size` and `used`. `tokensIn`/`tokensOut` =
+  `input`/`output`; `cost = { amount: usage.cost.total, currency: "USD" }`.
+  A future improvement could issue `get_session_stats` (which carries
+  `contextUsage`) for a true window size, at the cost of an extra round-trip.
+- **`length` → `max_turns`** — pi's `length` stop reason is a token/context
+  cap, not a turn-count cap. `max_turns` is the closest canonical "budget hit"
+  reason; there is no exact equivalent in the `StreamEvent` taxonomy.
+- **Multimodal** — pi's `prompt` command accepts `images: ImageContent[]`.
+  `capabilities.multimodal` is `true` (pi supports it), but the current client
+  extracts **text only** from the host message; image passthrough is not yet
+  wired.
+- **`plan`** — pi emits no plan/todo event on the RPC stream, so this adapter
+  never produces `StreamEvent{kind:"plan"}`.
+- **`steer` / `follow_up`** — pi's RPC mode supports these mid-turn duplex
+  commands (hence `bidirectional: true`), but the AgentCliClient contract only
+  exposes `send` / `cancel`; this adapter maps `send` → `prompt` and `cancel` →
+  `abort`. Steering is available on the wire but not surfaced by the current
+  contract.

package/PI.md

@@ -0,0 +1,103 @@
+---
+name: pi
+id: pi
+description: earendil-works/pi — MIT headless TypeScript coding agent. Driven over pi's persistent JSON-over-stdio RPC mode (`pi --mode rpc`) as a spawned child. Multi-provider (Anthropic/OpenAI/Google), streaming, live-duplex (steer/follow-up/abort mid-turn). No native ACP/MCP, but injected MCP servers are bridged into pi tools via a generated pi extension (see MCP-BRIDGE.md).
+version: 0.1.0
+bin: pi
+install:
+  - method: npm
+    package: "@earendil-works/pi-coding-agent"
+    global: true
+  - method: curl
+    url: https://pi.dev/install.sh
+version_check:
+  cmd: npm view @earendil-works/pi-coding-agent version
+  parse: "(\\d+\\.\\d+\\.\\d+)"
+  range: ">=0.80.0"
+  timeout_ms: 15000
+auth:
+  ref: ./SECRETS.md
+  state:
+    env: [ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_GENERATIVE_AI_API_KEY]
+sandbox: ./SANDBOX.md
+protocol: proprietary
+adapter: "@agentproto/adapter-pi"
+session:
+  mode: persistent
+  idle_timeout_ms: 1800000
+  turn_idle_timeout_ms: 300000
+  context_carryover: true
+capabilities:
+  streaming: true
+  tool_calls: true
+  sub_agents: true
+  file_io: true
+  multimodal: true
+  resumable: true
+  bidirectional: true
+continuation:
+  default: native-resume
+  supported: [native-resume, pinned-session, transcript, none]
+tags: [pi, earendil, proprietary, rpc, agent-runtime, coding, mcp-bridge]
+---
+
+# Pi — AIP-45 manifest overview
+
+`@agentproto/adapter-pi` drives **earendil-works/pi**
+(`@earendil-works/pi-coding-agent`) as a `protocol: "proprietary"` AGENT-CLI
+operator. The canonical, executable manifest lives in `src/index.ts`
+(`defineAgentCli({...})`); this file is the human-readable overview.
+
+## Why `protocol: "proprietary"`
+
+Pi ships neither ACP nor MCP, so neither the `acp` nor the `print` arm applies.
+Pi *does* ship a persistent JSON-over-stdio RPC mode (`pi --mode rpc`), so the
+adapter implements the proprietary-arm `AgentCliClient` contract directly:
+`createAgentCliRuntime` skips its own subprocess plumbing and dynamic-imports
+this package's `createAgentCliClient` factory, which spawns `pi --mode rpc`
+and translates the stream. See [`PI-RPC.md`](./PI-RPC.md) for the wire profile.
+
+## Protocol arm
+
+- **`bin`**: `pi` — a real binary. The proprietary arm never spawns it for you;
+  `client.ts` does, invoking `pi --mode rpc`. `AGENTPROTO_PI_BIN` overrides the
+  path.
+- **`adapter`**: `@agentproto/adapter-pi` (self-reference the proprietary arm
+  dynamic-imports at session start).
+
+## Models
+
+Default `anthropic/claude-sonnet-4-5`. `allowed` is a curated cross-provider
+menu (`anthropic/claude-sonnet-4-5`, `openai/gpt-5.1`,
+`google/gemini-2.5-flash`); the free-form `model` option accepts any pattern
+pi's `--model` understands (`provider/id`, verified against pi's
+`core/model-resolver.ts`). `env` maps provider → key env var.
+
+## Options
+
+| id       | type   | values | maps to |
+| -------- | ------ | ------ | ------- |
+| `model`  | string | free-form `provider/id` | pi `--model <pattern>` spawn flag |
+| `effort` | enum   | `off, minimal, low, medium, high, xhigh` | pi `set_thinking_level` RPC command |
+
+## Modes
+
+A single `default` mode. Pi's RPC surface exposes no plan/build/read-only mode
+switch, so none is invented — the manifest stays honest.
+
+## Continuation
+
+`native-resume` by default. `client.ts` captures pi's session id from the
+`get_state` response after connect; the host persists it and, on a cold start,
+`connect({ resumeSessionId })` re-spawns pi with `--session <id>`.
+
+## Capabilities & MCP bridging
+
+Pi has no native MCP client, but `connect({ mcpServers })` is **bridged**: the
+adapter enumerates the servers' tools and spawns pi with a generated extension
+(`-e <mcp-bridge-extension.mjs>` + `PI_MCP_BRIDGE_CONFIG`) that registers one pi
+tool per MCP tool (`mcp__<server>__<tool>`), proxying calls over
+`@modelcontextprotocol/sdk`. So injected toolsets — including the daemon's
+`agent_start` gateway — are callable from pi, enabling sub-agent orchestration
+when the daemon injects its gateway (`--orchestrator` flag). Mechanism +
+limitations: [`MCP-BRIDGE.md`](./MCP-BRIDGE.md); sandbox: [`SANDBOX.md`](./SANDBOX.md).