clemvault internals production

Local Clembot LLM

An Ollama adapter that routes agent harness calls to a local LLM, cutting session costs and keeping sensitive client context off the cloud.

OllamaLLaMA 3TypeScriptWindows 11

Claude API costs $15-30 per long build session. Sensitive client context shouldn’t leave the machine. Some tasks (summarization, formatting, light reasoning) don’t need a frontier model. This is the local drop-in for those cases.

The Problem

The agent harness routes everything to Claude API by default. There’s no local LLM path. That means every task, regardless of complexity, runs at frontier model pricing. And sensitive client prompts leave the machine.

What It Is

An Ollama adapter that sits between the agent harness and the model layer. Task routing rules in a config file determine which tasks use the local LLM (LLaMA 3, Mistral, or Phi-3) vs. which fall back to Claude. On error, the adapter falls back automatically. Local conversation logs write to Obsidian.

Features

Stack

ToolRole
OllamaLocal LLM runtime (CPU or GPU)
LLaMA 3 / Mistral / Phi-3Model options
TypeScript / PythonAdapter layer
Windows 11Host machine

Cost Case

Internal tooling. The value is measured in API cost reduction and data privacy, not revenue.

Development timeline

2 logged updates over 77 days, 15 May 2026 to 30 Jul 2026.

  1. The local-model lane shipped, under a different projectfeature

    The delegation lane this project existed to build landed inside token-thrift instead, on the day that skill was built. It pins one local model on the loopback Ollama port, states that nothing leaves the machine, names a hosted provider as…

  2. Scoped: run the harness on a local modelfeature

    The problem was cost and confidentiality in one. Long build sessions were spending real money per session, and some internal prompts carry business context that should never leave the machine.

Written from this project's decision log as work happened, not afterwards. See every project →