In this article
A LibreChat agent saves a model, category, and instructions; optional files and tools introduce additional configuration and access requirements.
To start a LibreChat agent with a local model, first establish the model connection, then save a minimal agent in Agent Builder. The agent is reusable application configuration, not a new model or an automatic local tool environment.
The concrete application boundary
Agent Builder exposes configuration that should be kept deliberately minimal during onboarding. Model and Category are required, while the description is optional. Instructions may be entered inline or sourced from a saved prompt; choose inline text for the first exercise so that access to another prompt object does not become an extra dependency. File uploads for File Search or File Context follow agent creation. The Tool Library reflects administrative settings and role permissions, and an entry marked Needs setup is not ready just because it appears. None of those optional resources is necessary to prove a text-only local agent. This makes the first failure easier to attribute. Choose a recognizable agent name, then select that saved agent again from a fresh chat to verify that its instruction is actually reused (LibreChat feature documentation).
A practical route
Confirm that a plain conversation works through the intended local provider. Open Agent Builder from the side panel and choose Create New Agent. Give the assistant a name, select the required Model and Category, and enter narrow instructions. Click Create before attaching files. Start a conversation by selecting the agent or using its entry from the chat interface (LibreChat Agents).
A worked example
Build a helper that rewrites fictional issue descriptions into reproduction steps and unanswered questions. Initially attach no tools or files: paste a harmless issue directly into the conversation. Compare the result with the instruction. After editing the instruction, start a fresh test so that previous conversation context does not hide the effect of the change.
| Check | Record |
|---|---|
| Connection | The local provider and actual model used by the baseline conversation. |
| Saved agent | The selected model, category, and instruction for issue triage. |
| Trial | The fictional issue and whether the response separates facts from missing information. |
Reading the failure correctly
A missing local model is a provider configuration problem, while an unavailable tool can involve role permissions or additional setup. Do not enable unrelated resources to repair a plain text task. If an agent produces unsupported reproduction details, correct the instruction and inspect the source issue rather than claiming that reuse guarantees correctness (LibreChat configuration example).
What completes the check
The starting agent is useful when its owner can explain the selected model and repeat the same bounded task. Add files or tools only for a concrete next requirement, then test their access independently.
Related background: llama.cpp server: a local API from a GGUF model, VRAM for LLMs: why model size is only part of the calculation.