BloomDesktop: Skill for Claude Code

Bloom Exe CDP Automation

Outcome

Use the real embedded WebView2 inside Bloom.exe as the automation target. Determine whether Bloom is already running, whether it belongs to this worktree, stop the right processes when necessary, start the current worktree through a source-aware launcher, discover the live CDP target, and drive the UI through the embedded browser instead of Bloom APIs.

When To Use

• You need to know whether Bloom is already running.
• You need to know whether the running Bloom came from the wrong worktree.
• You need to kill a confusing stale Bloom or dotnet watch parent process.
• You need to start Bloom from the current worktree.
• You need to attach to the embedded WebView2 for DOM, console, network, and screenshot/debug access.
• You need Playwright tests to hit the actual exe instead of http://localhost:8089/bloom/CURRENTPAGE in a separate browser tab.

Default Assumptions

• Current repo root is derived automatically by the checked-in helper.
• Bloom project path is src/BloomExe/BloomExe.csproj.
• Fresh automation launches must not start an already-built Bloom.exe directly, because that can miss local source changes.
• Use a source-aware launcher. In this repo the current default is ./go.sh at the repo root.
• go.sh launches the coordinated dev flow from src/BloomBrowserUI/scripts/go.mjs, which in turn starts the front-end and the exe together.
• In automation mode Bloom writes a machine-readable BLOOM_AUTOMATION_READY {...} line to the console as soon as it knows its HTTP, CDP, and process IDs.
• Running Bloom reports its actual HTTP and CDP ports through http://localhost:<port>/bloom/api/common/instanceInfo.

Commands

Examples below assume you are somewhere inside the repository and first compute the repo root once:

repo_root="$(git rev-parse --show-toplevel)"

Terminal:

• In this VS Code workspace, the shared bash terminal keeps whatever cwd the previous command left behind.
• Prefer running the helper through $repo_root/.github/skills/... or $repo_root/scripts/... so the command does not depend on the current working directory.