Skip to content

feat(ui): add full-page Assistant, backed by assistant-chat-kit - #6

Draft
kevwilliams wants to merge 1 commit into
mainfrom
feat/assistant-page
Draft

kevwilliams wants to merge 1 commit into
mainfrom
feat/assistant-page

Conversation

@kevwilliams

Copy link
Copy Markdown
Contributor

Summary

  • Adds a full-page "Assistant" route (portal.page/project, .../services/interconnect/assistant) — a full-page counterpart to the assistant plugin's docked ChatDock, reusing the same @datum-cloud/assistant-chat-kit conversation logic against the same per-project Patch backend. Interconnect-specific answers come from that backend's own AgentBinding capability document (separate work), not from anything in this repo.
  • Fixes vite.config.ts, which had no Module Federation shared singletons at all. Without @datum-cloud/portal-plugin-sdk shared as a singleton, useProjectContext()/usePluginFetch() would read a disconnected React Context instead of the host's (this would have broken any future use of those hooks, not just this page). Added react-dom/client too, matching a gotcha already documented in the assistant plugin's own config.
  • Expands package.json's dependencies to @datum-cloud/datum-ui's full optional-peer surface (leaflet, monaco, recharts, dnd-kit, etc.), discovered via real build failures — its subpath exports aren't independently tree-shakeable, so importing just /assistant still pulls in shared chunks referencing the rest of the library at build time. Matches the assistant plugin's own (equally broad) dependency list rather than a hand-picked subset.

Test plan

  • bun run typecheck passes clean
  • bun run build succeeds
  • Verified against the real published @datum-cloud/assistant-chat-kit@0.1.0
  • Manual smoke test: load the plugin in cloud-portal's dev shell, navigate to the assistant page, confirm it starts a conversation and streams a response

New portal.page/project extension (interconnect.datumapis.com/Assistant,
routed at .../services/interconnect/assistant) — a full-page counterpart
to the assistant plugin's docked ChatDock, using the same
@datum-cloud/assistant-chat-kit conversation logic against the same
per-project Patch backend. Interconnect-specific answers come from that
backend's own AgentBinding capability document, not from anything here.

vite.config.ts needed shared singleton entries it was missing entirely
(react-dom/client, @datum-cloud/portal-plugin-sdk) — without them,
useProjectContext()/usePluginFetch() would read a disconnected Context
instead of the host's. package.json needed @datum-cloud/datum-ui's full
optional-peer surface, not just the pieces this page uses directly:
its subpath exports aren't independently tree-shakeable, so importing
just /assistant still pulls in shared chunks referencing leaflet,
monaco, recharts, etc. at build time.
@kevwilliams
kevwilliams marked this pull request as draft September 18, 2026 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant