> ## Documentation Index
> Fetch the complete documentation index at: https://docs.belvedir.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Local Models

> Trace agents running open models locally via Ollama.

Belvedir traces agents running on local models the same way it traces cloud providers — same sessions, tasks, and groups. The only difference is where the tokens are generated.

## 1. Run a model locally

Download the **Local Inference** desktop app — it bundles the Ollama engine and walks you through picking a model that fits your machine. If you already run [Ollama](https://ollama.com) yourself, that works too (e.g. `ollama pull qwen3:4b`). Either way a local server listens on `127.0.0.1:11434` — Ollama's default. If you've set `OLLAMA_HOST` or run Ollama in Docker with a remapped port, use that address in the `baseURL` below instead.

## 2. Point your agent at the local endpoint

Ollama exposes an OpenAI-compatible API, so your agent talks to it through the OpenAI SDK — which the Belvedir SDK already instruments:

```ts theme={null}
import OpenAI from "openai";

const client = new OpenAI({
  baseURL: "http://127.0.0.1:11434/v1",
  apiKey: "ollama", // required by the SDK, ignored by Ollama
});

const res = await client.chat.completions.create({
  model: "qwen3:4b",
  messages: [{ role: "user", content: "hello" }],
});
```

## 3. Trace it as usual

Nothing changes on the Belvedir side: initialize the SDK with `instrumentModules: { openAI: openai.OpenAI }` and wrap agent runs in `withSession` (see [Quickstart](/quickstart)). Spans arrive with the local model name (e.g. `qwen3:4b`) so you can tell local and cloud calls apart in the dashboard.

> Note: inference stays on your machine, but traces do not — prompts and completions are exported to Belvedir like any instrumented app. Only enable tracing for local workloads you're comfortable sending.