Skip to main content

New in Wave 0.26.0

· 4 min read
Martin Turoci

Another Wave release arrived! This time, with a main focus on LLMs. See the full changelog to learn more.


Large language models are all the rage nowadays, the race is on. Wave aims to help with showing the results of the LLMs and what can be better than an interactive chatbot widget?

As with most things in Wave, we try our best to make the code as simple and straightforward as possible:

from h2o_wave import main, app, Q, ui, data

async def serve(q: Q):
if not q.client.initialized:
# List buffer is a dynamic array. Cyclic buffer can also be used. Must have exactly 2 fields - content and from_user.['example'] = ui.chatbot_card(
box='1 1 5 5',
data=data('content from_user', t='list'),
q.client.initialized = True

# A new message arrived.
if q.args.chatbot_name:
# Append user message.['example'].data += [q.args.chatbot_name, True]
# Append bot response.['example'].data += ['I am a fake chatbot. Sorry, I cannot help you.', False]


The chatbot_card requires a new type of buffer called list buffer to be used. It acts as a dynamic array, providing a simple append operation (+=) and indexing (negative indexing is supported as well).

The widget supports features like:

Stay tuned for a Github repo with a sample ChatGPT-like Wave app.

By-name component access

Wave allows for updating component attributes like label, content, value etc.:

async def serve(q: Q):['example'] = ui.form_card(box='1 1 4 4', items=[
ui.button(name='step_button', label='Step 1'),
# Update button label.['example'].items[0].button.label = 'Step 2'

The problem is that this code is not very flexible as it depends on the order of items, which can easily change. Wave 0.26.0 comes with a better mechanism - use component name as index.['example'] = ui.form_card(box='1 1 4 4', items=[
ui.button(name='step_button', label='Step 1'),

# ❌ Pre Wave 0.26.['example'].items[0].button.label = 'Step 2'
# ✅ Use the "name" attribute to access to component.['example'].step_button.label = 'Step 2'

File configuration

Waved can now be configured via .env files in addition to command-line arguments and environment variables. The priority goes: cmd arg > env var > config > default. By default, waved looks for a file called .env in the same directory. The configuration file location can also be specified by -conf argument or H2O_WAVE_CONF env variable.

The app can be also configured by .env file - uvicorn foo:main --nv file. See deplyoment docs for more info.

Live demos

In order to bring Wave closer to the AI community without the need for any installation, we decided to put some of our core Wave apps to Hugging Face spaces!

Sprinkle code blocks with colors

From now on, Wave supports markdown code syntax highlighting natively.

sample_markdown = '''=
<!DOCTYPE html>

<style>body {width: 500px;}</style>

<script type="application/javascript">
function $init() {return true;}

<p checked class="title" id='title'>Title</p>
<!-- here goes the rest of the page -->
'''['example'] = ui.markdown_card(
box='1 1 4 4',
title='I was made using markdown!',



We look forward to continuing our collaboration with the community and hearing your feedback as we further improve and expand the H2O Wave platform.

We'd like to thank the entire Wave team and the community for all of the contributions to this work!