Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
Drive Rhino 3D from Claude — designs in one call
Cohesive360 exposes Rhinoceros 3D — running on your own Windows PC — to Claude through 137 atomic primitives + 165 skill recipes + 17 parametric design templates. ONE-CALL builders for solitaires, halos, three-stones, wedding/eternity bands, men's beveled+signet rings, pendants, earrings, chains, bracelets. Skills wrap multi-step moves ("add pavé along curve", "apply hammered finish"). Primitives expose the full Rhino modeling kit. Designs in ONE call instead of ~20 — ~10× faster, deterministic proportions.
ONE-CALL parametric jewelry CAD
17 parametric design templates (solitaire / halo / three-stone / wedding+eternity bands / men's beveled+signet / cross / heart / letter pendants / stud+hoop earrings / cable+cuban chains / bangle+tennis bracelets). Each one a single Claude prompt instead of ~20 manual operations.
165 skill recipes + 137 atomic primitives
Skills wrap higher-level moves ("add three-stone setting", "build pavé along curve"); primitives expose Rhino's modeling toolkit (booleans, sweeps, lofts, fillets, mesh polish, render presets). Pick the abstraction level your prompt needs.
Local bridge — your Windows PC owns the file
Claude talks to a bridge agent running on your Rhino-licensed Windows machine. Designs, geometry, and renders stay on your hardware; we only transit commands + return metadata. No cloud Rhino licensing required.
Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.
Capabilities
0 workflow areas in Solo plan. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Limits and roadmap
What the Rhino 3Dconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- Cloud Rhino / Rhino.Compute. The connector targets Rhino running locally via the bridge agent. Rhino.Compute (McNeel's cloud Rhino) has a separate API surface and is not yet wired.
- GH / Grasshopper definitions. Grasshopper visual programming has its own surface. The connector targets the Rhino document directly. Driving Grasshopper definitions is on the roadmap.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Non-Windows hosts. The bridge agent is Windows-only today (matches McNeel's primary platform). Mac Rhino support requires platform-specific install scripts; tracked on the roadmap.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
Bridge runs on your PC — files never leave
The Rhino Bridge Agent runs locally on your Windows machine. Claude sends commands to it via your bridge URL; geometry and Rhino files stay on your hardware. We only transit operation parameters + metadata responses.
Shared-secret bridge token in encrypted vault
Your bridge URL + API token are stored AES-256-GCM encrypted, master key in Azure Key Vault, AAD bound to your user ID. Token is the bridge's authentication — rotate from the agent CLI any time.
Bridge reachability is your call
LAN-only access via http://your-pc.local:7780 means the bridge can ONLY be reached from your local network. Internet exposure (ngrok, cloudflared, Tailscale Funnel) is optional and printed at agent install time so you opt in deliberately.
Undo / Redo + snapshots
Every Claude-driven operation is undoable via Rhino's native undo stack. The connector also supports document snapshots — capture state before a complex operation, restore if the result isn't what you wanted.
What Rhino 3D via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your Rhino 3Dtenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.