Operator surfaces
Chat and Apps
Choose the right surface
| Surface | Use it for | Durable output |
|---|---|---|
| Chat | Open-ended tasks, investigation, and repository work | Thread history, files, and selected memory |
| App | Repeated workflows and structured operator interfaces | App data, queryable collections, and an App thread |
Start uncertain work in Chat. When a repeated workflow needs a durable interface, ask the agent to turn it into an App.
Move beyond transcripts
Kern Apps are the UX layer for agent work. They turn a repeated workflow into a focused interface where the operator can revisit the records, filters, decisions, and actions that matter without searching through a long conversation.
How to use an App
- 1Start with the operator job
Define the repeated decisions, records, filters, and actions the interface should support.
- 2Ask the agent to build it
Begin in Chat and create one App when the work needs its own durable interface.
- 3Operate through the UI
Open the App for the everyday workflow. Its data and interface persist independently of a single response.
- 4Iterate in the App thread
Ask for layout, workflow, and data-model changes in the App's own thread so its identity and state stay connected.
UI backed by durable state
| Store | Use it for | Rule of thumb |
|---|---|---|
| App data | Settings, summaries, and small structured state | Use named paths and preserve unmentioned values |
| Collections | Large or repeated queryable rows | Use a collection when the UI filters, sorts, or pages records |
| App thread | Building and improving the experience | Keep App-specific iteration attached to the App |
The UX stays inside the boundary
Generated App code cannot use arbitrary network access, browser storage, navigation, timers, imports, or external libraries. Durable state belongs in App data or collections. When the experience needs a real-world tool action, the agent performs it through Kern's governed tool and approval boundary.