aboutsummaryrefslogtreecommitdiff
path: root/FORK.md
AgeCommit message (Collapse)Author
2026-10-14FORK.md: hosted on git.soarez.net, not castleIgor Soarez
2026-10-14fix(profile): never prompt for a profile when driving a remote browserIgor Soarez
Profile selection works by launching the browser with --profile-directory and letting ProcessSingleton delegate to the running process, which only reaches a browser on this machine. discoverEndpoint() already withholds userDataDir for a remote target, but resolveUserDataDir() fell through to the local candidate dirs, so the picker offered this disk's Chromium profiles for a browser on another host - on castle, Brave's profiles for a Chrome on :9223. Pinning one launched a local browser and polled the remote for a sentinel that could never appear, failing after the seed deadline; seedProfileWindow()'s mismatch guard missed it because connectedDir is undefined on the remote path. Setup now returns early instead of prompting - the question had no actionable answer, and since cancelling stores nothing it returned every session. /browser-profile and seedProfileWindow() refuse with the reason, the latter catching a pin left over from a local session.
2026-10-14docs: castle restarts Chrome on failure, not hourlyIgor Soarez
2026-10-14fix(setup): skip local-browser precondition for every remote targetIgor Soarez
The pre-flight check only skipped isBrowserRunning() when BU_CDP_HTTP was set, so a machine with no local browser failed /browser-setup with 'No browser instance running' before discovery ever dialed the built-in castle default. Resolve the target the same way discovery does and skip the local-process check whenever it resolves remote — env var, /browser-target choice, or default. A resolved local target still requires a local browser, and an unreachable remote still fails loudly in step 4.
2026-10-14docs: /browser-target, and why switching restarts the daemonIgor Soarez
2026-10-14docs: castle is now the default; document the override tableIgor Soarez
BU_CDP_HTTP is an override rather than a requirement, and /browser-status explains the lazy connection instead of showing a bare red light.
2026-10-14docs: fork notes — why BU_CDP_HTTP exists, install, upstream mergesIgor Soarez
Kept out of README.md so upstream's own README continues to merge cleanly.