Problem Statement

Jan currently renders assistant responses as markdown, which limits richer generative UI outputs such as interactive cards, tables, follow-up actions, and structured UI components. Models can emit UI-like content, but Jan does not have a first-class integration for rendering OpenUI Lang responses or guiding models to produce valid OpenUI output.

Feature Idea

Add OpenUI as an optional integration under Settings → Integrations, alongside Claude Code and MCP.

When enabled, Jan should:

• Append OpenUI prompt guidance to chat requests so models can emit valid OpenUI Lang.
• Render OpenUI Lang assistant responses using @openuidev/react-ui.
• Support choosing the OpenUI component library, such as chat or standard components.
• Lazy-load the OpenUI renderer so normal markdown chat performance is not affected.
• Handle OpenUI CTAs as real chat actions, submitting the clicked prompt through Jan’s normal message flow.
• Fall back to markdown when OpenUI is disabled or the response cannot be parsed.

This would let Jan support richer interactive assistant responses while keeping the feature opt-in and isolated from the default chat experience.

If this direction sounds good, I’d love to work on this issue.