Why Own a Harness When Five Already Work

The Question That Has to Be Answered First

A family that already talks to models through several vendor harnesses does not need another window. Those products already run a loop, already call tools, already keep a transcript, already ask before a dangerous command. If Firebrand were a prettier launcher over the same sessions, it would be a waste of a year.

The Firebrand Mac app: a native window over the same engine, with the session, a projector, and a terminal — not a second loop. — The window is a projector. The engine is still the loop underneath.

The founding refusal is blunt. If we were going to be vendor-dependent, why build it? The vendor harnesses already work. Reinventing their window is not a product. Owning the loop, the tools, the record, and the permission decision is.

Two Jobs, Neither Optional

The first job is ownership without vendor gravity. A frontier harness is allowed to change its wire, its login, its pricing, or its shutdown date. That is their right. It is a bad place to keep the only copy of how the family delegates coding work. Firebrand keeps an attachment point that still boots when the only reachable model is a local daemon with no account at all.

The second job is a laboratory. Using a harness teaches you how to type at one. Building one teaches you what a step is, what a cut is, what a permission unit is, and what happens when a small model emits a tool call that is not actually a tool call. Those questions have no answer you can rent.

A launcher inherits someone else's loop. An engine owns its own. The test is simple: if the vendor product disappeared tomorrow, could you still run a turn against a workspace and prove what happened? If the answer needs their client, you built a bookmark.

What This Quest Will Not Do

It will not teach you to beat those vendor products, or to stop using them. They remain the canonical homes of their own brains. Firebrand exists so the family can attach models that are not harness-bound, and so the family can measure harness ideas instead of only consuming them.

Code

The charter in one contrast·text

VENDOR HARNESS          FIREBRAND
---------------        -----------------
Their loop             Our loop
Their tools            Our tools
Their transcript       Our append-only record
Their account          A leg: endpoint + auth + dialect
Their client           Optional projector over the same engine

If the left column vanished, the right column still has to
complete a turn on a machine that has never logged into a vendor.

Exercise

List every coding harness you used this month. For each one, write one sentence naming who owns the loop, who owns the transcript, and what still works if that vendor's client is uninstalled. If every row dies without the vendor client, you have measured why an owned engine is a different object.

Hint

The useful column is not 'which model.' It is 'which process still exists after I delete their app.'

The Question That Has to Be Answered First

Two Jobs, Neither Optional

What This Quest Will Not Do

Code

External links

Exercise

Progress

Comments 0