crewAIInc / crewAIInc/crewAI

[FEATURE] Add an OpenUI guide and runnable CrewAI Flow example

Open
#7,046 1 comment 0 reactions 1 assignee View on GitHub

@Vidit-Ostwal is already working on this.

Since Aug 25, 2026.

vendor-pitch
Dominant language
Python
Stars
58.8k
Forks
8.5k
Avg merge
1d 15h
Merged PRs (30d)
109

Description

Feature Area

Documentation

Is your feature request related to an existing bug?

N/A

Describe the solution you'd like

Add a dedicated guide and runnable example that show how to render CrewAI Flow responses with OpenUI.

The integration uses CrewAI for the Flow lifecycle, conversation state, and LLM calls. The existing ag-ui-crewai endpoint carries requests and streamed events. OpenUI generates the component prompt, parses and renders OpenUI Lang, applies the UI theme, and sends follow-up or form actions into new CrewAI turns.

The documentation would include:

  • an OpenUI page in the frontend guide
  • links from the frontend overview, Generative UI, A2UI, and Conversational Flows pages
  • Arabic, Korean, and Brazilian Portuguese translations
  • a runnable Python backend and React frontend under docs/examples/openui-crewai
  • chart, follow-up, and validated form examples

Tested versions:

  • CrewAI 1.15.16
  • ag-ui-crewai 0.3.0
  • @openuidev/react-ui 0.13.6
  • @openuidev/react-lang 0.2.11

Validation completed:

  • 4 backend tests passed
  • 3 frontend tests passed
  • TypeScript and Vite production build passed
  • OpenUI prompt and library spec generation passed
  • navigation JSON and diff checks passed
  • browser checks passed for theming, chart rendering, a follow-up LLM turn, form values returning to the Flow, and viewport overflow
Describe alternatives you've considered

Tool-based rendering and A2UI remain useful when the application owns each component or catalog. Building a custom chat shell around the lower-level OpenUI renderer would duplicate the message list, composer, streaming state, and action handling already provided by OpenUI AgentInterface.

Additional context

The example uses the existing CrewAI Flow and AG-UI extension point. Generated OpenUI prompt and library spec files remain ignored build artifacts.

AI-assisted contribution. Maintainers: please apply the required llm-generated label because outside contributors cannot set repository labels.

Willingness to Contribute

Yes, I'd be happy to submit a pull request.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.