Octo for AutoCAD
Octo can write, test on a sample and run the routines that process AutoCAD drawings (DWG files) through Core Console, without opening the interface: PDF, cleanup, attributes, plugins. You approve the plan and each batch; it prepares the script, the result and a report of what failed for human review.
Six concrete deliverables, drawn from the research. In all of them, Octo proposes the approach, writes the script and tests it on a sample before the batch.
Generates one .scr per drawing, because scripts don't accept variables, and a batch that calls Core Console file by file, with parallelism limited by the number of cores. Uses -PLOT, whose prompts are in the Autodesk help, and checks the sequence on your version.
Runs -PURGE twice, AUDIT with fixes and saves, on every DWG in the subfolders, or saves to an older version when needed. Leaves a log next to each file. Since it overwrites, it only runs after the backup.
Writes an AutoLISP routine that runs in Core Console, opens the drawing without saving and writes a CSV per file (file, layout, block, handle, tag, value); then merges them all into one. If you need the actual name of a dynamic block, it lets you know and proposes the COM path (Windows automation).
Deliverable: .lsp + .scr + consolidated CSVWhen the rule is complex, it writes a C# plugin that references only the AutoCAD core, to load in Core Console with NETLOAD. Uses .NET 8 from AutoCAD 2025 on and .NET Framework 4.8 up to 2024. For many files in one process, it reads the DWG without opening it as a document.
Controls an invisible instance of full AutoCAD, on a Windows desktop, from Python or PowerShell. Handles call rejections when AutoCAD is busy, with retries, and prefers object model methods over sending commands as text.
Deliverable: .py (pywin32) + .ps1With no Windows or AutoCAD at the company, the same kind of routine (.scr, LISP, .NET, ObjectARX) runs in Design Automation, part of Autodesk Platform Services (APS), and is called from a Linux server. Octo compares the paths and proposes the migration when it pays off.
The same Octo cycle, applied to AutoCAD. Each arm has a narrow role; the decisions are made by a person at your company.
How many DWGs, which AutoCAD version and which verticals are installed (Civil 3D, Architecture…), whether the drawings open in Model or in a Layout. Runs Core Console with no arguments to read the options for your version.
The CSV columns, the name of each PDF, where each log goes. If the redirected log comes in UTF-16, it reads it in that encoding.
Reads the end-user license agreement (EULA) or the company agreement before any server use. Prefers adding the folder to TRUSTEDPATHS over turning off SECURELOAD, and isolates the console so it doesn't change the everyday AutoCAD.
Core Console when possible; acad.exe /b when the command requires the interface; COM when the actual block name is needed; the cloud when there's no Windows. Sizes parallelism by cores and memory.
Script with FILEDIA 0, English commands with _. and a blank line at the end; LISP with no COM functions; plugin with the core only. Every command prompt has an answer, so the console doesn't hang.
Runs a few drawings, with /readonly for extraction, and checks the result: the PDF exists and opens, the CSV has the rows, the log has no errors. Doesn't take the exit code as proof.
With your OK and the backup done, it runs the whole folder and checks file by file what came out and what failed, without taking a success message as proof.
Version, paths, the prompt sequence on your installation and what was confirmed on your machine. The next batch starts ready.
Nothing runs in batch before your OK. Nothing is overwritten without a backup.
The criteria Octo uses to choose. Core Console first; the interface only when there's no other way.
| Task | Recommended path | Alternative |
|---|---|---|
| Purge, audit or save to an older version across hundreds of DWGs | Core Console + .scr | acad.exe /b |
| Export PDFs in batch | Core Console + .scr (-PLOT) | COM Plot.PlotToFile; PUBLISH with .dsd (acad.exe /pl) |
| Extract attributes, text and layers to CSV | Core Console + plain AutoLISP | COM (Python) if you need a dynamic block's EffectiveName |
| Complex logic, validation, generating geometry | .NET plugin (AcCore/AcDb) in Core Console | ObjectARX CRX |
| Read and write DWG without opening a document, many files in one process | .NET or ObjectARX with a side database (ReadDwgFile) | — |
| Orchestrate from Python or PowerShell on a Windows desktop | COM/ActiveX | Launch accoreconsole.exe per process (better for batches) |
Command that requires the interface, Express Tools, vla-* | acad.exe /b | COM |
| Custom objects, maximum performance | ObjectARX | — |
| Linux server, no Windows | APS Design Automation | Windows VM with Core Console |
| macOS | AutoLISP and scripts in AutoCAD for Mac | ObjectARX for Mac |
Three steps. Each one only makes sense after the previous one has shown results in your operation.
A proposal, not a promise
On a Windows machine with AutoCAD, you ask in business terms and get the finished batch.
.scr + batchThe batch is no longer requested; it runs on its own, in the scheduler, over a watched folder.
The same routines in Autodesk's Design Automation, called by API, with no local Windows or AutoCAD.
Each point below has a source published by the vendor, the project or the responsible agency. The sources are in the next section.
4
points with a published source, each with its reference alongside.
vla-*, vlax-* and vlr-* functions don't work; LISP has to use entget, ssget, command.Source: Autodesk Developer Network (ADN) blogOcto prepares everything, but doesn't sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and generates the documents: spreadsheets, reports, drawings and drafts.
Deliverable: material ready to checkThe licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.
Step: review by the signerOcto does not sign. Designs, technical reports, ART/RRT (Brazil's professional responsibility records), accountability reports and any official document are still signed by the company's or agency's licensed professional: here, the designer or the engineer responsible for the project.
Sign-off: designer or responsible engineerAutodesk documentation used on this page, accessed on October 28, 2026.
The assessment starts by reading your DWG folder and your installation, without changing anything. You get a map of what can be automated and decide with it in hand.