Assistant and goals overview
The panel, Rhino commands and the assistant go through the same checks and reach the same code. What never happens without you, and the record each run leaves.
Built and tested; final checks in live Rhino before general release.
Pressing a button in the panel, typing a Wrengler command at the Rhino prompt, and asking the assistant all go through the same checks and reach the same code.
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.
Three ways in#
The panel and Rhino commands. What you press in the panel or type at the Rhino prompt. A command the plug-in doesn't know is refused with a message, never silently ignored.
The assistant. It answers from the project's data, and in Rhino it acts with a fixed set of Rhino and project actions. It 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.
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 | A fixed set of Rhino and project actions (the assistant in Rhino) | Anything that saves to the project, deletes, and plans with steps in order |
What never happens#
- The assistant never writes code. No Python, RhinoScript or C# is generated or run. It can only use the actions the plug-in offers.
- 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 can be undone. What the assistant changes in the model is an undo step in Rhino: one Ctrl+Z for a plain request.
- Nothing is saved without you. Anything that would save to the project shows a card and waits for Approve.
- 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 the assistant measured, such as an area or a count. Object ids can travel with those results so the assistant can act on the same objects next. The geometry itself never leaves.
Every run leaves a record#
Assistant turns are recorded on the project's Activity tab on the web, next to Chat and Data. Each run shows its status, how long it took and the steps it went through. The record holds timings and the names of the actions, not what you wrote or what it answered.
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 the time taken. See Goals.
Plans#
The assistant, including the assistant in Rhino, and goals come with Wrengler Pro. On Free, the panel and the Rhino commands work for Sunlight studies. See pricing.
Related#
- The project assistant: asking, and what an answer was built from.
- The assistant in Rhino: its actions, and what waits for your approval.
- Goals: set a goal, and agents work through the project's data.
- Architecture: how the panel and Rhino talk.