by Innominds
RELEASE 2026.11.20.4 · 20 NOVEMBER 2026

The Context assistant keeps the conversation in view

On laptop-height windows the Context step's chat could shrink to a sliver: the suggestion chips, the input box and the hints took the space and answers were cut off. The conversation now keeps its height on any screen.

2×taller conversation on a 1366 × 640 window (137 px to 229 px)
1row for the Try asking suggestions, scrolled sideways
0clipped inputs or overlapping footers, from phone to 1920 wide
1097automated tests pass
Fixes

Step 1, Context: the chat on short screens

AreaChange
Try askingIn free chat (an agent whose Context is captured), the label and its suggestions share one row that scrolls sideways, instead of wrapping onto two or three rows above the input.
Conversation heightThe conversation keeps at least 180 px. The pane header, the topic row and the input keep their size, so the conversation is no longer the part squeezed to nothing.
Short windowsWhen the window is too short for everything, the page scrolls instead of cutting off the input or drawing the footer over the panes (seen on a new agent with Why context matters open).
Laptops and zoomed browsersOn windows 820 px tall or less, padding is tighter and the "Enter to send" hint is hidden, which gives the height to the conversation.
Get started

Upgrade

Upgrade TruVelocity

pip install -U "truvelocity-tevv[ui,proxy]"

Check it

tv --version
Quality

How this release was checked

Lint (ruff, format, mypy strict, the core import rule) and the full suite: 1097 passed, none failed (6 database tests skipped: no Postgres, SQL Server or MySQL here; CI runs them). The Context view was measured in Chromium at 390, 1000, 1280, 1366, 1536 and 1920 pixels wide, for a new agent and a captured one: the input is never cut off and the footer never overlaps the panes. The wheel was built and smoke-tested in a clean environment.