VitruAI + AutoCAD
The AI AutoCAD drafting agent installs as a signed AutoCAD plug-in that reads and writes block references, layers, xrefs, layouts, and AutoLISP routines through the ObjectARX .NET API for AutoCAD 2023, 2024, 2025, and 2026 on Windows. It is currently shipping with 1–3 design partners on permit-drawing and electrical-detailed-design DWG workflows.
- Native DWG access for block references, layer standards, xrefs, paper-space layouts, and title blocks through the ObjectARX .NET API, without DXF exports or manual scripting.
- AutoLISP-compatible execution that calls existing firm LISP routines as named commands so agents extend, not replace, the standards library you already maintain.
- DWG-in to permit-ready DWG-out for high-volume FTTH, electrical HV/LV, and mechanical schematic detailed-design workflows, aligned with downstream Bluebeam review and markup.
Install, requirements, and what runs through the integration.
-
Install in ~30 minutes
Drop the signed plug-in into AutoCAD’s per-user or shared plug-in folder, restart AutoCAD, and pair it with the workspace token your VitruAI admin issued. The installer registers commands for the ai autocad drafting agent and validates the EV-signed DLL before load. Typical firms complete rollout across 5–20 drafting seats in ~30 minutes, including a smoke test on a sample FTTH or electrical DWG.
-
AutoCAD 2023, 2024, 2025, 2026 on Windows
The integration targets full AutoCAD 2023, 2024, 2025, and 2026 on Windows through the ObjectARX .NET API, with 64-bit support only. AutoCAD LT is excluded because it does not expose the .NET API surface required for block, xref, and layout automation. AutoCAD for Mac is not supported; firms standardise on Windows workstations for these DWG automation runs.
-
Calls your existing firm AutoLISP routines
On load, the plug-in inspects the search path for `acad.lsp` and `acaddoc.lsp`, then registers tagged routines as callable building blocks. The agent calls those routines as named commands, so your existing block-insertion, layer-creation, and annotation tools stay in control. This keeps firm standards intact while the agent automates higher-level tasks like FTTH permit layouts and electrical detailed design from a washed base.
-
Layer-standards and plotting aware
The integration reads your CTB or STB plot styles, layer templates, and any DWG standards (DWS) you reference for QA. Agents create and modify geometry only on approved layers, with colour, line-type, and plot-weight rules respected for both model space and paper space. This keeps DWG output consistent with your existing plotting workflows and downstream Revit integration or Document AI Agent checks.
-
DWG-in, detailed-design DWG-out for permit workflows
The plug-in receives a source DWG (or xref stack), runs the configured agent, and writes back a new DWG or layout set for permit-ready deliverables. Typical use cases include FTTH trench and duct layouts and electrical HV/LV asset placement, aligned with the AutoCAD permit drawing generation pattern. Output is calibrated per deployment and can be validated against PDFs processed through the Document AI Agent.
-
Network and data residency controls
The AutoCAD plug-in initiates outbound HTTPS calls only, to a single fully qualified domain name and IP range that your IT team can pin in firewall rules. Tenant regions are currently eu-central or me-central, selected at workspace creation to align with your data residency policy. This matches the same control surface used by the Revit integration and supports joint deployments with Bluebeam review pipelines.
AutoCAD integration questions from drafters and CAD managers
-
Does this work with AutoCAD LT?
No, the integration requires full AutoCAD because it depends on the ObjectARX .NET API, which AutoCAD LT does not expose. Without that API surface, the agent cannot inspect block references, xrefs, or layouts or call into your AutoLISP routines. Firms that currently use LT for redlines typically keep LT for markup and run the agent on full AutoCAD seats for DWG generation.
-
Will it overwrite our firm’s AutoLISP standards?
The plug-in does not overwrite `acad.lsp`, `acaddoc.lsp`, or any existing LISP files; it reads them and calls registered routines as named commands. Your existing block library loaders, layer-setup tools, and annotation helpers continue to run unchanged, and the agent treats them as primitives. This keeps your standards library as the source of truth while the agent automates workflows like AutoCAD permit drawing generation and electrical detailed design.
-
Does it work on AutoCAD verticals (Civil 3D, Electrical, Plant 3D)?
The integration runs on verticals installed on AutoCAD 2023+ as long as the base AutoCAD environment and ObjectARX .NET API are present. Today it treats Civil 3D, Electrical, and Plant 3D objects as standard AutoCAD entities unless a vertical-specific profile is configured. Vertical-specific object-class support is available now as Labs engagements per vertical, similar to the pattern used for electrical detailed design autodraft.
-
How does this differ from the Revit integration?
The AutoCAD integration drives DWG automation through the ObjectARX .NET API and AutoLISP, focusing on block libraries, layers, and xref hygiene. The Revit integration works through the Revit API, acting on Families, parameters, and workshared models instead of DWG entities. Many firms run both: AutoCAD for FTTH and 2D electrical permit sets, Revit for building models that later round-trip through Bluebeam and the Document AI Agent for QA.
-
Is this AI AutoCAD drafting agent suitable for one-shot permit drawing batches?
Yes, the integration was shaped around one-shot and repeat permit drawing batches where you start from a washed base DWG and need consistent, permit-ready output. The AutoCAD permit drawing generation pattern covers FTTH and electrical runs in the $1K–$15K fixed-budget range. For ongoing HV/LV asset placement on infrastructure and building projects, firms pair it with the electrical detailed design autodraft workflow under the same AutoCAD plug-in.