@sayknow-cli/coding-agent 0.4.3 → 0.4.5

package/CHANGELOG.md

@@ -5,6 +5,52 @@ This file tracks the **fork's own releases**; upstream's full feature history li
 in that project. Each release notes the upstream version it is built on.
 
 
+## [0.4.5] — 2026-07-23
+
+### Added (Sayknow Pet in tmux)
+
+- **Auto-enable the Sayknow Pet (and inline sixel graphics) under tmux when the
+  outer terminal genuinely supports sixel.** Previously graphics were
+  unconditionally suppressed under any multiplexer because tmux advertises
+  compile-time sixel support (`DA1 ";4"`) regardless of the attached terminal,
+  and no code emitted the DCS passthrough envelope. Now:
+  - The startup sixel capability probe runs under tmux with its DA1 +
+    XTSMGRAPHICS queries wrapped in tmux's `\ePtmux;…\e\\` passthrough envelope,
+    so the **outer** terminal answers — a positive reply is genuine end-to-end
+    evidence, not tmux's unreliable self-report. screen/zellij (no passthrough
+    envelope) stay suppressed.
+  - Sixel render output (pet frames + inline images) is wrapped in the same
+    passthrough envelope under tmux.
+  - SKC-launched tmux sessions set `allow-passthrough on` (pane-scoped, quiet on
+    tmux < 3.3) automatically.
+  - Probe-gated and safe: terminals that do not actually render sixel through
+    tmux (e.g. Ghostty, which uses the kitty protocol and has no sixel) never
+    activate it, so no garbage escapes are emitted. Set `SKC_SIXEL_MULTIPLEXER=0`
+    to force the pre-0.4.5 behavior (graphics off under tmux).
+
+## [0.4.4] — 2026-07-22
+
+### Fixed (workflow arbitration native)
+
+- **Port `skc-notifications` to upstream v0.11.6 and switch pi-natives to
+  `sdk.rs`.** 0.4.x synced upstream's coding-agent, whose SDK bus requires the
+  native `NotificationServer` arbitration API (`registerArbitratedAsk`,
+  `retireIfUnclaimed`, `stopAndWait`). But the fork's `skc-notifications` crate
+  was stuck at upstream v0.9.1, so `crates/pi-natives/src/sdk.rs` (restored from
+  v0.11.6) could not compile against it and was dropped from `lib.rs`. The
+  shipped `notifications.rs` `NotificationServer` lacked the arbitration
+  methods, so every SDK session startup threw `NativeRuntimeCompatibilityError`
+  ("required workflow arbitration methods are missing") — extensions failed to
+  load and no session could start on 0.4.1–0.4.3.
+- Upgrades `crates/skc-notifications` v0.9.1 → v0.11.6 (adds the
+  `broker_protocol`/`control`/`query`/`reverse` modules and the `hmac` workspace
+  dependency), wires `mod sdk;` and retires `notifications.rs`. This restores
+  the arbitration API **and** the SKC v3 SDK connection lane
+  (`onSdkFrame`/`sendTo`/`onConnectionClose`/`registerWorkflowGateAsk`/
+  `pushTurnStreamUnchecked`), which was also dead in 0.4.1–0.4.3. No native
+  method that the fork already relied on is removed (`sdk.rs`'s
+  `NotificationServer` is a strict superset of `notifications.rs`).
+
 ## [0.4.3] — 2026-07-21
 
 ### Fixed (cross-platform native publish)

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@sayknow-cli/coding-agent",
-	"version": "0.4.3",
+	"version": "0.4.5",
 	"description": "Sayknow-CLI CLI with read, bash, edit, write tools and session management",
 	"homepage": "https://sayknow-cli.com",
 	"author": "jaybeyond",
@@ -52,12 +52,12 @@
 		"@agentclientprotocol/sdk": "1.2.1",
 		"@babel/parser": "^7.29.3",
 		"@mozilla/readability": "^0.6.0",
-		"@sayknow-cli/stats": "0.4.3",
-		"@sayknow-cli/agent-core": "0.4.3",
-		"@sayknow-cli/ai": "0.4.3",
-		"@sayknow-cli/natives": "0.4.3",
-		"@sayknow-cli/tui": "0.4.3",
-		"@sayknow-cli/utils": "0.4.3",
+		"@sayknow-cli/stats": "0.4.5",
+		"@sayknow-cli/agent-core": "0.4.5",
+		"@sayknow-cli/ai": "0.4.5",
+		"@sayknow-cli/natives": "0.4.5",
+		"@sayknow-cli/tui": "0.4.5",
+		"@sayknow-cli/utils": "0.4.5",
 		"@puppeteer/browsers": "^2.13.0",
 		"@types/turndown": "5.0.6",
 		"@xterm/headless": "^6.0.0",

package/src/modes/components/sayknow-pet-widget.ts

@@ -14,6 +14,7 @@ import {
 	type SayknowPixelFrameName,
 	type SayknowPixelFrames,
 	type TUI,
+	wrapTmuxPassthrough,
 } from "@sayknow-cli/tui";
 import type { CustomEditor } from "./custom-editor";
 import { getPetPixelProtocol } from "./pet-capability";
@@ -280,6 +281,9 @@ export class SayknowPetWidget {
 			sixelTopPaddingPx: protocol === "sixel" ? PET_SIXEL_DROP_PX : 0,
 			kittyCellYOffsetPx: protocol === "kitty" ? petKittyDropPx(cell.heightPx) : 0,
 			kittyImageId: protocol === "kitty" ? this.#kittyImageId : undefined,
+			// Forward the pet's sixel raster through tmux's DCS passthrough envelope
+			// when under tmux (no-op otherwise), so the outer terminal renders it.
+			wrapSixel: wrapTmuxPassthrough,
 		});
 		this.#framedEditor.setReserve(this.#pixel.columns + PET_SIDE_MARGIN);
 	}

package/src/skc-runtime/tmux-common.ts

@@ -245,6 +245,13 @@ export function buildSkcTmuxProfileCommands(
 	if (envDisabled(env[SKC_TMUX_PROFILE_ENV])) return commands;
 	commands.push(
 		{ description: "enable tmux clipboard integration", args: ["set-option", "-t", target, "set-clipboard", "on"] },
+		{
+			// Forward DCS passthrough (sixel graphics / Sayknow Pet) to the outer
+			// terminal. `-pq` scopes it to this session's pane (never the global
+			// server state) and stays quiet on tmux < 3.3 where the option is unknown.
+			description: "allow DCS passthrough for sixel graphics",
+			args: ["set-option", "-pq", "-t", target, "allow-passthrough", "on"],
+		},
 		{
 			description: "make copy-mode selection readable",
 			args: ["set-window-option", "-t", target, "mode-style", "fg=colour231,bg=colour60"],