SoduWork Carries Pi, Qwen Code, and Google Harness² Through One Conversation: Rules Survive, Billing Does Not
Teams juggling multiple CLI agents can stop re-explaining business rules at every model switch, but the handoff context is hard-truncated, ACP-style harnesses produce no billable usage data, and a Linux-only CPU-sampling assumption silently stalls the scheduler on macOS, so relay cost and reliability stay open questions for production.
A relay experiment ran three AI harnesses inside one SoduWork conversation (session `01a1d12b-7ee4-71b4-9ea5-3e5667a1c7c4`) against 120 cloud gateway fault tickets. Pi 1.4.0 cleaned the data and set four rules (R1–R4) in 8.59s; Qwen Code 0.21.8 produced a regional scorecard in 16.85s that matched 4/4 rules without re-pasting thresholds; Google Harness² 0.2.0 finished a 190-character decision brief in 27s after its first attempt was tripped by a path-safety guardrail.
The handoff works through SoduWork's segmented-conversation bridge: it snapshots the old harness, forces the same working directory, and auto-injects a truncated context summary when the new harness starts. The summary keeps only the trailing 28,000 characters of message text and the last 12 tool records, so early details can fall away.
Cost traces show the relay is serviceable but incomplete. Pi's leg consumed 71,043 tokens (76.4% cache-hit) at about ¥0.048; Google Harness² needed 119,312 tokens with just 6.1% cache-hit across 11 model requests (¥0.232). Qwen Code's ACP events are marked `contextOnly` and sit outside the billing path, so that leg's real cost is unknown. A macOS-only scheduler bug also stalled the first switch: loadavg-derived CPU estimates capped at 100% and blocked `claim_next` even at zero concurrency.
The 4/4 pass proves state carried over, not that a fresh harness independently re-derived the rules: R1's filtering and R2's scoring already lived in Pi's JSON, so Qwen Code validated continuity of artifacts rather than reasoning from scratch.
The macOS scheduler stall is a platform assumption that will keep biting local-dev AI tooling: Linux-only /proc/stat logic silently inflates CPU on Darwin and blocks the scheduler even when nothing is running.
ACP-style harnesses like Qwen Code currently emit contextOnly usage events that the billing path explicitly excludes, so a relay's real cost can vanish from the ledger even as context tokens pile up.
Google Harness² sent 8 model requests to produce a 190-character brief at an 11.8% cache-hit rate, and its own path guardrail killed the first attempt; heavy reasoning pipelines inflate both the cost and the failure modes of a relay.