¶ Compatibility and integrations
- Revit scripts can now control their own transactions, making script actions easier to combine without unexpected transaction conflicts.
- Assistant now supports Tekla Structures 2025.
- Assistant commands now run through the integration that owns the current design application.
- Disconnected integrations are cleaned up correctly, so they no longer leave stale running tasks behind.
- Messenger event handling is bounded, reducing the risk that a busy integration blocks other operations.
- Integration monitors now stop cleanly when their connection is disposed.
- Solibri AutoRun now handles multiple batches without mixing their completion state.
- Revit IFC export now applies the selected property sets correctly.
- Assistant can run guarded C# scripts in AutoCAD.
- ProjectWise folder loops now match paths correctly.
- AutoCAD integration queries now run one at a time, reducing conflicts during active operations.
- Assistant discovers available integration instances and lets users choose which one to use.
- Revit shortcut callbacks no longer block the Revit UI thread.
- Revit now shows the underlying reason when it cannot create a 3D view.
- Forge folder browsing limits concurrent requests and reports retry details more clearly.
- Revit no longer rejects valid workset selections when opening all worksets.
- Forge model browser navigation is more reliable.
- Revit-hosted Assistant chat now starts correctly when a Revit document is open.
- Dynamo again installs packages automatically and preserves graph ports.
- Revit popup closer now handles dialogs with a "Dismiss" button automatically, reducing interruptions during Revit workflows.
- In Revit, the chat panel is now labeled Agent instead of Chatbot, and Assistant uses gpt-6-luna for its responses.
- Solibri AutoRun now warns when a batch may leave Solibri open or contains an unusable Exit task, and offers a repair action before running. Close model can target a specific model by exact path or pattern while keeping the existing close-all option.
- Assistant chat sessions now start correctly in Revit 2022-2024 instead of timing out with a host-not-answering message.
- Batch Solibri checks tasks now start with the standard Solibri.exe path, so users no longer need to fill in the application path when using this template.
- Solibri AutoRun no longer reports completion too early and limits parallel runs.
- Assistant no longer asks for approval before read-only wiki, Forma, and local Revit model lookups. Operations that can change data, use network paths, or connect to integrations still require approval, and approving one operation no longer approves other operations in the chat.
- Revit 2026 Python tasks can now import rpw and print output without closing Revit or failing because of the host’s console encoding.
- ProjectWise connections now work whether the server URL includes a trailing slash or not, reducing failed requests when users browse, download, upload, or manage ProjectWise files.
- AutoCAD startup logs are now stored alongside Assistant's other AutoCAD bootstrap logs, making them easier to find when troubleshooting startup problems.
- Invalid Revit and AutoCAD C# scripts now report the required Execute signature as a source error, without misleading compile-failure text or empty line and column values.
- The Revit Agent pane now connects to the Revit it is running in, even when it starts before Revit's server. The Tekla Assistant button now waits for Tekla to finish starting its server before opening the Viewer.
- IFC exports from saved configurations now preserve the requested property sets in Revit 2024, 2026, and 2027 with either the built-in exporter or IFC for Revit. Unsupported settings are reported as warnings instead of being silently ignored.
- The Dynamo About window now shows the Assistant logo and name, displays the version clearly, and opens the Assistant website from its Website button.
- Assistant now starts correctly with Tekla Structures 2025 Service Pack 10 while continuing to support Service Pack 8 side by side.
- Users can sign in to Trimble Connect from Assistant again without seeing a wrong-password error or being signed out.
- In Revit chat, Assistant now explains which action-file changes require the Assistant window, and chat exports contain only the conversation shown to the user.
- Assistant chat in Revit 2025 no longer causes Revit to crash when users open Manage Links, including on machines using newer WebView2 runtimes.
- The Revit task "Run Dynamo script for Revit" is now marked as deprecated so users can distinguish it from the supported "Run Dynamo script" task. Existing task behavior is unchanged.
- Users can open and run Dynamo graphs again in Revit 2024 instead of seeing an error when a .dyn file is opened.
- Revit model-open shortcuts now run after startup without showing a shortcuts error dialog, including when a model is opened from the command line or by double-clicking an .rvt file.
- Run Dynamo script tasks now wait for Dynamo to finish loading before they start. When a run cannot start, Assistant reports the specific reason, such as an unavailable view, package-load failure, or a file that is not a runnable .dyn graph.
- Run Dynamo script tasks now stop immediately with a clear message when a graph is in an untrusted folder, including instructions for trusting the folder, so unattended workflows do not hang waiting for confirmation.
- Assistant now supports Revit 2026.5 with Dynamo 3.7, so Dynamo tasks and Start Dynamo for Revit work in that version.
- When an integration is unavailable, Assistant spaces out connection retries instead of sending repeated requests without a pause. Starting an already available integration is unchanged, and cancelled starts stop promptly.
- Agent chat now uses a separate operating-system-assigned port, reducing conflicts with Revit and other Messenger hosts so chat starts reliably and open chat panes can reconnect after a runtime restart.
- Starting Dynamo for Revit no longer stops at the Dynamo 4.0 welcome screen, so the task can continue without a manual Launch Dynamo click.
¶ Agent and chat
- Assistant now shows operations that are available but need a connection, so users can see what can be done and what must be connected first.
- Assistant chat sessions now persist across restarts, so users can return to previous conversations instead of losing them.
- Agent chat now shows the work plan while it runs.
- Assistant supports OpenAI and Azure AI Foundry providers.
- Extension documentation is available through a bundled documentation source, even when the external documentation service is unavailable.
- Assistant now exposes stable extensions as operations that Agent can use.
- Agent chat now shows queued messages and lets users steer an active run.
- Assistant built-in chat now uses the Responses API for its model interactions.
- Each chat now has one clear context owner, which is shown in the chat panel.
- Enumerated operation inputs can now be selected from chips in chat.
- Agent chat names the operation being requested instead of the underlying tool.
- New chats now offer suggested starting actions instead of opening to a blank screen.
- Chat actions stay visible while scrolling and follow the surrounding theme.
- Agent chat now uses one consistent definition of its context.
- Chats without an origin are no longer presented as Assistant-originated chats.
- Assistant-hosted chats now run actions in the correct host context.
- Loading files is safe when requests overlap or fail, and action files are not lost.
- Assistant-hosted chats can use the actions currently open in their host.
- Assistant checks that a chat belongs to the connection through which it arrived.
- Agent chat can describe a task and read its configuration.
- Users can change a task configuration from chat.
- Chat sessions are now created through the host connection, keeping their origin and context consistent.
- Assistant start page now includes Agent chat as a tab.
- The start page and dialog now call Chatbot Agent.
- Agent receives descriptions of what task fields mean, not only their current values.
- Agent sees one consistent description of each task.
- Token refresh now avoids repeated warnings while a token remains due.
- Assistant opens its window and chat without waiting for sign-in or a fixed delay.
- Deleted tasks no longer remain falsely executable.
- Hosts can describe the user’s current selection in chat.
- Regex generation works again.
- Agent can see task members even when they hold no actions.
- Assistant now tells you when a chat run stops before finishing, including the reported reason when available, instead of leaving the chat silent.
- Assistant no longer gets stuck after a canceled or interrupted tool action. Later messages can continue instead of failing silently.
- Long Assistant chats and AI Agent tasks no longer resend earlier prompts on every run, reducing unnecessary model input and helping conversations and tasks continue for more steps before reaching context limits.
- Agent chat history is retained for all supported AI providers.
- Long chats now fit within the model context by shortening older context when needed.
- Assistant now displays C# script arguments as readable source code in chat and approval details, while keeping additional arguments visible separately.
- Agent can be opened in a separate window from the start page.
- Agent shows how much of the available context the chat is using.
- Generating a Python script in Assistant now works with the built-in AI service instead of failing with an API error.
- Category filter presets now include more HVAC and electrical categories, and site categories are enabled by default. Filter choices are shared across Assistant tools and reset once to the new defaults; new users get organization-provided settings when available without creating stale machine-wide defaults.
- Agent chat no longer covers the hamburger menu, notification drawer, save-changes dialogs, or license overlay when they open. The chat returns after the overlay closes.
- Undoing deletion of an action group now restores its actions in their original order, so users can continue editing and save the recovered group without losing its actions. If the deleted group contained the open action, Undo reopens it.
- Users can now export an Assistant chat as a Markdown file, including the conversation, approvals, tool activity, queued messages, failures, and the context supplied to the model.
- When the Assistant API is unreachable, the Add task picker still shows built-in tasks and searches them locally, while clearly indicating that extensions are temporarily unavailable.
- When you decline an approval in Assistant, the Agent stops without retrying the same operation, clearly says it was not completed, and marks the tool call as Denied in the chat and exported conversation.
- When the Agent cannot start, Assistant now replaces the loading spinner with a clear explanation and steps to try, including closing other Assistant windows or restarting the computer.
- Assistant now tells you when an AI request is being retried, including whether the provider is busy, returned an error, or did not respond, so a delayed reply no longer looks like a frozen chat.
- Assistant chat can now open without a license so users can view its history and settings. Sending a message still requires a license and shows the existing license message instead of failing when the chat opens.
- Long-running Assistant operations that use the built-in AI service can now finish instead of being stopped and retried after 10 seconds.
- Agent chat stays available after a temporary connection failure instead of requiring an Assistant restart before the next message.
- Open Agent chats keep working when the local chat runtime exits because Assistant starts it again on the same address.
- When an Agent run fails after streaming starts, Assistant now shows a clear error message in the chat instead of ending with a generic "terminated" message. Sign-in, API key, and other run failures are reported without exposing technical error details.
- Agent chat now spaces tool calls evenly and provides one visible copy button for each completed round, copying the round's assistant text without tool calls or their results.
- Assistant chat now continues after users approve or deny a tool request. A declined sign-in is also shown as Denied instead of remaining in the Running state.
- Agent chat now sends new prompts normally after you reload a conversation, instead of leaving them stuck in the Queued messages list.
- Assistant no longer remains stuck on "Checking database..." when a previous startup was interrupted. If the local service does not finish starting, Assistant now shows a failure message instead of waiting indefinitely.
- Assistant keeps a previously valid, unexpired license active when a temporary storage timeout occurs, so users can continue working instead of being asked to retry the license check.
- Errors from query handlers now retain the original failure location in logs, making support investigations easier when an overnight or automated run fails.
¶ Files, tasks, and templates
- Assistant start page now has Recent Files and Templates tabs for quicker access to recent work and reusable tasks.
- Assistant text search now returns results correctly and shows a clear error when search cannot be completed.
- Assistant no longer duplicates top tasks when metrics are reported repeatedly.
- Assistant now includes 16 curated templates to help users get started.
- Assistant start-page templates are easier to browse, with clearer navigation and cards.
- Schedule triggers now have a Run now action.
- Generated startup scripts now show Assistant branding and a skippable countdown.
- Assistant start-page file navigation is easier to use.
- Hierarchical folder loops now provide each item’s relative path.
- Task descriptions now use clearer wording.
- Assistant cloud file browsers now use a consistent resizable layout with clearer provider and item icons, better scrolling and loading feedback, and easier access to grouped favorites across supported services.
- Dragging tasks from search now assigns extensions correctly.
- Recent files now use one shared settings location per application.
- Undo actions now run only once, so deleted items are restored at most once and later clicks cannot undo newer changes.
- Recent files now move to the top after you open them, so the list stays current when sorted by date or frequency.
¶ Reliability and sign-in
- Retrying an action now preserves each run in its history.
- Assistant now reports its connected state only after the connection is ready.
- Backend requests can now reach the correct host through the Assistant connection.
- Assistant now retries a sign-in token less often when a temporary problem prevents its background refresh, reducing repeated warnings while continuing to refresh healthy tokens normally. Tokens are still refreshed on demand when needed.
- Assistant keeps users signed in to SharePoint beyond the first access-token expiry by refreshing the token correctly, and no longer gets stuck accessing SharePoint data after a refresh.
- Visibility expressions now support full paths and numeric enum values.
- Assistant now protects its local services with a per-launch secret, preventing websites and other Windows users on the same machine from sending requests to the user's Assistant session or connected design applications.
- Assistant now evaluate conditional placement during Coordination Tool element assignment.
- Published extensions now resolve to the correct version.
- Shortcut progress updates no longer hold background workers unnecessarily.
- Assistant recognizes its origin regardless of letter casing.
- Extension argument upgrades skip types that cannot be loaded.
- Variables in serialized extension inputs are expanded correctly.
- Assistant Cloud users no longer see the generic Logins window before browser authentication starts. Other login providers keep the existing login window.
- Installing a specific Assistant version with
assistant-installer install -v now keeps that version pinned, so a later update check does not silently switch back to an older pinned build.