pi-agent-rb 1.1.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3c4f0ddb3c0e7d8dd8c01189b0b27469f1c62f5293ffe6aee263b41af4c248d3
-  data.tar.gz: 0fc2f911b59a4e0ae3e0a78897ce5a1457e29d7badcf1e6623b12d8754d9e803
+  metadata.gz: f7c01a8fec7bf4290d4482d3789e16b8606b96282d1c1b9a2b4483fb74f31cd6
+  data.tar.gz: 9bbe1686b1f30a66ac752e59fb6fe5cfd1aba2bd55412626379fa79a0687d56f
 SHA512:
-  metadata.gz: 1ae00b74a6ce44eec1e0e25cd5250ff0f6c2f68e2495d005bd69367611c71ce253a3d096cf51e83c4e64d4710d4c226ab29bc20ab7027562faf5597ca9c485d8
-  data.tar.gz: 6d0ab90a5e5a95014b2604973e13790fa9d44a43fd6baf813dabaebf2fe7de41bc75fe7970aa6b00d885de6bd64edcef17fe6bcba7614017d5c33f032d91ae09
+  metadata.gz: fd191daa5f49d399d2918b11992e7f34604aec94573c21cdc0abac2bde8af6d61f52ca3d757859c1bb532125728cb9a3822b17214376ff1a696be69a7d51fa79
+  data.tar.gz: d20001bfc37bda6c2ef11b4140b3c08db81abc707fbb7ccd5ec8c7622a1ff2ae0c8f9aab9210217480fd78ce5a2ac409436d7d60f639aa4abd4cd52fa99328ae

data/CHANGELOG.md

@@ -7,6 +7,69 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.2.1] - 2026-10-16
+
+Tracks pi 1.3.0 (rolls up `1.2.0` and `1.3.0`). No gem API change: the RPC
+mode sources (`src/modes/rpc/*`, `rpc-entry.ts`) and `docs/rpc.md` are
+unchanged between pi 1.1.0 and 1.3.0, so the JSONL RPC command/response
+shapes this gem drives are the same.
+
+### Changed
+- Bumped pinned upstream `pi-coding-agent` version to `1.3.0` (from `1.1.0`).
+  - `1.2.0` — CLI/TUI, extension API (`before_agent_start` becomes a
+    `messageType` union; session counts as busy while a run starts), MCP
+    (`pi mcp list --json` reports `resources: true`; non-object structured
+    content), codemode, per-key OpenRouter model lists, and published
+    `$schema` config schemas.
+    Release notes: https://github.com/earendil-works/pi/releases/tag/v1.2.0
+  - `1.3.0` — `sessionShareDestination` setting for `/share`; `kimi-coding`
+    moves to Chat Completions (`models.json` base URL overrides must include
+    `/v1`); model switching drops prior-model thinking; resumed sessions keep
+    their active tools (`--tools +name`/`-name` applies on top); `--model`
+    prefers the provider with credentials; retry/provider fixes.
+    Release notes: https://github.com/earendil-works/pi/releases/tag/v1.3.0
+
+## [1.2.0] - 2026-10-10
+
+Tracks pi 1.1.0 (rolls up `1.0.1`, `1.0.2`, `1.0.3`, `1.0.4`, and `1.1.0`).
+Verified against a real `pi --mode rpc` 1.1.0 (live specs green).
+
+### Added
+- `Event#aborted?` — true for an `agent_settled` event whose run was aborted
+  (pi >= 1.1.0), so callers can tell a cancelled run from a finished one.
+
+### Changed
+- Bumped pinned upstream `pi-coding-agent` version to `1.1.0` (from `1.0.0`).
+  None of the intermediate releases alter the JSONL RPC command/response
+  shapes this gem drives, so no gem API change is required.
+  - `1.0.1` — CLI/TUI/MCP/provider/packaging batch: Nix flake install path;
+    project-level overrides for user MCP servers; MCP Client ID Metadata
+    Documents (`oauth.clientRegistration: "cimd"`); `pi.registerToolRenderer()`;
+    Cloudflare Clef classifier models. Packaging: `brace-expansion` pinned to
+    5.0.12 (security advisory) and `npm-shrinkwrap.json` removed from the
+    published package. All CLI/TUI, MCP, codemode, or provider concerns.
+  - `1.0.2` — adds `samplingParamsByThinkingLevel` to `models.json` for
+    per-thinking-level sampling overrides on OpenAI-compatible APIs.
+    Provider/config concern only.
+  - `1.0.3` — renames the Azure provider `azure-openai-responses` → `azure`
+    (breaking for `auth.json`/`models.json`/`settings.json` provider keys) and
+    adds Azure Foundry Chat Completions deployments; codemode `image()`
+    temp-file behavior; editor `Home`/`End` key changes. Provider/config,
+    CLI/TUI, and codemode-local concerns, outside the RPC surface.
+  - `1.0.4` — `--tools`/`--exclude-tools` accept `*` patterns and keep MCP
+    tools unless an entry starts with `mcp__`; `--no-mcp` flag; codemode
+    `tools.read()` returns an image block for image files. All CLI/TUI,
+    codemode, MCP, or provider concerns.
+  - `1.1.0` — adds program status reporting over OSC 7501, Claude Haiku 5.5
+    (`anthropic/claude-haiku-5-5`), `+name`/`-name` entries for `--tools`,
+    GPT-6 Luna image classification, and native llama.cpp decision models.
+    The one RPC-adjacent change is additive: `aborted` is added to
+    `agent_settled` session, extension, and JSON events so integrations can
+    tell a cancelled run from a finished one; surfaced as `Event#aborted?`.
+    `tool_execution_end` also gains `durationMs` (reachable via
+    `event[:durationMs]`). All other changes are CLI/TUI, codemode, or
+    provider concerns.
+
 ## [1.1.0] - 2026-10-01
 
 Tracks pi 1.0.0. No gem API change; verified against a real `pi --mode rpc`

data/README.md

@@ -14,7 +14,7 @@ building interactive agent UIs (web, TUI) on top of pi.
 
 - Ruby 3.3+
 - `pi` 0.80.4+ on `PATH` (install via `npm i -g @earendil-works/pi-coding-agent`)
-- This gem is pinned against pi `1.0.0`; other versions may work but are not verified.
+- This gem is pinned against pi `1.3.0`; other versions may work but are not verified.
 
 ## Installation
 
@@ -105,7 +105,7 @@ Pi emits `agent_end` after each low-level agent run, but may then retry,
 compact and retry, or process queued continuations. It emits
 `agent_settled` only when no automatic work remains, so high-level streams
 use that as their completion boundary. Upstream added the RPC event in pi
-0.80.4; it is available in this gem's pinned pi 1.0.0.
+0.80.4; it is available in this gem's pinned pi 1.3.0.
 
 `events` is a lower-level, prompt-less drain of the same stream. Because it
 subscribes lazily when iteration begins, it only works when you subscribe
@@ -279,6 +279,8 @@ timeouts then remain the only backstop when pi dies.
   (`"aborted"` vs `"error"`). This covers `extension_error` events and
   errored assistant turns. The gem does not abort your iteration on
   agent errors; you decide how to react.
+- To tell a cancelled run from a finished one, check `Event#aborted?` on
+  the terminal `agent_settled` event (pi >= 1.1.0).
 
 ## Protocol reference
 

data/lib/pi_agent/event.rb

@@ -57,6 +57,12 @@ module PiAgent
       assistant_event["reason"]
     end
 
+    # True for an `agent_settled` event whose run ended because it was
+    # aborted (pi >= 1.1.0). Distinguishes a cancelled run from a finished one.
+    def aborted?
+      @type == :agent_settled && @raw["aborted"] == true
+    end
+
     def to_h
       @raw
     end

data/lib/pi_agent/version.rb

@@ -1,9 +1,9 @@
 # frozen_string_literal: true
 
 module PiAgent
-  VERSION = "1.1.0"
+  VERSION = "1.2.1"
 
   # Pinned upstream pi-coding-agent version this gem is verified against.
   # See: https://www.npmjs.com/package/@earendil-works/pi-coding-agent
-  SUPPORTED_PI_VERSION = "1.0.0"
+  SUPPORTED_PI_VERSION = "1.3.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pi-agent-rb
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.2.1
 platform: ruby
 authors:
 - chagel