[loganj]

🤖

Summary

• Stacked on refactor(agents): type screens against an agent type view #1732. The agents port from feat(agents): serve the agents service to screens over a MessagePort #1725 served the service's state and calls, but not types(). Screens use types() for every type-specific part: the create dialog, settings tabs, provider readiness, models in the composer, and usage. A type's screens also reach its runtime through the handles it exposes (refactor(agents): split the Claude harness into runtime and UI #1719 through refactor(agents): give present the exposed handles as another page would #1731).
• The port client now answers types() and takes present(key, ...), as the service does when everything runs in one page. Each type is built on the screens' side from data the service pushes and from what the screens' page presents. Exposed stores and keyed reads stay synchronous there, and calls go over the port.
• Nothing in the app uses the port yet, so behavior does not change. The hidden agents page (layer 3) will use it.

Details

• New features/agents/type-port.ts:
  • serveTypes(agents) describes each type as data: its identity, title and description, its defaults(), its migration warning, and whether it is hosted. It also says which calls the type answers (models, usage, provider check and attention action) and gives the shape of its expose. With each push it reads every exposed store's snapshot, the provider snapshot, each keyed read a screen asked for, and each shown agent's session scope.
  • typesClient(...) builds an AgentTypeView from a descriptor. The screens' page's presentation is merged through the service's own presented(), and the result is cached, so a type keeps its identity while its stores change. Exposed handles become a proxy:
    • snapshot reads the pushed value;
    • subscribe is the client's change notice;
    • read(key) asks the service for that key once, and answers empty until the key arrives;
    • any other function is a call by path.
  • An AbortSignal argument crosses as a stand-in. Its abort is sent over the port, and the service aborts a signal of its own, so a screen that stops a transcript read stops it in the service.
  • A type whose expose is not plain handles is listed but not shown, and the error is logged. This matches refactor(agents): give present the exposed handles as another page would #1731 in the service's page.
• port.ts:
  • The service subscribes to each type's provider, session controls and exposed stores, so their changes are pushed. It still pushes before each answer.
  • New message kinds: type (a call), watch (a keyed read) and abort.
  • AgentsPortClient now has types and present. sessionState and previewRetype stay out of the client; they come next.

Testing

• New port.test.ts cases, over a real MessageChannel (structured clone):
  • A type and its handles cross. A store reads synchronously and keeps its identity across an unchanged push. A call answers after the change it made. The provider's check, its attention action and models work, and the type keeps its identity.
  • A keyed read reads as empty, then follows the service's value after it changes.
  • Aborting an exposed call's signal aborts the service's signal.
  • A type that exposes a class instance is listed without what it shows.
• service.test.ts: over the real service, the client lists the same types with the same defaults.
• Mutation checks: each of these makes the named test fail.
  • Not sending aborts: the abort test times out.
  • Not subscribing to the types' stores: the type test and the keyed read test fail.
  • Not pushing after a watch: the keyed read test fails.
• tsc --noEmit passes. The agents, Agents page and huddle suites pass (986 tests), except the Agents page avatar-picker test, which also fails on the base branch in this worktree (its node_modules is a symlink).

🤖 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.