The design partner in the room
Initializing0%
Always on · Silent by default · Runs on your machine

It watches. It almost never speaks.

MANTIS sits quietly beside you while you model in Grasshopper — reading your canvas the whole time. It stays out of your way until something silently breaks or you get stuck. Then it's already there, with the reason and the one-click fix. A partner in the room, not a box you talk to.

Ask Mantis…
The 20 minutes nobody sees

The pain isn't the question.
It's the silence before it.

Most of the time you lose in Grasshopper isn't the moment you ask for help — it's the twenty minutes a definition is quietly broken and you don't know yet. It turns green, looks fine, and produces nothing — because three components upstream, a wire is feeding the wrong kind of data. Grasshopper doesn't warn you. The AI in the side-panel doesn't know, because you didn't ask. Nobody is actually watching the work with you.

The difference

Not a box you talk to.
A partner in the room.

Every AI tool for Grasshopper — and the old MANTIS too — works the same way: a panel you turn to, type at, and wait on. A good human assistant doesn't wait to be asked. They're in the room, glance over, and say "oh — your loft is empty because that curve isn't closed." Quiet 95% of the time; right when they speak. That's the product.

A day with MANTIS

Quiet, aware, present.

A small dot, breathing

Open Rhino + Grasshopper and a calm green dot appears in the corner. Not a panel demanding attention — more like the light that says something's on and working. It reads your canvas the whole time. You never explain your file. You forget it's there.

Something goes quiet

An hour in, you rewire a cluster. What you don't notice: an output just went empty. The dot shifts — quietly — to amber. No popup, no interruption. You keep working. Maybe you'll catch it. You don't.

One glance, one fix

You're jiggling a slider, confused why nothing updates. You glance at the dot and hover. A small card: "Your panel grid went empty when you rewired Divide. Want me to fix it, or show the plan?" You click Fix. It reconnects on your actual graph — not a rebuild — and shows a receipt: "Fixed. Now produces 96 panels." Fifteen minutes saved.

It remembers

At day's end you close Grasshopper. MANTIS leaves two lines: "Today: parametric façade, 96 panels, verified clean. One fix applied to the Divide cluster." Tomorrow it picks up where you left off.

It didn't forget how to build

And when you do want it to build — it builds.

Ask in plain English and MANTIS stages the graph, then places native, editable Grasshopper components on your canvas — wired and grouped, exactly as an expert would. It reads the result back and heals its own warnings. The same engine that watches is the one that builds.

MANTIS · chat
staging the graph…
→Lofted tower surface → diagrid skin
→14 native components, 3 groups
→Read-back: 24 floors, solid valid
✓Built & verified · 0 warnings
diagrid_tower.gh BUILDING
Drag to orbit
rot x 17° y 0°
1.2
8
12
Build

Describe a design — it plans, then streams grouped native components onto the canvas.

Agent

Acts across Rhino and Grasshopper. Asks before it deletes.

Ask

A conversational answer about GH or your current canvas — explains, doesn't build.

Iterate

Builds on what's there — panelization, thickness, mullions — nothing dropped.

Why only MANTIS can do this

To be in the room, you have to watch all day.

∞

Watching costs them money. It costs us nothing.

Every competitor — Raven, Ant, Reer — runs on metered cloud AI: every look at your model is billed, so they can't afford to watch continuously. MANTIS runs on your key or a local model, where watching is free. The always-on partner is the one shape their pricing forbids them from building.

◴

It learns where people get stuck.

Because MANTIS is the only one actually watching, it sees what no panel can: not what you ask, but where you struggle — silently, before you'd ever ask. Opt-in and anonymous, geometry never shared, that becomes a living map of how to get unstuck. Competitors start that map at zero.

Why it isn't Clippy

Silent by default. Right when it speaks.

Clippy failed because it talked too much and was usually wrong. MANTIS is the opposite by design.

⌁

Earns every interruption

It speaks only when it caught something real and you're genuinely stuck — you tried, it didn't work, you paused. Dismiss it once and it backs off.

✓

Verified before spoken

It reads the real result of your live solve, so "this is empty and here's why" is a fact it machine-checked — not a guess.

↺

Always reversible

Every fix touches your actual graph and is a single Ctrl-Z. Anything destructive asks first.

⌂

Your machine, your model

Local, on your own key or a local model. Your geometry never leaves; only opt-in, anonymous, corroborated lessons do.

⌂

Runs on your machine

The plugin lives in Rhino. Your geometry never leaves unless you send it. No cloud lock-in.

🔑

Your key, or fully local

Bring your own API key, or run a local model with Ollama / Claude CLI. No MANTIS subscription, ever.

↻

Everything is editable

It's a real GH definition — every node Ctrl-Z-able, inspectable, and yours to extend.

Put a partner in the room.

Free, open source, and watching your canvas inside Rhino 8 in two minutes.

Get started
In Rhino command line
_PackageManager → search "MANTIS"