Feature Request: Native Support for .DWG / .DXF File Formats — Enabling AI-Assisted Architectural and Engineering Workflows

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

.. I am a retired Chief General Manager (Architecture), Government of India, currently based in Kolkata. As an active Claude Pro subscriber, I use Claude extensively for architectural research and writing — including a biography of Indian architect Jeet Malhotra, who collaborated with Le Corbusier on Chandigarh's Capitol Complex. I also explore agentic AI workflows for heritage documentation and publishing.
The Request Please add native support for .DWG and .DXF file formats — the universal file standards of the built environment — to Claude's supported file types, and consider a dedicated Claude extension for AutoCAD/Revit, analogous to the existing Claude for Excel and Claude for PowerPoint add-ins.
Market Scale AutoCAD and Revit together serve approximately 50 million users worldwide across architecture, engineering, urban planning, construction, and heritage conservation. This is a large, high-value professional segment that is currently entirely underserved by AI assistants.
What This Would Unlock
• Reading and interpreting floor plans, sections, elevations, and site plans
• Extracting spatial data, dimensions, and building element metadata
• Annotating and querying drawings in natural language
• Assisting heritage documentation and conservation analysis
• Laying the groundwork for cost estimation and 3D model generation
None of these capabilities exist in any current mainstream AI assistant. This would be a genuine differentiator for Claude in the AEC (Architecture, Engineering, Construction) sector.
The Gap AutoCAD (.DWG) and DXF are to the built environment what Word and Excel are to office work — foundational, universal, and irreplaceable. Every government infrastructure project, every heritage drawing archive, and every active architectural practice generates files in these formats daily. Claude currently cannot engage with any of them.
My Specific Use Case My ongoing projects — the Jeet Malhotra biography, Chandigarh Capitol Complex documentation, and a comparative study of Palladian architecture's lineage in colonial Kolkata — all involve architectural drawings that I cannot currently share with Claude. This is a direct limitation on what Pro users in the AEC field can achieve.
Vision A Claude extension sitting natively inside AutoCAD — reading drawings, answering queries, generating descriptions, flagging inconsistencies — would be as transformative for architects as Claude for Excel has been for analysts. The plugin architecture already exists. The user base is ready.
I would be happy to participate in any beta testing or user research for this feature.

Proposed Solution

.. Vision A Claude extension sitting natively inside AutoCAD — reading drawings, answering queries, generating descriptions, flagging inconsistencies — would be as transformative for architects as Claude for Excel has been for analysts. The plugin architecture already exists. The user base is ready.
I would be happy to participate in any beta testing or user research for this feature.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

.. None of these capabilities exist in any current mainstream AI assistant. This would be a genuine differentiator for Claude in the AEC (Architecture, Engineering, Construction) sector.

Additional Context

I am a retired Chief General Manager (Architecture), Government of India, currently based in Kolkata. As an active Claude Pro subscriber, I use Claude extensively for architectural research and writing — including a biography of Indian architect Jeet Malhotra, who collaborated with Le Corbusier on Chandigarh's Capitol Complex. I also explore agentic AI workflows for heritage documentation and publishing.
The Request Please add native support for .DWG and .DXF file formats — the universal file standards of the built environment — to Claude's supported file types, and consider a dedicated Claude extension for AutoCAD/Revit, analogous to the existing Claude for Excel and Claude for PowerPoint add-ins.
Market Scale AutoCAD and Revit together serve approximately 50 million users worldwide across architecture, engineering, urban planning, construction, and heritage conservation. This is a large, high-value professional segment that is currently entirely underserved by AI assistants.
What This Would Unlock
• Reading and interpreting floor plans, sections, elevations, and site plans
• Extracting spatial data, dimensions, and building element metadata
• Annotating and querying drawings in natural language
• Assisting heritage documentation and conservation analysis
• Laying the groundwork for cost estimation and 3D model generation
None of these capabilities exists in any current mainstream AI assistant. This would be a genuine differentiator for Claude in the AEC (Architecture, Engineering, Construction) sector.
The Gap AutoCAD (.DWG) and DXF are to the built environment what Word and Excel are to office work — foundational, universal, and irreplaceable. Every government infrastructure project, every heritage drawing archive, and every active architectural practice generates files in these formats daily. Claude currently cannot engage with any of them.
My Specific Use Case My ongoing projects — the Jeet Malhotra biography, Chandigarh Capitol Complex documentation, and a comparative study of Palladian architecture's lineage in colonial Kolkata — all involve architectural drawings that I cannot currently share with Claude. This is a direct limitation on what Pro users in the AEC field can achieve.
Vision A Claude extension sitting natively inside AutoCAD — reading drawings, answering queries, generating descriptions, flagging inconsistencies — would be as transformative for architects as Claude for Excel has been for analysts. The plugin architecture already exists. The user base is ready.
I would be happy to participate in any beta testing or user research for this feature.