Three MCP tools to manage the user's Chromium instances by profile, distinct
from browser_launch's isolated automation Chrome:
- browser_list: enumerate running Chromium master processes by scanning
/proc/*/cmdline (has --user-data-dir, no --type=). Returns pid, profile,
user_data_dir, cdp_port, has_cdp as a JSON array.
- browser_launch_profile: launch a concrete profile using the REAL binary
/usr/lib/chromium/chromium (bypassing the /usr/bin/chromium wrapper). No CDP
by default so Google keeps the session for human profiles; cdp=true adds
--remote-debugging-port + --remote-allow-origins=*. Detects DISPLAY/XAUTHORITY
from the XFCE session and launches decoupled via setsid.
- browser_close: locate a master by profile/cdp_port/pid, SIGTERM with a 10s
wait, then SIGKILL as a last resort.
Per-profile instances are NOT registered in the connection pool: they are
user-facing and survive the MCP dying; cleanup is explicit via browser_close.
Unit tests for cmdline master detection, flag parsing, and close-target
matching. Bumps version 0.6.0 -> 0.7.0 (42 -> 45 tools).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
