Skip to content

Interface and controls

Flow Code presents each conversation as a tab. The sidebar chat drives a turn, and the center editor panels carry the run output and detail views. This page covers the controls you use to pick a model, tune how it runs, watch context usage, manage tabs, and work with the generated DSL.

Each tab carries its own model selection, so different tabs can target different models at the same time. The model picker groups entries into local and cloud sections. Local models come from the Model Hub and run through the managed local runtime. Cloud models are the opt-in cloud providers. The selection you make on a tab stays with that tab.

Next to the model picker, a per-model run-config popover exposes how the selected model runs:

  • Context size. For local models, a slider sets the context window. It is wired to llama-server --ctx-size, the same flag documented in the local runtime. The slider is shown for local models, where the runtime owns the process.
  • Reasoning. A reasoning on/off toggle controls whether a capable model produces thinking traces. When it is on, the trace streams live into a collapsible Thinking section above the turn’s reply. Local models stream their raw trace; cloud models return a summarized trace, since the provider does not expose the full chain of thought.

A context-usage ring shows how much of the model’s context window the current turn occupies. Hover the ring for a breakdown of what fills the window. For the full accounting, open the Context Usage detail tab, which lays out the same breakdown in an editor panel.

The sidebar header keeps two icon-only controls: History and Settings. History opens a floating panel over the chat that lists past conversations grouped by recency, with a search box to filter them. Settings opens the shared settings surface described in the settings reference. Both controls carry accessible labels even though they render as icons.

A new tab starts with a default name and is retitled automatically from your first prompt, so the tab strip reads as a list of topics rather than “Flow 1, Flow 2”. Right-click a flow tab for its context menu:

  • Rename the tab to override the generated title.
  • Pin the tab so it stays in place.
  • Export the tab.
  • Close, Close others, Close to the right, Close to the left, and Close all.

The run panel shows the generated Flow DSL in an editable overlay with live syntax highlighting, covered in DSL syntax highlighting. Two export actions sit alongside it:

  • Export DSL writes the generated .flow document.
  • Export output writes the run output.