¶ Improvements and fixes
- Revit C# scripts can now control their own transactions and cancellation, so committed model changes are kept when a later part of the script fails or is canceled. The execution result no longer reports host rollback or changed-element details.
- Assistant now supports Tekla Structures 2025, so users can use the Tekla integration with projects running that version.
- Assistant can now show matching operations and their connection requirements before the required integration is connected. Execution still checks the live connection before running the operation.
- Assistant now retains completed chat sessions and relevant model and document context locally. Persistence failures are shown in the chat without hiding a completed response, while live chats are not reopened automatically after a restart.
- When an integration disconnects, Assistant can still clean up the correct running process and reports a clear result if cleanup cannot be completed.
- Assistant's start page now separates Recent files and Templates into tabs, with search and browsing controls for each tab. The selected tab is remembered for the next visit, while empty or still-loading recent files are handled clearly.
- Assistant integrations now process events in order, avoid repeating events during restarts or handovers, and finish queued work before shutdown. Handler failures are logged with the integration and event identifiers.
- Solibri AutoRun tasks with multiple inline batches now run each batch separately in sequence, so every batch is executed reliably and temporary configuration files are removed after use.
- Assistant text search now returns matching tasks and extensions instead of an empty list when a search fails, and shows a clear error message while preventing older searches from replacing current results.
- Assistant integrations now stop their background activity cleanly during disconnects, restarts, and shutdowns, reducing duplicate events, stale connections, and failed reconnects.
- Top task usage counts now remain accurate when the same task is reported by multiple metric entries, so usage-based task lists no longer undercount activity.
- Revit IFC exports now preserve the selected property-set options, including built-in and custom property sets, schedules, materials, and parameter mappings. Existing custom property-set file overrides continue to work.
- Assistant now starts the hosted CLI and related shortcuts on the exact Revit, AutoCAD, Navisworks, Dynamo, or Tekla instance that launched them. This prevents a chat or shortcut from connecting to a different running instance when more than one is available.
- Assistant can now connect to OpenAI or Azure AI Foundry from its AI configuration, let users choose the OpenAI API mode, discover available models, and show clear connection results.
- Manual Coordination Tool assignment now follows the applicable placement rule when selecting an existing element, preventing assignments to the default family when a different family is required.
- Assistant chat now shows a read-only work plan for complex requests above the chat input, so you can see which steps remain without the plan appearing as ordinary tool activity.
- Published extensions now run with the correct integration and version, so Assistant no longer fails before execution or routes AutoCAD, Navisworks, or Tekla extensions through Revit.
- Assistant now provides separate C# scripting tools for Revit and AutoCAD. Integrators can run complete scripts against the active AutoCAD drawing with clear validation and cancellation behavior, while script-owned document locks and transactions remain under the script's control.
- ProjectWise and Forge loop tasks now apply path filters correctly to nested folders, so files in excluded folders such as Testing are left out as expected.
- AutoCAD actions now wait for queued commands to finish before the next action starts, reducing "Drawing is busy" errors in workflows that run commands, save drawings, and close them.
- Assistant start-page navigation now uses clearer Recent files and Templates choices, with aligned search and more compact template cards that show loading progress without obscuring the selected template.
- Fields in Assistant forms now appear and enable correctly when visibility rules refer to nested fields, full paths, or enum values by name or number. Missing nested values no longer cause validation errors.
- Assistant can now discover and run accessible published extensions through the same operations workflow as other capabilities. When some extension inputs cannot be fully described, Assistant shows a notice while still allowing discovery and checks the live integration connection before execution.
- Assistant now keeps each retry attempt in the action run history, labels repeated attempts clearly, and reports a mixed failed-and-successful sequence as partially succeeded instead of hiding the earlier failure.
- Assistant now provides curated templates for common Revit, AutoCAD, Navisworks, Tekla, cloud-file, and file-management workflows. Selecting a template creates an editable action with safe defaults and placeholders, while unavailable hosts or extensions show a clear creation error.
- Users can now run a configured schedule trigger immediately from Assistant Viewer, without waiting for its next scheduled time. The action respects the trigger's selected actions and existing sign-in requirements.
- Built-in AI chat now streams responses steadily as they are generated, instead of delivering most of the response at the end.
- Assistant integrations now build consistently with the same C# language version across supported .NET frameworks, reducing framework-specific build differences for users and contributors.
- Recovered integrations are now reported as connected before dependent features receive the connection update, so chat and other consumers no longer briefly treat them as unavailable.
- Assistant no longer offers integrations for obsolete host versions. Supported Revit, AutoCAD, Navisworks, Dynamo, and Tekla versions now match the current supported-version list, reducing invalid installation and configuration choices.
- Long-running shortcut operations no longer exhaust Revit's threads and handles while the host is busy, reducing the risk of crashes and allowing the operation to recover when Revit resumes.
- When saving an Assistant startup script, users can now see what it will launch, watch a live countdown, and press a key to start immediately or close the window to cancel.
- Assistant now lets users see running integration instances, including their open model and version, and choose which one to use. Switching keeps the existing connection if the new one cannot be established, and automatic startup selection no longer overrides a deliberate choice.
- Browse extensions suggestions no longer treat Assistant as a product to search for, regardless of how the host reports its casing.
- Assistant Viewer now lets users create a new action file, browse for an existing file, and return to configuration from the start page. Viewing runs no longer loses the active action file context.
- Assistant chat now keeps messages submitted during an active run visible above the input, where users can edit, remove, undo, pause, resume, or steer a message into the current run. Queued messages are processed in order, and stopping or a failed run pauses the queue.
- Users no longer see an unexpected Report issue dialog when a pop-up menu closes during an animation. The underlying animation error remains logged for investigation.
- Loop tasks for ProjectWise, Autodesk Forma, and local folders now provide a relative path that keeps the selected root folder and nested folders, making it easier to build outputs or references from the original folder structure.
- Assistant's start page now includes an Agent tab, so users can open AI chat alongside Recent files and Templates. The selected tab is remembered for the next visit.
- Assistant now refreshes sign-in tokens before they become too close to expiry, reducing repeated refresh warnings and preventing requests from using tokens with only a short time left.
- The start page and Agent dialog now use the name Agent consistently, including tab labels, loading text, and notifications.
- Assistant starts faster because sign-in checks no longer block the window, and Agent chat becomes ready sooner. Chat initialization now avoids getting stuck when users switch tabs while it loads.
- Assistant handles large BIM 360 and Forma folder traversals more reliably, with fewer throttling failures and clearer details when Autodesk rate limits requests.
- Assistant now makes its Revit, AutoCAD, Navisworks, and Tekla extension tasks clearer by stating that users can run an existing extension or create a new one.
- Assistant can now continue upgrading saved extension inputs when some extension types depend on unavailable host components, so compatible saved actions remain usable instead of failing during upgrade.
- Revit no longer reports warnings for previously selected worksets when you choose Open All Worksets. Workset validation remains active for Close All Worksets and Open Last Viewed.
- Run actions become available immediately after you delete a task that was preventing them from running.
- Regex generation now validates returned patterns directly and retries invalid or non-matching results without conflicting instructions, making regexes generated from examples more reliable.
- Assistant now provides a resizable Revit model browser with searchable Favorites and an Autodesk Forma view side by side. Clear icons, folder support, grouped projects, and full-path tooltips make cloud model selection easier to navigate.
- Assistant chat can now see task members even when their values are empty, so it can describe the full task configuration.
- Assistant chat now knows which task or action you have selected, so requests about "this task" use the item you are working with.
- Assistant chat now uses one consistent description of task fields when reading or changing task settings.
- Assistant chat now receives clearer information about what each task field means, helping it interpret and update task settings correctly.
- Chat sessions opened from Assistant now retain the same actions and context as sessions opened through the host integration.
- Assistant chat can now propose task-configuration changes for your approval before applying them to the open action file.
- Assistant chat can now describe a task and read its current configuration.
- Chat sessions now stay tied to the integration that created them, preventing actions from being sent to the wrong host.
- Assistant-hosted chat can now use actions from the open Assistant file.
- Opening an action file while another load is in progress no longer risks losing the file or its changes.
- Assistant actions now use the same project context as the open screen, so changes made through connected tools appear in the correct place.
- Chats without a host integration are no longer treated as Assistant-hosted chats.
- Assistant-hosted chat can now exchange requests with the host integration when an action needs information from it.
- Revit shortcut actions no longer wait on the Revit interface while they complete, reducing delays during shortcut use.
- The Assistant chat panel now keeps its controls in a compact top row and follows the application theme.
- New chat sessions now show starter suggestions, making it clearer what Assistant chat can do before you type.
- Assistant chat now shows the user-facing name of an operation instead of an internal tool name.
- Assistant chat now offers available choices directly for operations that use a fixed set of values.
- Chat sessions now keep one consistent context, including the active host and open model, throughout the conversation.
- Assistant can now check the installed Revit, AutoCAD, Civil 3D, Plant 3D, Tekla Structures, and Navisworks APIs before generating host scripts, reducing errors caused by using the wrong version or member name.
- Assistant can now run guarded C# scripts in Tekla Structures against the open model, including scripts that read selected objects or make model changes. Scripts receive a clear warning when changes may remain after a failure or cancellation.