all repos — sz-chrome-remote-cdp @ f6bab02b6b93c3804ec83b853e333fba417a0988

pi-browser-harness, patched to drive a Chrome on another host over CDP, with castle_cdp_search web search

fix: remove browser footer status indicator (#10) (#11)

The footer status chip set during session_start could go stale: after a
successful /browser-setup, the setup command only called ctx.ui.notify()
and never updated ctx.ui.setStatus("browser", ...), so the footer kept
showing the red "Browser — run /browser-setup" nudge even though the
browser was connected.

Rather than syncing the status from the setup handler, remove the footer
status indicator entirely. Browser control is on-demand and the setup
command already reports its own outcome via notify(), so the persistent
footer chip added no value and only introduced a stale-state bug.

Closes #10
Aman Kumar 145339995+amankumarsingh77@users.noreply.github.com
Sun, 12 Jul 2026 22:03:37 +0530
commit

f6bab02b6b93c3804ec83b853e333fba417a0988

parent

1c12b43a674ae51a39c430ed8cfa138dbdf4dc71

1 files changed, 0 insertions(+), 4 deletions(-)

jump to
M src/index.ts → src/index.ts

@@ -144,10 +144,6 @@ toolsRegistered = true;

} registerSetupCommand(pi, client); registerDeepResearchCommand(pi); - ctx.ui.setStatus( - "browser", - client.status().alive ? "🟢 Browser connected" : "🔴 Browser — run /browser-setup", - ); }); pi.on("session_shutdown", async () => {