gazesight 0.4.0 → 0.5.0

package/README.md

@@ -4,7 +4,7 @@
 
 **Let your coding agent see what you see.**
 
-GazeSight lets coding agents inspect the browser tab you're already using, without launching another browser session. Firefox is fully supported and Mozilla-approved (0.3.4). Chrome is supported via manual installation while it awaits Chrome Web Store review. Node.js 20+ and an MCP coding agent with image support are required. Technical decisions and measured results live in `GAZESIGHT_MASTER_SPEC.md` in the source repository.
+GazeSight lets coding agents inspect the browser tab you're already using, without launching another browser session. Firefox is fully supported and publicly available from Mozilla Add-ons (0.4.0). Chrome is supported via manual installation while it awaits Chrome Web Store publication. Node.js 20+ and an MCP coding agent with image support are required. Technical decisions and measured results live in `GAZESIGHT_MASTER_SPEC.md` in the source repository.
 
 ## Install and first capture
 
@@ -27,13 +27,15 @@ npx gazesight doctor
 ```
 
 1. Run `gazesight setup` in a real terminal. It configures Claude Code, Codex, or both, then keeps a temporary loopback pairing listener open. Re-running setup is safe and leaves existing client registrations unchanged.
-2. Install a compatible extension: **Firefox 0.4.0+** or **Chrome 0.2.0+**. These versions are development candidates and are not publicly distributed yet; the public npm 0.3.5 and Firefox 0.3.4 releases still use manual import.
+2. Install a compatible extension: **Firefox 0.4.0+** from Mozilla Add-ons or **Chrome 0.2.0+** by loading the packaged extension manually while Chrome Web Store publication remains pending.
 3. Open GazeSight and click **Connect to GazeSight**. Confirm that the six-digit verification code matches the terminal, then explicitly approve it there. The code expires and is not the permanent credential.
 4. Open your local project in your browser, keep its tab active, and click **Use this tab**. Pairing never selects or authorizes a tab automatically.
 5. Restart your coding agent to load MCP, then run `gazesight doctor` while its GazeSight connection is active.
 6. Ask your agent: "Use GazeSight visual_capture to inspect my active preview tab." The image arrives directly as MCP image content.
 
-Compatibility: npm/MCP 0.4.x pairs with Firefox 0.4.x and Chrome 0.2.x. The published npm 0.3.5 runtime remains compatible with the published Firefox 0.3.4 extension through Advanced manual configuration; zero-friction pairing is not available in those older builds. New and legacy browser credentials are scoped independently, and importing a legacy JSON configuration remains a recovery fallback rather than a pairing prerequisite.
+Compatibility: npm/MCP 0.4.x pairs with Firefox 0.4.x and Chrome 0.2.x. The prepared 0.5.x runtime/Firefox and 0.3.x Chrome candidates remain unpublished until their release gates are approved. The published npm 0.3.5 runtime remains compatible with Firefox 0.3.4 through Advanced manual configuration; zero-friction pairing is not available in those older builds. New and legacy browser credentials are scoped independently, and importing a legacy JSON configuration remains a recovery fallback rather than a pairing prerequisite.
+
+Claude Code and Codex can both be configured, but the current local architecture allows only one GazeSight MCP process to own a configured bridge port at a time. A second process exits explicitly with `GS_PORT_IN_USE`; close the first client session before starting the other, or use a separate config and port. GazeSight does not terminate or silently take over another process.
 
 Claude Code stores user-scope servers in `~/.claude.json`; Codex uses `~/.codex/config.toml` with `[mcp_servers.gazesight]`. Setup generates installation-specific Node/CLI paths; it never relies on a developer's source checkout. See [Claude Code MCP docs](https://code.claude.com/docs/en/mcp-quickstart) and [Codex MCP docs](https://developers.openai.com/codex/mcp/).