Skip to content

spec: OpenUI 1.0-beta community review draft - #925

Draft
Aditya-thesys wants to merge 1 commit into
mainfrom
spec-0.9-community-draft
Draft

spec: OpenUI 1.0-beta community review draft#925
Aditya-thesys wants to merge 1 commit into
mainfrom
spec-0.9-community-draft

Conversation

@Aditya-thesys

@Aditya-thesys Aditya-thesys commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

OpenUI specification, 1.0-beta community review draft

Three documents under spec/:

  • overview.md: what OpenUI is, every feature with examples, how to build with it, and the proposed 1.0-beta extensions (extend, multi-library segments, versioning, registries, data components, constraints).
  • language.md: the normative language specification: grammar, program model, evaluation, streaming rules, state and forms, data and actions, incremental editing, error recovery, serialization, client checklist.
  • prompt.md: the LibrarySpec and everything sent to the model: spec documents, prompt generation, signatures and docs, the conversation contract.

Sections 1 to 3 of the overview and everything unmarked in language.md describe shipped behavior; (proposed) marks designed but unshipped features, collected in overview section 4 for review.

This is a review draft: feedback welcome on any section, especially the proposed extensions.

@vercel

vercel Bot commented Aug 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openui-docs Ready Ready Preview Aug 5, 2026 2:24pm

Request Review

Comment thread spec/overview.md
A library derives from another with one method, covering both directions of the common request: use the default library but add your own components, or use it minus the parts your product does not want.

```tsx
export const library = defaultLibrary.extend({

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extending a library means, I have to know each and every component in the library. should we just promote composition instead?

Comment thread spec/overview.md
```openui-lang library=charts
root = ChartCard([rev])
rev = BarChart(labels, [series])
```

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LLM would need to be careful about escaping if it uses backticks. should the fences be something unique like

|>>>> openui-lang lib=charts
Lang
|<<<<

or we expect LLMs to be smart enough?

Three documents: overview.md (guide, features, proposed extensions),
language.md (normative language specification), prompt.md (LibrarySpec
and the prompt contract).
@Aditya-thesys
Aditya-thesys force-pushed the spec-0.9-community-draft branch from c36d9c0 to 946369a Compare August 5, 2026 14:20
@Aditya-thesys Aditya-thesys changed the title spec: OpenUI 0.9 community review draft spec: OpenUI 1.0-beta community review draft Aug 5, 2026
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.

2 participants