Generate parametric geometry workflows with an agent
AI Agentic Generation of Parametric Geometry Workflows. Task: AI Agentic Generation of Parametric Geometry Workflows Personal project · Prototype 1 · Work in progressExperimental. Not yet validated for general use. Provided as is. More will follow. A project by Miro Bannwart Short Introduction Watch on YouTube Full Introduction Detailed walkthrough to follow An idea becomesa workflow. GrassLobster connects the parametric world of Rhino and Grasshopper with an external AI agent of your choice. Describe your idea, shape it together, and keep changing the result. From intention to geometry What GrassLobsterDoes Imagine describing what you want to make — and getting a workflow you can keep changing. Building a parametric definition can take longer than exploring the idea itself. GrassLobster brings an AI agent into that work: from the first brief to a connected Grasshopper model. Start with an idea, not a perfect prompt Describe a building form, a timber structure or a pattern of elements. Your external agent asks about dimensions, rules, materials and what you want to control. It guides you through the decisions until the task is clear enough to build. Build the rules. Keep exploring. Once the approach is agreed, the agent builds the parametric workflow. Change the span, spacing or number of elements, and the related geometry updates. Ask for another variation or develop the project further. The value goes beyond executing CAD commands: you keep the logic that generates the geometry. The result can work like a small design tool made for your particular task. Start with the Rhino model you have The agent can inspect selected objects, create or revise supported Rhino geometry, and use existing geometry as the starting point for the next step. You can work directly in Rhino, then make the parts that need ongoing control parametric through connected Geometry Stations. Bring selected geometry into a BIM workflow Experimental BIM/IFC tools can organise building elements and export IFC for review. Selected 3DM, DXF and DWG geometry can also enter or leave the project through dedicated tools. Inspect the geometry and exported data in the applications used for your project. Keep a growing model manageable Control which Geometry Stations are visible and which are calculating, locally or across the project. Save named visibility, calculation and scheduling states to return to a useful working setup. These states store operating settings, not geometry or design alternatives. Your agent. Your design decisions. Work through a compatible external agent of your choice. It handles the implementation while you review the geometry and guide the design. The model stays visible and adjustable in Grasshopper. The architecture How It WorksBehind the Scenes The geometric process stays visible to you. The same process is mirrored as text for the agent. Geometry Stations on the canvas GrassLobster Session Components organise the model into connected Geometry Stations. Each Station runs the code for a meaningful task. You see the sequence and dependencies without following every individual operation. A project might move through inputs, primary geometry, structural logic, secondary geometry and output. The structure follows the task. GrassLobster hides implementation complexity, not geometric logic. Mirrored logic and inputs Station definitions and executable code are mirrored in readable project files. The agent can locate the relevant logic, understand connected Stations and make targeted changes through the supported workflow. Supported input values are mirrored too. Dimensions, counts or spacing can be changed without rewriting the Station code; Grasshopper recalculates the related geometry. A folder with project context Agent Instructions guide how the agent asks questions and works with you. Domain knowledge adds prepared subject guidance, your own standards or material notes. Geometric references communicate shape through screenshots, studies or example models. References can come from chat or designated project folders. What the agent can use depends on its tools and the file format. This is project context, not an automatically indexed knowledge system. Direct Rhino work and live references; tools: custom-built or unnamed agent. Human role: The original post does not say how a person stayed involved.; limitations: Prerequisites include Rhino 8.30+, .NET 8, and a compatible coding agent with file access. IFC export is experimental; tested sphere Breps failed to reimport despite passing schema checks. MCP is optional; file-based workflows are sufficient. Human approval is required for all geometry changes and exports. Costs for agent subscriptions and image tools must be budgeted separately..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
AI Agentic Generation of Parametric Geometry Workflows
Workflow
AI Agentic Generation of Parametric Geometry Workflows Personal project · Prototype 1 · Work in progressExperimental. Not yet validated for general use. Provided as is. More will follow. A project by Miro Bannwart Short Introduction Watch on YouTube Full Introduction Detailed walkthrough to follow An idea becomesa workflow. GrassLobster connects the parametric world of Rhino and Grasshopper with an external AI agent of your choice. Describe your idea, shape it together, and keep changing the result. From intention to geometry What GrassLobsterDoes Imagine describing what you want to make — and getting a workflow you can keep changing. Building a parametric definition can take longer than exploring the idea itself. GrassLobster brings an AI agent into that work: from the first brief to a connected Grasshopper model. Start with an idea, not a perfect prompt Describe a building form, a timber structure or a pattern of elements. Your external agent asks about dimensions, rules, materials and what you want to control. It guides you through the decisions until the task is clear enough to build. Build the rules. Keep exploring. Once the approach is agreed, the agent builds the parametric workflow. Change the span, spacing or number of elements, and the related geometry updates. Ask for another variation or develop the project further. The value goes beyond executing CAD commands: you keep the logic that generates the geometry. The result can work like a small design tool made for your particular task. Start with the Rhino model you have The agent can inspect selected objects, create or revise supported Rhino geometry, and use existing geometry as the starting point for the next step. You can work directly in Rhino, then make the parts that need ongoing control parametric through connected Geometry Stations. Bring selected geometry into a BIM workflow Experimental BIM/IFC tools can organise building elements and export IFC for review. Selected 3DM, DXF and DWG geometry can also enter or leave the project through dedicated tools. Inspect the geometry and exported data in the applications used for your project. Keep a growing model manageable Control which Geometry Stations are visible and which are calculating, locally or across the project. Save named visibility, calculation and scheduling states to return to a useful working setup. These states store operating settings, not geometry or design alternatives. Your agent. Your design decisions. Work through a compatible external agent of your choice. It handles the implementation while you review the geometry and guide the design. The model stays visible and adjustable in Grasshopper. The architecture How It WorksBehind the Scenes The geometric process stays visible to you. The same process is mirrored as text for the agent. Geometry Stations on the canvas GrassLobster Session Components organise the model into connected Geometry Stations. Each Station runs the code for a meaningful task. You see the sequence and dependencies without following every individual operation. A project might move through inputs, primary geometry, structural logic, secondary geometry and output. The structure follows the task. GrassLobster hides implementation complexity, not geometric logic. Mirrored logic and inputs Station definitions and executable code are mirrored in readable project files. The agent can locate the relevant logic, understand connected Stations and make targeted changes through the supported workflow. Supported input values are mirrored too. Dimensions, counts or spacing can be changed without rewriting the Station code; Grasshopper recalculates the related geometry. A folder with project context Agent Instructions guide how the agent asks questions and works with you. Domain knowledge adds prepared subject guidance, your own standards or material notes. Geometric references communicate shape through screenshots, studies or example models. References can come from chat or designated project folders. What the agent can use depends on its tools and the file format. This is project context, not an automatically indexed knowledge system. Direct Rhino work and live references
Reported result
Actual outcomes are not fully validated for general use as the project is an experimental prototype. The author reports that strong reasoning models (e.g., GPT-6 Astra) produce better geometry than weaker ones. A potential direction is agentic optimization where inputs are varied to meet measurable goals, but this is not yet a built-in general-purpose optimizer.
Human role
The original post does not say how a person stayed involved.
Limitations
Prerequisites include Rhino 8.30+, .NET 8, and a compatible coding agent with file access. IFC export is experimental; tested sphere Breps failed to reimport despite passing schema checks. MCP is optional; file-based workflows are sufficient. Human approval is required for all geometry changes and exports. Costs for agent subscriptions and image tools must be budgeted separately.
Try it
I want to test GrassLobster with my current Rhino project. I have installed GrassLobster 0.1.17-alpha and have a compatible coding agent (e.g., Codex or Claude Code) configured with file access to my project folder. My goal is to generate a parametric timber structure workflow from a text description. Please guide me through the following steps: 1. Confirm my Rhino and Grasshopper documents are saved in the project folder and Agent Start is placed. 2. Generate the Agent Start Prompt and paste it into my agent conversation. 3. Ask the agent to read the entry file and confirm the project path. 4. Describe my timber structure idea (e.g., [replaceable: span, spacing, material]) and let the agent ask clarifying questions. 5. Review the generated Geometry Stations in Grasshopper. 6. Change a main parameter (e.g., [replaceable: beam depth]) to verify the geometry updates. 7. If successful, ask the agent to export a small sample to IFC and verify it in an independent viewer. Do not proceed to full modeling until I confirm the sample works. Handle any permission or path errors by checking the folder structure first.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.