# Langflow with a local model: a first conversational flow

Build a local Langflow conversation with Model Providers, a Language Model component, explicit input/output connections, and Playground verification.

Author: Retrivium team
Updated: 2026-11-03
Canonical URL: https://retrivium.ai/journal/langflow-local-model-first-flow/
Language: en

To build a first local Langflow conversation, configure the local provider, enable its model, and connect Chat Input through a Language Model to Chat Output. A cloud-based quickstart example does not make a cloud credential mandatory for every local model path.

## The concrete application boundary

Langflow’s current model component documentation separates global provider configuration from selection inside a flow. Open the profile menu, Settings, and Model Providers to manage available models. A model enabled there becomes selectable by model-driven components. The Language Model component performs generation, while Chat Input and Chat Output provide direct conversation interaction. A Prompt Template can supply a system message when that input is enabled. These are typed component connections, so visual proximity on the canvas does not transmit data. Keep the initial graph explicit and avoid an agent template with extra tools when the task needs only a text response ([Langflow documentation](https://docs.langflow.org/)) ([Langflow Language Model component](https://docs.langflow.org/components-models)).

## A practical route

In the existing local Langflow instance, configure Ollama or the compatible local provider using its required fields, save, and enable the intended language model. Create a flow with Chat Input, Language Model, and Chat Output. Select the enabled model in Language Model. Connect Chat Input to Input, then Message output to Chat Output. If using a Prompt Template, enable System Message in the component inspection panel and connect the template there. Open Playground and submit a harmless text question ([Langflow Quickstart](https://docs.langflow.org/get-started-quickstart)).

## A worked example

Create a writing helper whose instruction asks for a short answer and a separate list of unknowns. Supply a fictional project brief through Playground. Verify that the brief reaches the model and that the unknowns are not converted into invented project facts. Then edit the instruction while keeping the model selection and component wiring unchanged, which isolates prompt behavior from a broken connection.

| Check | Record |
| --- | --- |
| Provider layer | The local model enabled in global Model Providers. |
| Graph layer | Chat Input → Language Model Input; Language Model Message → Chat Output. |
| Instruction layer | The optional template connected to the explicitly enabled System Message input. |

## Reading the failure correctly

An enabled model is not necessarily the one selected in the component. A disconnected Chat Output can hide a successful generation, while an unconnected prompt template cannot affect the system message. Inspect each port and the component output before altering model parameters or adding another integration.

## What completes the check

The flow is ready for further experimentation when Playground shows the intended response through visible connections. Exported API examples and external execution are separate next steps; they are not necessary to prove this local conversation graph.

Related background: [A local RAG server: placing components around the GPU](/journal/rag-server-local-architecture/), [llama.cpp server: a local API from a GGUF model](/journal/llama-cpp-server-launch/).