Set up Loco with confidence.

System requirements

• Windows 10 or Windows 11 on an x64 computer.
• At least 1 GB free for the application, extraction and temporary setup files, plus space for every GGUF model you download.
• Enough system memory for the model, quantisation and context size you choose. Loco's fit indicator provides guidance before download.
• An internet connection for the application and model downloads. Local inference itself does not require a cloud AI account.

Download and install Loco for Windows

The official Loco 2.0.2 installer is digitally code-signed by Marais Software. Confirm that you downloaded the file directly from this site.

Your first local conversation

1. Check your hardware.Open Loco and review the CPU, memory and GPU profile shown in the interface.
2. Choose a GGUF model.Open Models, select a curated option or provide a direct GGUF download URL.
3. Wait for the download.Keep Loco open until the model is listed as installed.
4. Start the runtime.Select the installed model and start the local model server from Runtime or the top bar.
5. Open Chat.Send a prompt. Responses are generated by the model running on your PC.

Where Loco stores its files

The installed app uses Electron's per-user application-data directory. On a typical Windows installation this is under %APPDATA%\Loco. Inside it, Loco maintains:

models\

Downloaded GGUF model files.

data\

Settings, agents, users, conversations, workflows, API keys and credentials used by the app.

These folders are not automatically a secure vault. Protect your Windows account, disk and backups, particularly if you save credentials or confidential documents.

Manage local models

Choosing a model

Use model size, quantisation and Loco's hardware-fit guidance as a starting point. A model publisher's licence and acceptable-use terms still apply to that model.

Starting the runtime

Select one installed model, choose your context size and GPU-layer settings, then start the server. Loco exposes the model on 127.0.0.1:5319 while it is running. Stop the runtime before changing models or moving model files.

Custom model URLs

A direct URL must point to a GGUF file. Only download models from sources you trust, and verify the publisher and model licence independently.

Agents, documents and users

Create an agent

Choose an installed model, add a system prompt, set temperature and maximum tokens, and optionally attach supporting documents. Loco accepts PDF, TXT, Markdown and CSV files for this feature.

Control local access

Create staff users and assign only the agents they should use. When the LAN portal is enabled, its address follows the pattern http://YOUR-PC-IP:5318/chat.

Review conversations

The Audit area shows conversations created through the staff-agent experience. Treat this history as sensitive business data when backing up or sharing the data directory.

Workflows, credentials and API keys

Loco can create event-driven workflows, incoming webhooks and local API keys. Credentials stored for SMTP or other configured services are used only when the related action runs.

• Give each API key a clear name and remove keys no longer in use.
• Use separate, limited credentials for integrations wherever the service supports them.
• Assume that content sent to SMTP, webhooks or external workflow services leaves the local privacy boundary.
• Do not expose port 5318 directly to the public internet.

What is local and what uses the network

Read the full privacy explanation for both the desktop app and this website.

Local service endpoints

Chat-completions example

With the runtime running, this PowerShell request sends a short prompt to the local model:

$body = @{
  messages = @(
    @{ role = "user"; content = "Write a one-line welcome message." }
  )
  stream = $false
} | ConvertTo-Json -Depth 4

Invoke-RestMethod -Method Post `
  -Uri "http://127.0.0.1:5319/v1/chat/completions" `
  -ContentType "application/json" `
  -Body $body

The endpoint is available only while the model runtime is active. Keep local services behind your workstation and trusted-network controls.

Back up or move your Loco data

1. Stop the model runtime and close Loco.
2. Copy the Loco per-user application-data folder to an encrypted backup location.
3. Restore it only while Loco is closed and only into the matching Windows user's application-data location.
4. Restart Loco and confirm models, agents and settings before deleting any older copy.

Model files can be large. Make sure the backup destination has enough capacity and is allowed to contain any confidential conversations, documents or credentials stored in Loco.

Common problems

Verify release installer

In PowerShell, run Get-FileHash .\Loco-2.0.2-x64.exe -Algorithm SHA256 to verify file integrity.

Installer