Onshape AI Advisor: what PTC shipped and what it missed

I was building a sheet metal bracket in Onshape last Tuesday, the kind of part that takes fifteen minutes if you know what you're doing and forty-five minutes if you're fighting the interface. Halfway through a flange bend, a small panel in the corner of my screen offered a suggestion: "Consider using a Flange feature instead of Extrude for sheet metal parts." I stared at it for a second. I was already using the Flange feature. The AI Advisor was telling me to do the thing I was actively doing, with the confidence of someone who walked into a room mid-conversation and decided to summarize what they heard.

That moment captures Onshape AI Advisor pretty well. It's trying to help. It sometimes does. And it has no idea how much you already know.

What PTC actually shipped#

Onshape AI Advisor launched in October 2025 as part of release 1.205. It's built on Amazon Bedrock, which means it's running on AWS infrastructure using a mix of foundation models that PTC selected and tuned against Onshape's own documentation. The advisor sits inside the Onshape interface, available as a chat panel where you can type questions and get responses.

The core pitch: real-time guidance while you model. You're building a part, you hit a wall, you type a question, the advisor gives you an answer sourced from Onshape's official docs, tutorials, and training materials. It doesn't hallucinate from the open internet. It doesn't make up commands that don't exist. It sticks to what's actually in the Onshape knowledge base, which is a design choice that limits creativity but improves reliability.

PTC is careful to note that the AI Advisor does not access your design data. It can't see your model. It can't read your feature tree. It can't inspect your sketches. It only knows what you tell it in the chat window, plus whatever context it can infer from the conversation. That's an important distinction that changes what the tool can and can't do.

Where it's genuinely useful#

For newer Onshape users, especially people migrating from SolidWorks or Fusion 360, the AI Advisor is a decent safety net. Onshape does things differently enough that experienced CAD users still trip over its conventions. The way mates work, the branching and merging model, the Part Studio vs Assembly distinction, the way configurations are set up. These are all things that make sense once you understand them and are bewildering until you do.

I asked the advisor how Onshape's branching model compares to file versioning in traditional CAD. The answer was clear, accurate, and included a link to the relevant documentation. It explained the concept in terms that would make sense to someone coming from a PDM background. For that use case, finding the right documentation page fast, the advisor earns its place.

The FeatureScript guidance is another bright spot. FeatureScript is Onshape's programming language for custom features, and it has a learning curve that makes most people give up before they get anywhere interesting. The advisor can explain FeatureScript concepts, break down example code, and help you understand what a particular function does. It won't write production FeatureScript for you, but it'll get you over the hump of "what does this syntax even mean?" faster than reading the documentation raw. PTC has hinted at FeatureScript autocomplete as a future feature, and honestly, that would be more useful than most of what the advisor currently does.

Where it falls short#

The advisor can't see your model. It has no context about what you're building, what features you've applied, what errors you're hitting, or what the geometry looks like. Every conversation starts from zero. You have to describe your problem in text, which means you're spending time translating a visual, spatial problem into words so that a language model can translate it back into instructions.

I had a sketch that wouldn't fully constrain. In a normal CAD workflow, an experienced colleague would glance at the screen, point at the under-constrained point, and tell me what dimension I'm missing. With the AI Advisor, I had to describe my sketch geometry in words, list the constraints I'd already applied, and ask what might be missing. The advisor gave me a generic checklist of common under-constraint causes. Technically helpful. Practically slower than just staring at the sketch for another thirty seconds.

This is the fundamental limitation of an AI CAD copilot that can't see the CAD. It's like calling tech support and having to describe your screen over the phone. The information barrier means every interaction carries overhead, and that overhead adds up until it's faster to just figure things out yourself.

The advice quality also has a ceiling. For basic workflow questions, the advisor is fine. For nuanced modeling decisions, like whether to use a loft or a sweep for a particular transition, or how to structure a multi-body Part Studio for downstream assembly work, the answers get vague. The advisor defaults to restating what the documentation says, which is accurate but doesn't include the judgment calls that make one approach better than another for your specific situation. It's the difference between "a sweep creates geometry by moving a profile along a path" and "use a sweep here because the cross-section changes and a loft would create a tangency break at the transition." The advisor gives you the first kind of answer.

For Enterprise customers, the AI Advisor is disabled by default and has to be turned on by an admin. If your company has a cautious IT department, which describes most companies large enough to have Enterprise Onshape licenses, you might not have access even though the feature technically exists.

The roadmap promises#

PTC has been public about what's coming: agent workflows that can interact with model metadata, AI-assisted rendering, and eventually automated geometry creation. The geometry creation part is the one that would actually change the game, and it's also the one furthest out on the timeline. I've seen enough roadmap slides turn into five-year plans to stay skeptical until I can click on something.

The FeatureScript autocomplete, if it ships, would be the single most useful AI feature Onshape could add. FeatureScript has enough users who know enough to be dangerous but not enough to be productive, and code completion with context awareness would lower the barrier meaningfully. That's the kind of AI assistance that saves actual time on actual work, rather than saving ten seconds on a documentation lookup.

How it compares#

Against SolidWorks AURA, the Onshape AI Advisor has a similar scope: documentation lookups, workflow guidance, natural language search. AURA has the advantage of assembly awareness, meaning it can answer questions about your current model's properties, which the Onshape advisor can't. The Onshape advisor has the advantage of running in a browser-based tool that's already cloud-native, so the AI integration feels less bolted-on.

Against what Siemens is doing with Design Copilot in NX, same pattern: chat panel, documentation search, command suggestions. The enterprise CAD market has collectively decided that the first AI feature to ship is "search, but in a chat window." Nobody's model is going to break because the chatbot gave a bad search result.

None of these tools do what the text-to-CAD guide describes: generating actual geometry from a text prompt. They're all workflow assistants, not design generators. The gap between "AI that helps you use CAD" and "AI that does CAD" remains wide, and the vendor assistants are firmly on the first side of that gap. For a broader view of where these sit in the current field, the assistants are catching up on usability while the generators are still working on accuracy.

The verdict#

Onshape AI Advisor is a solid documentation assistant that lives inside a good CAD tool. For new users, migration users, and FeatureScript learners, it saves real time. For experienced Onshape modelers, it's mildly useful for the occasional question and mostly ignorable for daily work. The inability to see your model is the fundamental constraint, and until that changes, the advisor will always feel like it's helping from outside the room.

PTC is making the right bets on the roadmap. Context-aware assistance, FeatureScript tooling, and eventually geometry agents are the features that would make the advisor worth talking about in a year. What shipped so far is a foundation. A decent one, competently built, appropriately cautious. Just don't expect it to know what you're modeling, or why your sketch is broken, or which approach will actually survive the manufacturing review. That part is still on you.

I keep the advisor panel open. I ask it a question maybe once or twice a day. And most days, I close the answer, nod, and go back to doing it the way I was going to do it anyway. Which, honestly, might be the most accurate review I can give: it's there, it works, and I forget about it the moment I'm actually thinking about geometry.