Harness Overview
One typed contract for every way into Wrengler — the panel, Rhino commands and the assistant — behind one gate.
Every action in Wrengler is a named, typed command. Pressing a button in the panel, typing a Wrengler command at the Rhino prompt, and a program the assistant sends all go through the same checks and reach the same code. We call this the harness.
Two things follow. The assistant can't do anything the panel can't. And a result means the same thing whoever asked for it: a study the assistant reads was run by the same code as the heatmap you see in the panel.
Preview. The parts that act in Rhino (host programs and deletes with approval) are built and tested, and still awaiting sign-off in a live Rhino session.
The three layers
Commands. The panel and the plug-in talk in commands whose requests and replies are generated from one shared definition, so the two sides can't drift apart unnoticed. A command the plug-in doesn't know is refused with a message, never silently ignored.
Host programs. How the assistant acts in Rhino. A program is a short list of typed steps drawn from a fixed vocabulary of eight operations. The assistant never writes code.
Goals. Agents that work through a project's studies, documents, conversations and notes toward a goal you set in the chat. They only read, on the platform, as you: they never act in Rhino, so they don't pass this gate at all.
One gate
Before any command runs, the plug-in asks the same questions: are you signed in, and does your plan
include this? Commands typed at the Rhino prompt, like WrenglerSunlight, pass the same checks.
| Who calls | What it can reach | Waits for your approval |
|---|---|---|
| The panel | Every command, including the studies | No, because you pressed the button |
| Rhino commands | WrenglerSunlight, WrenglerView, WrenglerRadiation | No, because you typed them |
| The assistant | Eight host operations: read, select, measure, colour, hide or show, filter, delete | Deletes |
What never happens
- The assistant never writes code. No Python, RhinoScript or C# is generated or run. It can only combine the operations the plug-in lists.
- Nothing is deleted without you. A delete is highlighted in Rhino first and runs only when you press Approve.
- Goals never change anything. They read the project's data and post an answer. They don't touch your model, your files or your tags.
- Every change is one undo step. Whatever a program changes, one Ctrl+Z in Rhino takes it back.
- Your geometry stays on your machine. What goes to the server is a short factual summary (file name, units, site, selection counts and areas, group and layer names) and the numbers a step measured, such as an area or a count. Object ids can travel with a program's results so a later step can use them. The geometry itself never leaves.
Every run leaves a record
Assistant turns can be recorded on the project's Activity tab, next to Chat and Data. Each run shows its route, model tier, whether it took the fast path, its status, duration, tokens and estimated cost. Open a run to see its steps: Triage, Gather, Fast path, Answer, Program sent, Host result, Continuation and Error.
A project's leads see every run on it; everyone else sees their own. Runs are kept for 30 days. Recording is switched on per deployment, so if the tab says No assistant runs yet, recording may be off.
A goal keeps its own log: its card in the conversation shows every part, every read and what it spent. See Goals.
Plans
The assistant, host programs and goals come with Wrengler Pro. On Free, the panel and the Rhino commands work for Sunlight studies. See pricing.
Related
- Host Programs: the operations, the checks, and approval.
- Goals: set a goal, and agents work through the project's data.
- Architecture: the bridge between the panel and Rhino.