Let plugins open external links and workspace browsers (#4972)

* feat(plugins): open external links and workspace browsers

* fix(plugins): refuse invalid links and unavailable browser workspaces

* docs(plugins): clarify external links and browser navigation
This commit is contained in:
Mohamed Boudra
2026-09-16 23:25:17 +02:00
committed by GitHub
parent a8a8da0472
commit c7db3c5a8c
19 changed files with 532 additions and 69 deletions
+5 -5
View File
@@ -283,11 +283,11 @@ when moved between hosts. Explorer configuration can create workspace-context pa
existing agent-context instances, but it cannot create an agent panel without an agent-aware command.
Command Center callbacks use the selected host's existing `PaseoApi` for normal Paseo operations.
They use typed plugin RPC only for plugin-specific backend work. Surface and panel props expose
optional client-owned agent and workspace navigation; its absence is the compatibility gate for
older clients. Navigation targets the selected host unless the call includes another `serverId`.
Other navigation remains limited to registered global surfaces and workspace panels. Plugins do not
receive Expo Router or workspace-layout store access.
They use typed plugin RPC only for plugin-specific backend work. Surface and panel navigation
belongs to the app; plugins do not receive Expo Router or workspace-layout store access.
See the public [navigation fields](../public-docs/plugins/v0.8/reference.md#surfaces-and-sidebar-items)
and [external links and workspace browsers](../public-docs/plugins/v0.8/reference.md#external-links-and-workspace-browsers)
for the author-facing contract.
## Lifecycle hooks