@khalilgharbaoui/opencode-claude-code-plugin 0.42.1 → 0.42.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@khalilgharbaoui/opencode-claude-code-plugin",
-  "version": "0.42.1",
+  "version": "0.42.3",
   "description": "Claude Code CLI provider plugin for opencode",
   "homepage": "https://opencode-claude-code-plugin.dev/",
   "funding": {

package/skills/claude-code-plugin/SKILL.md

@@ -312,7 +312,11 @@ without it they fail clearly. This changes transport, not account access or bill
 
 Interactive transport takes text plus images (PNG/JPEG/GIF/WebP staged as 0600 files
 whose paths the TUI attaches, deleted after the turn; PDFs and other blocks are
-dropped with a warning) and reads completed transcript blocks, not token
+dropped with a warning). A message sent while a proxied tool runs reaches the same turn
+through the TUI's own input queue, as on headless. A turn ends on its stop reason or
+`turn_duration`, or, as a safeguard for a CLI that writes neither, after 20 s of total
+silence once it has its reply (reported as ended without a stop reason). It reads
+completed transcript blocks, not token
 deltas. It currently re-reads the transcript while polling. Normal interactive turns
 do not forward opencode's system prompt, and have no account-failover form or
 model-fallback chain. `/btw` is answered by a short-lived fork of the conversation
@@ -859,9 +863,14 @@ options an applied preset replaced), `interactiveTransport`, `planModeQuestion`,
 (`not detected` means the binary did not answer `--version`, which also disables
 version-gated flags). Cwd is a startup fallback snapshot, not the per-session spawn
 directory. MCP names are disk discovery, not proof of live connectivity. The startup
-`interactiveTransport` boolean reports the legacy preference only, not the new
-`transport` selection or proof that Bun PTY transport was used. Check a
-relevant, redacted spawn/bridge entry for actual routing after an approved normal turn.
+`transport` field is the requested mode (`auto` / `headless` / `interactive` /
+`invalid`, resolved as the provider resolves it) and `interactiveTransport` is true
+when `interactive` was requested by either spelling; neither proves the PTY ran
+(`auto` stays headless until the CLI refuses `--print`). `/claude-code-doctor`'s
+live-process rows carry a per-process transport column, which is the proof; the
+spawn log line is the other. The PTY was measured on Claude Code 2.1.288: a newer
+CLI logs one WARN per version ("has not been measured") and the doctor flags it,
+but nothing is refused.
 
 Useful log lines to search for (redact payloads): `spawning new claude process`,
 `bridged opencode skills into claude`, `interrupt sent for aborted turn`, `btw:`,