Forge hallmark plate — the struck mark in an iron well on an ember enamel plate

Where local intelligence is shaped into tools.

Forge calls language models running on machines you control, from TypeScript or the command line. One small interface over your own Ollama runtime, returning a typed result with the execution evidence the runtime reported.

The data path

Four parts, one direction of travel.

Forge architecture — Your app to Forge to Ollama to a local model
Your app sends a prompt to Forge, Forge calls Ollama, Ollama runs a local model. Forge owns the boundary in the middle and nothing else.

Install

One package, no production dependencies.

Forge is ESM-only and requires Node.js 22 or newer. It never installs, pulls, or configures a runtime or a model — you bring those.

npm install forge-local-ai-kit

Usage

The whole public API is one function.

createForge, ForgeError and the public types are exported from the package root and nowhere else.

ask.mjs

import { createForge, ForgeError } from "forge-local-ai-kit";

const forge = createForge({
  provider: "ollama",
  host: "http://localhost:11434",
  model: "qwen3:8b",
});

try {
  const result = await forge.ask("Explain a bloom filter.");
  console.log(result.output);
  console.log(result.model, result.metrics.clientLatencyMs);
} catch (error) {
  if (error instanceof ForgeError) {
    // Branch on the category, never on the message text.
    console.error(error.category, error.message, error.evidence);
  } else {
    throw error;
  }
}

Local-first

Nothing leaves the machines you already trust.

  • Your host, and no other

    Prompts and responses go to the host you configure and nowhere else. Forge contacts no other service.

  • Nothing kept

    No persistence, no telemetry, no analytics, and no logging of prompts or responses. Only the response you asked for is returned; hidden reasoning is never surfaced.

  • No configuration of its own

    As a library Forge holds no credentials and reads no environment. Your application owns its configuration and passes normalized values in.

Forge Maker's Mark — struck state, iron ground

Every tool bears the mark.

A smith stamps finished work so you know the shop it came from. The mark sits beside anything that has actually been verified, and nowhere else. Every figure below names the file, the workflow, or the registry it was read from.

Where Forge sits

Four roles, one ecosystem.

Each does one job and knows where the others are. The names below are roles, not a shared visual identity: Pathfinder, Lorekeeper and LAMA keep their own.

  • Forge The smithy

    Shapes raw local intelligence into tools another program can hold.

  • Pathfinder The guide

    Marks the route through the work, from first debate to release.

  • Lorekeeper The archive

    Keeps what has been learned so it can be found again.

  • LAMA The companion

    The face you talk to, and the first to carry a tool out of the smithy.