Keep existing Platforms entrypoint accessible in web UI

[Copilot]

When OpenMessage is connected, the reconnect banner was fully hidden, which could remove the visible path to the Platforms dialog during runtime. This made WhatsApp/Signal pairing harder to reach in some states.

• UI access path

  • Removed the newly introduced sidebar Platforms button.
  • Reused the existing connection-banner entrypoint instead of adding a new persistent control.

• Connection-banner behavior update

  • Updated setConnectionState() in internal/web/static/index.html so that when Google Messages is connected and neither WhatsApp nor Signal is paired/connected, the banner remains visible with a Platforms action (open-platforms).
  • If a secondary platform is already paired/connected, existing behavior remains (banner hidden while Google is connected).

• Scope

  • No API changes and no modal wiring changes; this is a focused UI-state logic fix using the existing launch path.

[Copilot]

Pull request overview

Adds a persistent UI entrypoint to the existing “Platforms” modal so users can always open the pairing/reconnect dialog (WhatsApp/Signal/etc.) even when the reconnect banner is hidden during normal connected runtime.

Changes:

• Added an always-visible “Platforms” button to the sidebar action cluster.
• Wired the new button to open the existing platforms/WhatsApp overlay flow.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chz160]

@copilot apply changes based on the comments in this thread

Something else to note, lets double check that we need the new button. There is already an existing way to open the platform dialog, it just doesn't seem to show or have a way to show it when the server is running. we might want to look at the related code and think hard about this one. We don't want to make the wrong UI change when something else is staring us in the face.

[Copilot]

@copilot apply changes based on the comments in this thread

Something else to note, lets double check that we need the n...

Updated in commit a5d3376.

I removed the newly-added sidebar Platforms button and switched to the existing entry path by updating the existing top connection banner logic: when Google Messages is connected but neither WhatsApp nor Signal is paired/connected, the banner now stays visible with a Platforms action (open-platforms). This keeps access to the dialog while the server is running without introducing a new persistent button.

Screenshot: /tmp/openmessage-platforms-entrypoint.png

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: /home/REDACTED/.cache/ms-playwright/chromium_headless_shell-1181/chrome-linux/headless_shell /home/REDACTED/.cache/ms-playwright/chromium_headless_shell-1181/chrome-linux/headless_shell --disable-field-trial-config --disable-REDACTED-networking --disable-REDACTED-timer-throttling --disable-REDACTEDing-occluded-windows --disable-back-forward-cache --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-REDACTED-pages --disable-component-update --no-default-browser-check --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=AcceptCHFrame,AutoExpandDetailsElement,AvoidUnnecessaryBeforeUnloadCheckSync,CertificateTransparencyComponentUpdater,DestroyProfileOnBrowserClose,DialMediaRouteProvider,ExtensionManifestV2Disabled,GlobalMediaControls,HttpsUpgrades,Impro rg/toolchain@v0.0.1-go1.25.0.lin--annotation=plat=Linux --gdwarf-5 eow/binary -o rg/toolchain@v0.0.1-go1.25.0.lin-buildtags (dns block)
• instantmessaging-pa.googleapis.com
  • Triggering command: /tmp/TestBuiltBinaryAcceptsPairCommand4157827929/001/openmessage /tmp/TestBuiltBinaryAcceptsPairCommand4157827929/001/openmessage pair -stringintconv l/linux_amd64/vet /tmp/go-build1841404633/b379/vet.cfg sform.go 0.1-go1.25.0.linux-amd64/src/encgithub.com/beeper/argo-go/block ux-amd64/pkg/tool/linux_amd64/vet credential.usern/home/REDACTED/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.25.0.linux-amd64/pkg/too-buildtags /sys mpile ux-amd64/pkg/too-buildtags conf�� OiRm/0sV_het8FNL-errorsas _cgo_.o ux-amd64/pkg/tool/linux_amd64/vet (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.