Skip to content

Track upstream/browser-host localhost reachability gap #61

Description

@fitchmultz

Summary

External testing still reports open http://localhost:<port>/... and http://127.0.0.1:<port>/... failing with net::ERR_EMPTY_RESPONSE even when shell curl confirms the server is live.

Current wrapper state

The extension now documents and diagnoses this as browser-host loopback reachability:

  • README Current limits notes that localhost resolves from the browser host, not necessarily the shell/Pi host.
  • TOOL_CONTRACT documents the same boundary.
  • Presentation adds a local fixture hint for loopback navigation failures.
  • SUPPORT_MATRIX tracks RQ-0111 and RQ-0119.

Evidence

  • Maintainer local direct probe with agent-browser 0.27.0 and a same-host Python HTTP server succeeds.
  • External tester environment still fails with ERR_EMPTY_RESPONSE while shell curl succeeds.
  • This suggests provider/browser launch namespace, proxy, container/VM, or host networking behavior outside this thin wrapper.

In-scope next action

Keep this issue as the local tracking link for upstream/environment follow-up. A true fix likely requires upstream agent-browser browser-launch networking support or an explicit host-bridge story. This extension should not add a server manager or localhost proxy without a separate design pass.

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedWaiting on external input, access, decision, or upstream evidence before local work is justifiedneeds-reproNeeds a minimal reproducible command/artifact setquestionFurther information is requestedupstream-boundaryRequires upstream, browser-host, or environment support outside this thin wrapper

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions