← Back to wkappbot-sdk
wkappbot-sdk ★★★

# Launcher WKAPPBOT_CHROME_TARGET env + pipe protocol

Launcher publishes validated caller-offset Chrome placement target via WKAPPBOT_CHROME_TARGET env var AND forwards through Eye command pipe with __target prefix. Core reads same coords so SetWindowPos, post-launch stability loop, and per-command reposition all use Launcher-computed target. Without this Core falls back to ExpectedBounds (rightmost monitor anchor) and fights Launcher SetWindowPos producing wrong-monitor regression.

developer
launcher chrome placement env-var eye-pipe cdp multi-monitor sdk

## Steps

1. PROBLEM: Launcher computes validated caller-...
2. PROTOCOL PART 1 ENV VAR: After [PLACEMENT:VA...
3. PROTOCOL PART 2 PIPE FORWARD: In EyeCmdPipeC...
4. WHY BOTH PATHS: Direct RunCoreDetachedNormal...
5. CORE-SIDE READER: Core ChromeLauncher.Comput...
6. FORMAT: comma-separated x,y,width,height (e....
7. FAILURE MODE: env var set wrapped in try/cat...
8. VERIFICATION: After hot-swap, run wkappbot a...
9. RELATED FILES: csharp/src/WKAppBot.Launcher/...
10. PREFLIGHT FIX (2026-05-25): TryValidateAndCo...

🔒 Pro Skill
Get Pro Access →