AI harnesses

Books matched to this capability.

5books in this track

L01 · User

Who is affectedOnly you
T20-L01

Same Model, Different Harness: See What the Program Around the AI Changes

What an AI harness is, seen through three real runs of one bug fix: same model, same task, three harnesses, different steps and costs. Then add a run of your own in OpenCode.

Outcome: A four-row comparison table (three given runs plus your own OpenCode run) with result, minutes and step counts, one sentence naming the biggest difference, and three lines for your own task: the task, a check the agent cannot see, and two measures.

User12 minLast edited: Sep 30, 2026

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure
T20-L02

Choose a Harness by Testing It on Five of Your Own Tasks

Run DeepSeek Harness next to OpenCode on the same free model, test both on five tasks from your own work with answers kept away from the agent, and write a recommendation your group can check.

Outcome: A ten-row table (five tasks x two harnesses: known answer, minutes, three habits) and a recommendation of at most five lines naming the pick, the deciding score, the habit that mattered, what the test did not cover and when to test again.

Power user15 minLast edited: Sep 30, 2026

L03 · Builder

Who is affectedColleagues depend on something you built
T20-L03

Run a Harness on a Model You Control: Local Server or Team Gateway

Connect OpenCode and DeepSeek Harness to a local model server or a team gateway, set the four values that must match, and test whether a model can act as an agent before colleagues rely on it.

Outcome: A half-page set-up guide: approved model and where it runs, the four values per harness, the practice task result (2.000) per harness, and one provoked failure with how each harness reported it.

Builder18 minLast edited: Sep 30, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop
T20-L04

Set Up a Harness So a Mistake Stays Small: Container, Rules, Keys and Network

Keep an unattended coding agent small with four layers: a container that sees only the project, a network that reaches only the model gateway, a narrow expiring key, and harness rules for honest mistakes. Includes a five-action safety probe.

Outcome: The four promises with their layers, the two probe rows (before and after), and the practice task result in the final set-up. Passes when the after-row shows internet and writing outside blocked, no promise depends on a harness rule alone, the key expires and is limited to one model, and a colleague can rerun the probe.

Integrator20 minLast edited: Sep 30, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving
T20-L05

Run Coding Agents for a Team: Shared Rules, a Test Set, Nightly Jobs and No Lock-In

Turn single-person coding-agent set-ups into a team routine: one AGENTS.md every harness reads, a test set that defines done, a nightly CI job that fails loudly, and harness, model and gateway as separate settings.

Outcome: House rules with their checks, the four-row run table, links to one passing and one deliberately failed workflow run, and the operator log. Passes when every rule has a check, the job fails on a broken rule even if the agent reports success, harness/model/gateway are single settings, and the log names the next test-set date.

Operator20 minLast edited: Sep 30, 2026