OpenUI Lang: Support live data sources

Aperta
  • Qualcosa non va?
#388 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Aditya-thesys ci sta già lavorando.

Dal 25/3/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement

Is your feature request related to a problem? Please describe.
OpenUI responses can render data-rich UI, but the data in a response is mostly fixed at the time the model generates it. If the underlying data changes, the user often needs to ask again or the app needs to regenerate the whole response.

This is limiting for UI that should stay current, such as dashboards, metrics, stock prices, tickets, incident status, analytics, weather, inventory, or any view backed by an API or MCP tool.

Describe the solution you'd like
Allow OpenUI responses to include live data sources that can refresh independently of the original model response.

Ideally, OpenUI should support data sources backed by APIs, MCP tools, or registered host functions. A generated response could declare that a component depends on a live query, and the renderer/runtime would keep that data fresh.

This should support:

  • Declaring live data dependencies in OpenUI Lang.
  • Fetching data from an API, MCP tool, or host-provided provider.
  • Refreshing data on an interval, on demand, or when inputs change.
  • Showing loading, error, and stale states in rendered UI.
  • Updating only the affected part of the response instead of regenerating the entire message.
  • Cancelling or ignoring stale requests when a newer request is made.
  • Keeping the model output declarative and safe, so the model cannot execute arbitrary code.
  • Clear docs and examples for live charts, tables, cards, and metric components.

Describe alternatives you've considered

  • Ask the model to regenerate the full response every time data changes.
  • Fetch data outside OpenUI and manually inject it into component props.
  • Build custom components that handle their own data fetching.
  • Use only static snapshots of API results in generated responses.

These approaches work for simple cases, but they either duplicate data-fetching logic, make generated UI harder to reuse, or prevent OpenUI responses from staying current.

Additional context
This would make OpenUI much more useful for dashboards, monitoring views, analytics reports, admin panels, and assistant responses that need to reflect real-time or frequently changing data.

This likely overlaps with Query / Mutation, tool provider support, and MCP integration. The important part is that live data should be represented as a safe declarative dependency in OpenUI Lang, with actual execution handled by trusted runtime providers.

Lingua principale
TypeScript
Stelle
10k
Fork
698
Merge medio
1g 6h
PR unite (30g)
148

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di thesysdev/openui

Tutte le issue di thesysdev/openui

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.