Build a tool in the Conduit app, inspect the version it created, and send that version to the people who should run it.
What this is
The create path: you describe a tool, Conduit generates a version, you open Versions, and you deploy that version to specific people.
Why use this path
Use this when you already know the workflow you want the team to run — a ribbon button in Revit or AutoCAD, or an ACC app in the browser.
If you only need a one-off inside the model you have open, start with Copilot. If your firm’s own agents should do this work, see MCP.
What to type
In the Conduit app, describe the tool in plain language. Include:
- The host: Revit, AutoCAD, or ACC
- Who will run it
- What objects, categories, or views it touches
- What “done” looks like (a highlight, an Excel file, a list of misses)
- What it must never do (write to the model, touch workshared central, rename sheets)
Weak: “Make a Revit tool.”
Strong: “Revit add-in that finds structural columns missing a Fire Rating parameter, highlights them, and exports the list to Excel. Do not write values back to the model.”
Conduit asks follow-up questions before it writes code — parameters, edge cases, your firm’s actual habit. Answer those. That lock is what keeps the first build from being a guess.
What generate does
When you generate, Conduit writes the tool and compiles it in the cloud.
- First version of a new app: 40 credits
- Each later change: 20 credits
This is the step that spends credits. Deploying does not.
Treat the output as generated software: open it, test it on a non-production model or drawing, then decide who else should get it.
What you get:
- Revit — a compiled desktop add-in on the ribbon (Revit 2020–2027)
- AutoCAD — a compiled desktop add-in
- ACC — a hosted app in the browser. Conduit handles hosting and sign-in.
How Versions works
Every generate is its own version. A new generate does not overwrite the last one.
- Open the app.
- Go to Versions.
- Download a code snapshot if you want to inspect it.
- Deploy a specific version to specific people.
To put an older version in someone’s hands, deploy that version to those people.
How to pick people
Creators choose the version and the people. Viewers receive it and run it.
Start with yourself and one or two others. Add more people when you would have emailed a ZIP. Deploy to Revit, AutoCAD, and ACC covers rollout.
What happens next
You have a versioned build in the workspace. You have not rolled it to the whole office. Test it, then expand the list. If the ribbon label, parameter set, or edge case is wrong, generate another version (20 credits) and deploy that one.