What’s New in 0.2

Prepare the default chat library and inspect local setup before rendering OpenUI in Rails.

After reading this guide, you will know:

  • How to initialize the default library without browser-console copying.
  • How to find missing local setup steps without running actions.

Version 0.2.0 adds two setup tasks. See Release History for release dates.

Prepare the default library

After installing the engine, copy the exact pinned chat-library exports:

bin/rails openui:library:prepare

The task writes the configured prompt/spec files and their upstream license. It requires no browser, Node, network, or provider. Repeated runs keep identical files unchanged; different existing files require explicit overwrite. Read Library and Prompt Contract before replacing custom files.

Inspect local setup

Check library identity, asset checksums, and the engine’s action route:

bin/rails openui:doctor

Required failures produce a nonzero exit status. Browser registration, authorization policy, external assets, shared replay storage, and snapshot recovery still need application verification. The task prints those limits without invoking your callbacks or exposing file contents. See Setup Diagnostics.

Next Steps