[loganj]

🤖

Summary

• Stacked on feat(agents): forward tools the screens' page adds to the agents port #1738. Builderlab registers its hosted agent type whole from its UI entry, because its provider steps use the Builderlab sign-in that lives in the UI. Once agents run in their own page, the agents service must still see that type. This lets the screens' page register it with the service over the agents port.
• Nothing uses it yet, so behavior does not change. The agents window PR will connect it.

Details

• hosted-port.ts has two halves:
  • hostedClient (screens' page): register(type, owner) sends the type's id, title, description, defaults() value, provider steps and readiness to the service. What the type shows (Create fields, tabs, provider dialog, config functions) stays in this page, through present.
  • serveHosted (agents page): it registers a stand-in type. Its provision, activate, profile, interrupt and remove steps, and its provider check and attention action, are forwarded to the screens' page.
• Each step's signal is carried across: when the service aborts it, the screens' page's step sees its own signal abort.
• Readiness (the provider snapshot, such as "Log in to Builderlab") is pushed to the service each time it changes.
• Reloads behave as for tools in feat(agents): forward tools the screens' page adds to the agents port #1738. A reloaded service gets the types listed again. When the screens' page reloads and lists a type again, the service ends that type's open steps with an error.
• serveAgents now takes { addTool, register } instead of a bare addTool.
• Refusals: the screens' page refuses a type that runs its agents itself (no remote), or one with parts that only an agent entry can give (run, models, usage, sessions, sessionControls, syncedSettings, expose, …). The error says that its plugin needs an agent entry. No bundled or installed plugin registers such a type from its UI entry.

Testing

• service.test.ts: the real agents service, with a hosted type that the screens' page registers. The type's Create field and provider dialog are shown from the screens' page; its readiness reaches the service and changes there; creating an agent runs provision and activate in the screens' page; removing it runs remove.
• port.test.ts, over a JSON event bus:
  • A step's result crosses, and an abort reaches the step in the screens' page.
  • A local type, and a hosted type with usage, are refused.
  • A step that a reloaded screens' page never answers ends with an error, and a reloaded service gets the type listed again.
• Mutation checks: each of these makes a test fail: not carrying the abort, not listing again after a reload, not ending abandoned steps, not updating readiness, and not presenting what the type shows.
• tsc --noEmit, Biome, and vitest run src/features/agents src/buzz-mcp (866 passed) pass.

🤖 Generated with Claude Code

[loganj]

🤖 Closing: the Manager/Runner split replaces this design (#1748 → #1839, with more to come). The branch stays in place because #1737, #1743 and #1744 are still stacked on it. They will move onto the new stack in the hidden-page step.