ULTRA com Jarvis no ar·50% off nos 3 primeiros meses em qualquer plano·cupom DESCONTO50 aplicado automático
features· execution intelligence

Harness — the right task with the right agent on the right model

Right task, right agent, right model — you don't burn expensive model tokens on mechanical work.

what it is

The house thesis: the model isn't the ceiling

The Harness is the complete execution bundle for a task: agent + skills + CLI + model + effort — chosen by the type of the task, not fixed per agent. The same model delivers more or less depending on how it's used; that's why Overclock assembles the harness per task: mechanical work runs on a cheap model with low effort, dense reasoning runs on a strong model with high effort.

That's where the product's cost axis comes from: you don't burn expensive model tokens on mechanical work — and you don't hand a hard task to a weak setup. Resolution is deterministic, by a precedence chain: what the squad's roster sets beats the invocation argument, which beats the catalog default.

how to use it

How to use it

State the task

in an agentic mission, intake asks what you want; with a recipe, almost everything already comes answered.

The harness assembles itself

the right agent, the right model, the right effort, and skills cleared by the gate — automatically.

Fine-tune if you want

in a squad, every agent on the roster accepts its own CLI, model, and effort; the rest follows the precedence chain.

features in the area

What this area has today

Bundle by task typeshipped

Agent + skills + CLI + model + effort chosen by the TYPE of the task — not fixed per agent.

Precedence chainshipped

Roster beats invoke, invoke beats the catalog default — for CLI, model, and effort. Deterministic.

Skill gatesshipped

Allowed skills per agent, enforced by a hook on spawn — real enforcement, not instruction.

Effort per invocationshipped

From minimal to xhigh — how hard the agent thinks is a per-task dial, not a constant.

Recipesshipped

Ready-made harness formations for recurring goals — with autofill in Agentic mode.

Status straight from the product's brain: shipped = actually in use; partial = exists, with documented limits.

ready to run

Stop juggling windows. Start shipping in parallel.