Everything Yugmir does, in one place
Beyond publishing and governing tools: a family library, overnight batch runs, importing the tools you already have, and an AI assistant that works on your open model.
A ribbon your firm controls
Publishing a tool means copying it to your shared drive. It reaches the ribbon of the people it is meant for — no installer to reissue, no IT ticket.
Sync without restarting
Users press Sync and the ribbon rebuilds mid-session. Files in use are applied on the next start instead of failing. A report shows what arrived, changed or retired.
Only the tools you need
The Tool Store lets each person subscribe to the sets of tools for their discipline, and roles decide which tools a person may have at all.
Search instead of hunting
Search Tools finds and runs any tool by name. In Revit, star favourites onto your own tab and give any tool a two-letter shortcut.
Start a new tool in a minute
New Tool Project creates the folder, the project and a working command. Build it, press Reload UI, and the button is there.
Publish, then stage
Publish Tool moves a tested tool to the master drive. Release to a Beta group first, then promote — with rollback if something goes wrong. How governance works.
Every tool documented
Tool Guide builds a searchable page of every tool on the machine, your firm’s included, and names the ones nobody has documented yet.
Family Library
Search and load your firm’s families from inside Revit, with previews. The library lives in one database that can sit on a network share, so everyone browses the same content rather than their own copy.
- Previews for everyone. Thumbnails are stored in the library itself, so a library an admin publishes shows previews on every machine.
- No waiting for upgrades. It can keep a copy of each family for every Revit version, and loads the best match for the Revit you are in.
- Only what changed. New and modified families are indexed; unchanged ones are skipped.
- Nothing to set up per person. Publish the library list to the master drive and others pick it up on Sync.
- Filters for the exact Revit version and the project’s units.
Batch Runner — a folder of files, overnight
Tick what to do, pick a folder, and run it now or on a schedule. At the set time Windows starts Revit or AutoCAD, runs the job, e-mails the report and closes again.
Every .rvt in a folder
- Health check: warnings, size, views, sheets, families, imported CAD, links, unplaced rooms
- Open with Audit
- Upgrade and save in this Revit version
- Export sheets to PDF (Revit 2022 and later) and to DWG
- Export IFC
Workshared models are always opened detached, so a batch never locks or overwrites a central file.
Every .dwg in a folder
- Health check: entities, layers, blocks, missing xrefs, proxies, images
- Purge unused layers, blocks, linetypes and styles
- Save, skipping any drawing someone has open
- Export DXF
- Save an AutoCAD 2018 copy for consultants
Drawings are read in the background, never opened on screen, so a run shows no windows or prompts.
Every run writes an HTML report and a CSV. To have it e-mailed, enter your mail server; the password is kept in Windows Credential Manager, never in the job file.
Bring the tools you already have
Import Tools lays an existing collection out as a Yugmir panel in your own development folder. Your original files are never changed, and nothing reaches the firm until you publish.
From pyRevit
Point it at a .extension folder. Every panel, pulldown and button comes across
with its title, tooltip and icon.
- Buttons that run a DLL work straight away
- C# scripts become projects — build and they work
- Python scripts arrive as a button and a project to port them into, with the original script beside it. The AI assistant can do the porting.
From a folder of LISP
Every (defun c:NAME) becomes a button; a file with several commands becomes a
pulldown, and the tooltip comes from the file’s own comments.
- Dialog (.dcl) and data files are copied beside the script and found without a support path
- Library files with no commands are kept and loaded
- A report names every change, and any command two files both define
An AI assistant that knows your model
Yugmir connects AI assistants — Claude Desktop, VS Code, Visual Studio, Cursor, Antigravity, GitHub Copilot CLI, Codex and any other app that supports MCP, the open standard for connecting AI to tools — to your installation and, while Revit or AutoCAD is open, to the model or drawing in front of you. It runs on your own computer, with the AI service your firm already uses — Yugmir hosts no AI model and receives none of what you ask. What that means for your data.
Answers from what is really there
“How healthy is this model?” “Give me the sheet register.” “Concrete volume by level.” “Where is this family used?” Reports are saved as HTML and CSV.
Standards and QA
A health score with its trend, and checks against your firm’s own standards file. In Revit also structural checks, clashes between two categories, and what changed since Monday.
Excel and ETABS
Compare the model with a spreadsheet — or, in Revit, an ETABS export — and fill values from a sheet, with every change shown to you first.
From request to published tool
“Make a tool that renumbers the doors on this level.” It creates the project, writes the code, builds and checks it, draws the icon, and can publish it to Beta.
Which tools to build next
It reads the model’s problems, the tools you already have and what it keeps doing by hand, and proposes tools with the evidence and the effort.
Nothing changes without your Yes
Running a tool, fixing warnings, purging or changing values each wait for you to click Yes in Revit or AutoCAD, and each is one Undo. It can publish only to Beta, only for a Publisher or Admin, and never promotes to Production or deactivates a licence.
An administrator can set the link to On, ReadOnly (looks, never changes) or Off for the whole firm through Group Policy, or switch the AI connection off entirely. The assistant works only on the user’s own computer, and every request is logged.
A tool library without a VPN
The master drive does not have to be a file server. It can be:
A network folder
An ordinary shared folder you already have. Nothing to host.
SharePoint or Teams
A library synced by OneDrive — the simplest route for a Microsoft 365 firm, and publishing still works.
A web library
Any https:// address, such as Azure storage. Each computer keeps a local copy
and works offline, and a damaged download never replaces a working tool.
For IT
- One installer for Revit 2019–2027, or AutoCAD, Advance Steel, Civil 3D and Plant 3D 2021–2027 — or both together
- Silent install with
/VERYSILENT /ALLUSERS, and the master drive on the command line - Group Policy settings win over anything set locally
- Per-user or all-users install; no Active Directory needed
- Works offline. Licensing needs the internet once to activate, then has a grace window
- Your data stays yours. Tools and usage data live on your own server
- Usage data is opt-in, or set for the whole firm — and never includes model or drawing content
- Integrity checks on the tools your firm publishes
See it on your own projects
Fifteen days, the full product for Revit and AutoCAD, no card required.