TangleBrain is a local-first, config-driven router across OpenAI-compatible backends you own. A request enters through one front door, the router decides which configured backend should serve it, an adapter performs the call, and the result is logged and returned. Everything routable is described in a plain editable config file — adding or removing a backend is a config edit, not a code change.
This document describes the architecture as of v0.9.0. Per-change history lives in
CHANGELOG.md; how to run it lives in README.md; the opt-in /
bring-your-own-key posture lives in DISCLAIMER.md.
┌──────────────────────────────────────────────┐
prompt ───▶│ CLI (tanglebrain) / GUI (tanglebrain-gui) │
└──────────────────────────────────────────────┘
│
┌──────────────┴──────────────┐
│ (optional) classifier gate │ trivial ─▶ local tier
└──────────────┬──────────────┘
│ frontier
▼
┌──────────────────────────────────────────────┐
│ Router │
│ selects an orchestrator (task-fit), rotates │
│ across orchestrators, fails over on error │
└──────────────────────────────────────────────┘
│
┌───────────────────────┼───────────────────────────┐
▼ ▼ ▼
openai-compat cli adapter api adapter
(local server) (authenticated CLI) (gated paid backend)
│ │ │
│ local-delegate (MCP) ◀── orchestrator offloads sub-tasks
▼ ▼ ▼
┌──────────────────────────────────────────────┐
│ measurement: append one record per task │
└──────────────────────────────────────────────┘
│
▼
final answer
The roster is a plain YAML list of entries, each describing one routable backend. An entry has
an id, a tier (local / sub / api), an invoke block, and routing hints (good_at,
can_orchestrate). The invoke.kind selects the adapter (openai-compat / cli / api) and
carries kind-specific fields. Credentials are referenced, never embedded: key_ref is a reference
(env:NAME or file:PATH), resolved lazily at call time.
The active roster is auto-discovered so a fresh clone works out of the box and an operator's real
config lives outside the repo (a git pull never clobbers it). Resolution order, first hit wins:
$TANGLEBRAIN_ROSTER(explicit path)~/.config/tanglebrain/roster.yaml(XDG user config)- the packaged example (
tanglebrain/config/roster.yaml)
default_roster_path() implements that order; packaged_roster_path() always points at the bundled
example. The packaged default ships one active entry — the free local tier — with the
subscription-CLI and paid-API tiers present as commented opt-in examples.
Every backend is reached through an adapter exposing one method, run(prompt, opts) -> text, so the
router treats all tiers the same and adding a tier is contained to one adapter. Errors normalize to
AdapterError (adapters/base.py).
openai_compat.py—OpenAICompatAdapter. HTTP POST to any OpenAI-compatible/chat/completionsendpoint (a local server such as Ollama, a self-hosted gateway, etc.). Returns the assistantcontent.cli.py—CliAdapter. Drives an installed, authenticated command-line tool as a subprocess (never via a shell). The prompt is substituted into a{prompt}token in the configuredcmdor appended as the final argument;invoke.parseselects an output parser;invoke.scrub_envstrips named variables from the subprocess environment so the call uses the intended credential path.invoke.delegate_argslets the adapter hand the backend the local-delegate tool (below).api.py—ApiAdapter. A subclass of the openai-compat adapter for paid endpoints (which are themselves OpenAI-compatible). Same transport, different policy: it is built only when the paid gate is on (see below).
selector.build_adapter(entry, ...) is the single factory that maps an entry to its adapter and
enforces the paid gate.
An optional pre-router step that rates a request's complexity on the free local tier and sends
trivial work straight to local, letting frontier work fall through to the router. It is
off by default, toggled by settings.classifier_gate_enabled or per-run --gate / --no-gate,
and fails safe: any error or ambiguity routes to frontier, so a hard task is never trapped on
the local tier.
The router turns one prompt into one answer by choosing among orchestrator backends — entries
flagged can_orchestrate: true. Orchestrators are pluggable and config-driven; the set is
whatever the roster declares.
- Task-fit selection. When a
taskhint is given, the router prefers orchestrators whosegood_atmatches it, falling back to the full set otherwise. - Rotation. It rotates the orchestrator role across the eligible set for resilience and even
load. The rotation cursor is persisted across processes at
~/.cache/tanglebrain/router-state.json(override withTANGLEBRAIN_STATE_DIR) and only advances on success. - Failover. On an
AdapterErrorit fails over to the next orchestrator; if all fail it raisesRouterErrorlisting each failure (rate-limit errors are annotated). - Paid last resort. If every orchestrator fails and the paid gate is on, the router falls
through to enabled
tier: apientries in roster order. This is the genuine last resort; a paid success does not advance the orchestrator rotation cursor.
Router.last_served surfaces the entry that served a request so the CLI can meter it without
changing route()'s return type.
tanglebrain-delegate is an MCP server exposing one tool, delegate_local(prompt, max_tokens?),
that routes to the free local tier. An orchestrator that supports MCP can register it and offload
bulk sub-tasks to the local backend, then review the results — a decompose → delegate → review loop
that is emergent from the orchestrator simply having the tool (no graph engine required). The
delegate reuses the same roster + openai-compat adapter as the rest of the system, so the local
endpoint and its key reference live in exactly one place. MCP is an optional install extra
(pip install -e ".[delegate]").
Each routed task is appended as one JSON line to ~/.cache/tanglebrain/usage.jsonl (honoring
TANGLEBRAIN_STATE_DIR): the path taken, the tier and model that served it, estimated token counts,
and a cloud-equivalent cost figure — what the same work would have cost on a paid frontier API,
using the reference price in config/pricing.yaml. tanglebrain --stats rolls those records up.
Tokens are estimated with a uniform chars/4 heuristic over the visible prompt + response (the
authenticated CLIs expose no usable counts), so one consistent approximate methodology applies to
every tier. All measurement I/O is best-effort: logging never breaks routing, and a corrupt record
never breaks the rollup.
tanglebrain-gui serves a thin, localhost-only web panel (stdlib http.server + a single
vanilla HTML/CSS/JS page, zero extra runtime dependencies). It views the roster, the pricing
reference, and the cost-avoided rollup, and lets you run a prompt through the router. The
pricing card and a focused set of per-entry roster fields (enabled, can_orchestrate,
budget_usd_month, good_at) are editable, with strict validation, an atomic write, a timestamped
backup, and comment-preserving write-back. It binds 127.0.0.1 only — running a prompt spends real
backend quota and the panel reads the roster, so it is never network-exposed. Secrets are never
resolved or sent to the browser: a key_ref is shown as its reference string only.
gui/views.py holds pure, socket-free functions (testable directly); gui/server.py wraps them in
a pure dispatch(method, path, body) plus a ThreadingHTTPServer.
A small global settings file holds two boolean switches, both off by default and both validated strictly (a non-bool value can never coincidentally enable a feature):
api_billing_enabled— the paid-API gate. Atier: apientry parses and is inspectable at all times but is never routable until this is on and the entry's ownenabledflag is on (two independent gates). The durable rule: no paid billing without the explicit toggle.classifier_gate_enabled— the classifier gate described above.
| Console script | Module | Purpose |
|---|---|---|
tanglebrain |
cli.py |
Route a prompt (default), or --local / --model <id> / --gate / --stats. |
tanglebrain-gui |
gui/server.py |
Serve the localhost knob panel. |
tanglebrain-delegate |
mcp_server.py |
Serve the delegate_local MCP tool over stdio. |
- Config-driven, not code-driven. Backends, orchestrators, task-fit hints, and pricing all live in editable config; the code is the routing machinery, the config is the policy.
- Plain Python. No agent-graph framework — the orchestration loop is emergent from giving an orchestrator the delegate tool. A graph library remains an option only if the control flow ever grows genuinely branchy.
- Credentials by reference. No raw secret ever lives in config or in the repo;
key_refpoints at an environment variable or a0600file, resolved lazily at call time. - Fail-safe defaults. The classifier gate and the paid gate are both off by default and fail toward the safe behavior (frontier routing; never billing).