Autodesk Assistant is not built into Revit 2023. If you are looking for the Assistant panel shown in newer Revit demonstrations, there is no Revit 2023 setting that enables that same built-in experience. Autodesk places it in Revit 2027 and later.
You can still use AI for native work in a Revit 2023 project. ArchiLabs Desktop supports Revit 2023–2027, including native model editing, so a team can use AI in the release its project already uses.
How to use Autodesk Assistant in Revit 2023
The direct answer is that you can't: the built-in Revit Assistant requires Revit 2027 or later. Autodesk's version guidance covers Revit 2023 among the earlier releases that don't include it. See the Autodesk Assistant availability article.
If you landed here hunting for a missing button, check two things first: which product and release the tutorial was recorded in, and which release you have installed. If the video shows Revit 2027 and your project is in 2023, that's the whole explanation. Signing into a newer online help experience won't add native model-editing tools to the older application.
That leaves two routes for a Revit 2023 project. You can use a third-party tool that works in 2023, such as ArchiLabs Desktop, or you can upgrade the project, which is a separate decision covered at the end of this article.
Use ArchiLabs with the existing Revit 2023 model
ArchiLabs Desktop runs on Windows and works with native Revit elements in Revit 2023. You can attach context to a request, such as specifications, PDFs, spreadsheets, screenshots with markups or the elements you've selected in Revit. That matters because many changes start outside the model. Explore ArchiLabs Desktop.
Keep the first session small. Work on a copy of the model, connect Desktop using the current setup guidance, and start with a question you can check yourself, such as how many instances of a particular family are placed on a level. Once the answer matches what you see in Revit, move on to one small edit. By the time you hand it real work, you'll know the connection is sound and how you'll review a change.
When the specification changes after equipment is modeled
Here's a common first job on an established project. The specification for a piece of equipment was revised after the families were placed, and the description and manufacturer reference in the model no longer match it. The geometry and placement are fine; only the data is out of date.
Attach the approved specification, select the affected instances, and ask ArchiLabs to compare the document with the current values and propose updates to the description and manufacturer fields only. Say plainly that geometry and placement stay as they are. Reviewing the proposed values before they're written lets you catch a wrong match while it's still easy to fix.
Specifications often list several variants of the same product, with different capacities, voltages or finishes. If the document doesn't make clear which variant your instances are, the assistant should ask you instead of picking one. A confident wrong guess is much harder to spot later than an open question, so put that instruction in your request.
Check whether the value is type or instance
Established projects carry years of decisions: naming conventions, legacy parameters, and families reused across several areas of the building. Before any parameter change, find out whether the value lives on the selected instance or on its type. A type parameter change reaches every instance of that type, including ones in parts of the project you never meant to touch. Ask the assistant which elements the change will affect before it applies anything. Our type and instance update guide sets out a good way to review that.
Afterward, look at the result where the team will see it. Open the schedule that reports these fields, check any tags that display them on sheets, and look at one instance outside the scope to confirm it didn't change. If a variant question is still unanswered, leave those instances as they were until someone resolves it.
You don't have to upgrade first
Moving a coordinated project to a new Revit release is a bigger decision than trying an AI tool. Once a model is saved in a newer release it can't be opened in Revit 2023 again, so everyone working in it has to move together. Families and add-ins need checking, and the timing has to suit the project schedule. That decision can follow its own timeline. If what you need now is native AI editing in Revit 2023, ArchiLabs Desktop does it in the release you're already on, starting at $19 a month plus usage credits (pricing). Bring a real family and the specification that changed to a Desktop walkthrough.
Avoid widening a Revit change unintentionally by deciding which updates belong to a family type and which belong to one instance.