Teaches coding agents how to build TUIs with TamboUI correctly: API-level selection, render-thread discipline, display-width safety, CSS-aware element authoring, and JFR conventions.
87
90%
Does it follow best practices?
Impact
84%
1.44xAverage score across 5 eval scenarios
Passed
No known issues
You are extending a TamboUI Toolkit app that has three interactive panes side by side: a chat history pane, a trace log pane, and an input prompt at the bottom. The skeleton of the app already exists, but focus management is broken in several user-visible ways:
Your job is to fix all four of these issues. The fix should be ergonomic enough that adding a fourth pane later is a one-liner — no per-pane special-case handling.
Produce a single file FocusedApp.kt (or Java equivalent FocusedApp.java) containing the relevant slices of the ToolkitApp subclass. You do not need to reproduce the full panes — stubs are fine — but you DO need to show:
render() (or its relevant slice) and any helper you introduce.You may assume the three pane elements (chatList, traceList, promptInput) are already declared as fields elsewhere in the class and are built with the appropriate Toolkit factory methods — you only need to show the parts of their builder chain that pertain to focus.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
rules
skills