Skip to main content

lazycontroller

License: Apache 2.0 Python 3.13+ Status: alpha

lazycontroller is a drop-in replacement for the openai Python client. When your code asks an LLM for structured output that is really a decision (a category, a yes/no, a score), it asks a fast decision model first and uses its answer if every field is confident enough; otherwise the call goes to your LLM, unchanged.

Why

Codebases everywhere are full of OpenAI() clients asking GPT-class models to categorize a transaction, flag a message or pick a label, and paying LLM prices and latency for what is really a decision. Decision models now do that job in milliseconds, for a fraction of the cost, and tell you how sure they are. You don't need to rewrite anything to use them: change one import.

# from openai import OpenAI
from lazycontroller import OpenAI

When the decision model is confident, it answers. When it isn't, or when the call isn't a decision at all, the request goes to the model you were already calling, exactly as before.

Why "lazycontroller"

In Thinking, Fast and Slow, Daniel Kahneman calls the deliberate mind, his System 2, a lazy controller: it is in charge, but it lets the fast, intuitive System 1 handle whatever it can, and steps in only when that isn't enough. lazycontroller works the same way. A fast decision model (a "System One" model) answers the calls it is sure about; the slow LLM you were already using is called only when it isn't.

Install

pip install lazycontroller

or uv add lazycontroller. Requires Python 3.13+.

Quickstart

Your existing OpenAI client stays the slow side; the fast side here is Jev, a decision model, reached through OpenRouter.

import os
from typing import Literal

from pydantic import BaseModel, Field

from lazycontroller import FastConfig, OpenAI

client = OpenAI(  # the slow side, as before: reads OPENAI_API_KEY
    fast=FastConfig(  # the fast side: a System One decision model
        base_url="https://openrouter.ai/api",
        api_key=os.environ["OPENROUTER_API_KEY"],
        model="typesafe/jev-1.14",
        min_confidence=0.9,  # every field must reach it, or the call goes to GPT
    ),
)


class Transaction(BaseModel):
    category: Literal[
        "groceries",
        "dining",
        "transport",
        "shopping",
        "subscriptions",
        "utilities",
        "income",
        "transfer",
    ] = Field(description="What the money was spent on, or where it came from")


for line in ["NETFLIX.COM 866-579-7172 CA", "GITHUB, INC. SAN FRANCISCO"]:
    completion = client.chat.completions.parse(
        model="gpt-6-luna",
        messages=[
            {"role": "system", "content": "Categorize this bank transaction."},
            {"role": "user", "content": line},
        ],
        response_format=Transaction,
    )
    print(line, "->", completion.choices[0].message.parsed.category, "by", completion.model)

# NETFLIX.COM 866-579-7172 CA -> subscriptions by typesafe/jev-1.14-20261014
# GITHUB, INC. SAN FRANCISCO -> ... by gpt-6-luna-...

Jev is certain the first line is a subscription (confidence 1.00), so it answers and GPT is never called. The second could be a subscription or a one-off purchase; Jev is less sure (around 0.7–0.8, below the default min_confidence of 0.9), so the call goes to GPT as it always did. Either way you get the same ParsedChatCompletion.

examples/transactions.ipynb goes further: shadow mode on ten transactions, a sweep over min_confidence, with_fast, a call that isn't a decision, and the same thing running locally with Ollama. It needs no Jupyter in your project:

uv run --with jupyterlab --with matplotlib --env-file .env jupyter lab examples/transactions.ipynb

Choosing a fast model

The fast side is any server speaking the System One API; the slow side is any OpenAI-compatible API (OpenAI, OpenRouter, Ollama, vLLM, ...).

Fast model server base_url api_key Example model
TypeSafe "https://api.typesafe.ai" your TypeSafe key "jev-latest"
OpenRouter "https://openrouter.ai/api" your OpenRouter key "typesafe/jev-1.14"
Ollama (local) "http://localhost:11434" none "kev:0.8b-q8_0"

Decision models don't all support the same questions: some answer yes/no only. More in configuration.

How it works

For chat.completions.create / parse and responses.create / parse:

  1. Is it a decision? The schema must ask only for closed decisions: Literal/Enum (Choice), bool (yes/no), small integer ranges (Score), optionally nested or | None. A free-text field, tools, streaming, images and the like send the call to the slow model untouched.
  2. Ask the fast model. All fields go in one request, with the conversation as structured JSON state and each field's description as its question.
  3. Gate on confidence. If every field reaches min_confidence, lazycontroller builds a real OpenAI response object from the fast answer. Otherwise the original request goes to the slow model. It's all or nothing, so you never get a half-fast, half-slow answer.

If the fast model errors or lazycontroller can't read a request, the call goes to the slow model as if lazycontroller weren't there: it can save you calls, never break them.

Details, and how to write schemas a decision model answers well: schemas and requests.

Configuration

OpenAI / AsyncOpenAI take every openai argument (the slow side) plus fast=FastConfig(...):

FastConfig(
    base_url=None,  # the System One server; None turns the fast side off
    api_key=None,  # key for base_url, sent nowhere else
    model=None,  # the decision model; None means the server's default
    min_confidence=0.9,  # every field must reach it, or the call goes to the slow model
    enabled=True,  # False sends everything to the slow model
    shadow=False,  # ask both, return the slow answer, report disagreements
    on_route=None,  # called with a Route after every intercepted call
)

To vary settings for part of your code, derive a copy, like with_options:

refunds = client.with_fast(min_confidence=0.97)  # a wrong answer costs more here

All settings, keys and providers: configuration.

Monitoring and choosing min_confidence

Every intercepted call produces a Route: who answered (fast or slow), why, and the confidence of each field. Collect them to see how much traffic the fast model takes.

The default min_confidence, 0.9, is cautious. To choose yours, run with shadow=True on real traffic: both models answer, your users get the slow answer, and each route records whether the two agreed. A ShadowReport turns those routes into coverage and agreement for each min_confidence:

from lazycontroller import ShadowReport

report = ShadowReport(routes)
print(report.table())
report.suggest_min_confidence(min_agreement=0.98)  # lowest value keeping 98% agreement

Route fields, shadow mode and ShadowReport: routing.

Data and privacy

  • With a hosted fast model, the conversation of every eligible call is also sent to that provider (TypeSafe, OpenRouter, ...). Check that this fits your data agreements before enabling it. A local fast model keeps everything on your machine.
  • In shadow mode, eligible calls go to both providers.
  • Free models on some platforms may use requests for training; don't send real data to them.
  • Keys go only where they belong: FastConfig.api_key is sent only to FastConfig.base_url, and no key is picked up from the environment for the fast side.

To report a security issue, see SECURITY.md.

Limitations

  • Forced tool calls (tool_choice with a function) aren't treated as structured output yet, so they always go to the slow model.
  • Only OpenAI-style clients for now: no from lazycontroller import Anthropic yet.
  • with_raw_response, with_streaming_response and streaming always go to the slow model.
  • Answers from the fast model aren't stored by the slow model's provider (store=True has no effect on them).

Development

The project is managed with uv. CI runs lint and tests on Python 3.13–3.15 for every pull request.

uv run pytest                              # tests (both models are faked, no keys needed)
uv run --python 3.13 --isolated pytest     # tests on the minimum version
uv run ruff check && uv run ruff format    # lint and format

The documentation site is built with Zensical from docs/:

uv run --group docs python scripts/notebooks_to_docs.py   # example notebooks -> pages
uv run --group docs zensical serve                        # preview, reloads on changes

examples/transactions.ipynb is a runnable tour of the library; uv run --with jupyterlab --with matplotlib opens it without adding either to the project.

License

Apache License 2.0.

Metadata

Release files for lazycontroller 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lazycontroller 0.1.0
File Size Uploaded Provenance Actions
lazycontroller-0.1.0.tar.gz 25.7 kB With provenance Details for lazycontroller-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for lazycontroller 0.1.0
File Interpreter ABI Platform Actions
lazycontroller-0.1.0-py3-none-any.whl Python 3 none any Details for lazycontroller-0.1.0-py3-none-any.whl

Total release size: 50.9 kB

Release files / lazycontroller-0.1.0.tar.gz

Download URL lazycontroller-0.1.0.tar.gz
Size 25.7 kB
Tags Source
SHA-256 checksum
How to use checksums
8af0b2b8518151fce9035be4bf36c14bed5d51aeab3755a37c37403696d26813
BLAKE2b-256 checksum
How to use checksums
e5b76f9614d6a83b5bb6f2fb3dbd7f5e4c7c8acd6f22dae00d68aa4aeab5b980
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / lazycontroller-0.1.0-py3-none-any.whl

Download URL lazycontroller-0.1.0-py3-none-any.whl
Size 25.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
daf0574443af7e3553ad7d292e2bf50e68a3f66a9975872f9990111fb690d8d2
BLAKE2b-256 checksum
How to use checksums
1bbd3139674906b6727a43d26e047dcc6be3111cc40cbe3eb3cc59a58187dba6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Security for lazycontroller 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for lazycontroller-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page