Skip to content

chore(chat): mirror shared core/oss-plugins chat folders from kagent-enterprise#2282

Draft
cjlg-soloio wants to merge 1 commit into
kagent-dev:mainfrom
cjlg-soloio:cjlg-soloio/chatPluginFolders
Draft

chore(chat): mirror shared core/oss-plugins chat folders from kagent-enterprise#2282
cjlg-soloio wants to merge 1 commit into
kagent-dev:mainfrom
cjlg-soloio:cjlg-soloio/chatPluginFolders

Conversation

@cjlg-soloio

Copy link
Copy Markdown
Contributor

Description


🤖 written by Claude (start)

Mirrors the shared chat folder structure from kagent-enterprise so the chat UI can be
kept in sync between the two repos as a literal folder copy.

Adds two folders under ui/src/components/chat/:

core/          SHARED — chassis + render tree (copied ENT ⇆ OSS verbatim)
oss-plugins/   SHARED — HITL tool approval, ask-user, subagent panel (copied ENT ⇆ OSS verbatim)

There is no ent-plugins/ here — task→trace linking and rewind/fork are enterprise-only
and never copied to OSS. core/ and oss-plugins/ never import from ent-plugins/, so
they drop in cleanly without it.

Status: staged mirror (not yet wired in)

This lands the structure only. The files are copied verbatim from enterprise and are
excluded from tsc / eslint / next build (tsconfig.json, eslint.config.mjs)
so main stays green. They are not yet wired into the live ChatInterface. Replacing
the current OSS chat with the shared component and verifying no feature regression is
the tracked follow-up. The per-folder READMEs and SHARED_CHAT_FOLDERS.md document the
copy flow and the adaptation checklist (design-system alias, module alias, injected app
context, OSS host).

Related

Part of solo-io/kagent-enterprise#2221. Companion enterprise PR (where the shared folders
originate, with a Storybook story + mock-data harness + screenshot/video tests):
solo-io/kagent-enterprise#2313.

Testing

No runtime change — the copied folders are excluded from the build and not imported by the
app, so next build / eslint . / tsc --noEmit are unaffected. The shared component is
demonstrated (Storybook + Playwright, rendering with mock data and no backend) in the
enterprise companion PR.

Changelog

NONE

🤖 written by Claude (end)

…enterprise

Land the shared chat folder structure so kagent and kagent-enterprise can keep the
chat UI in sync as a literal folder copy:

  ui/src/components/chat/
    core/          SHARED — chassis + render tree (copied ENT <-> OSS verbatim)
    oss-plugins/   SHARED — HITL tool approval, ask-user, subagent panel

No ent-plugins/ here — task->trace linking and rewind/fork are enterprise-only and
never copied to OSS. core/ and oss-plugins/ never import from ent-plugins/, so they
drop in without it.

Staged mirror only: the copied files are excluded from tsc / eslint / next build
(tsconfig.json, eslint.config.mjs) so main stays green, and are not yet wired into
the live ChatInterface. SHARED_CHAT_FOLDERS.md documents the copy flow and the
adaptation checklist (design-system alias, module alias, injected app context, OSS
host). Wiring it in with no feature regression is the tracked follow-up.

Part of solo-io/kagent-enterprise#2221. Companion PR: solo-io/kagent-enterprise#2313.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Carlos Logroño Guerrero <carlos.logrono@solo.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant