Skip to content
The Brain Products Workbench
Sub-productLiveFree

Workbench

A free bench of tools for getting more out of AI models — count tokens, plan caching, route models, cut waste, wherever you build.

Entry vitalsProduct · Sub-product
Status
LiveAt /workbench
Tools
~20all free in-browser
Reach
3 waysbrowser · connector · embed
To run
Freeown key for model steps
Source · repo + live catalogueSynced 2026-07-04
The whole machine

Anatomy & connections

Everything inside the bench, and every thread tying it to the rest of the platform. Click any piece to read what it does.

Loading diagram
Tap a pieceClick a group to open it, or hover any piece to read what it does.
Live on turntwo.devOpen 19 Token & cost tools in the Toolbox
Read the entry
00

In one breath

Workbench is TurnTwo's free toolkit for getting more out of AI models. It answers the questions you can't eyeball — how many tokens is this, what will it cost, which model fits, where is a prompt wasting money — with tools that run right in the browser, no signup for the free ones.

Most tools are pure logic and free. A few add an optional step that calls a model, and those run on your own key — never the owner's. It's a way to meet the practice, not a paywalled product.

01

What it is

The tools

Around twenty tools, grouped by the job they do. The diagram above walks the whole bench — this is the plain-language version.

02

Why it's built this way

The reasoning

This is the layer a normal encyclopedia never gives you: not just what Workbench is, but the decisions that shaped it and the reasons behind each one.

The load-bearing principle · zero-subsidization
The owner never fronts model cost. Ever.
That single rule decides everything else: the free bench can only hold tools that cost nothing to run, and anything that calls a model must run on the visitor's own key.
03

How it actually works

The mechanism

The mechanism, told the way a public exhibit is allowed to tell it. Where a detail crosses into spend or provider specifics, the trail stops at a seam — that material lives only in the private brain.

A
One toolkit, three reaches
A single toolkit of logic is exposed to the browser tools, the connector, and the embeds alike. Build once; surface everywhere.
04

What's missing — and how it gets better

The honest gap log

The candid part. A wiki earns trust by being clear about what isn't here yet — this is the layer that makes it a true reference rather than a brochure.

next
Build-your-own tool composer
Let people wire their own tool from the free primitives, save it, and share it. The plumbing exists; the composer doesn't.
High · reach
open
Saved workspaces across surfaces
A prompt you tuned in the browser doesn't follow you into the connector or an embed. State is per-surface; it should sync to the account.
Med · retention
Wiki on the wiki

About this entry

This wiki documents its own construction. Here is the what, why, and how of the entry you just read — the same treatment we give every subject.

What this is

An instrumented entry, not a page. Every subject opens with a live vitals readout and a diagram of the whole machine, then four sections — what, why, how, and the honest gap log — each expandable from a skim to the full reasoning.

This is the public exhibit. The unredacted cockpit is a separate, sign-in-only surface that never ships a byte to this one.

Why it works this way

Depth is the reader’s choice.A skim gives the gist in a minute; “Go deeper” adds the decisions, the mechanism, the open threads.

Default-deny keeps it safe.Anything sensitive never enters this build — you see where the trail stops, never what’s behind it.

How it stays true

It maintains itself. A librarian process reads the live sources on a schedule, updates the brain, and republishes — so vitals reflect the system as it is.

The graph is earned. Connections come from real cross-references between subjects, not a hand-drawn diagram that drifts.