--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Checkpoints and conversation change log # Build Agent checkpoints and conversation change log {#ariaid-title1} Release version: Australia Updated August 25, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Build Agent checkpoints and conversation change log The conversation change log in Build Agent automatically tracks every change made to your application during a conversation. It is accessible within ServiceNow Studio as an integrated tab, enabling you to view, manage, and deploy changes efficiently. This feature provides visibility into updates, supports rollback to previous checkpoints, and facilitates deployment through update sets. Show full answer Show less ## Key Features * **Conversation Change Log:** Allows you to view changes since the last checkpoint, roll back to previous checkpoints, and approve changes for deployment. * **Checkpoint Management:** Checkpoints group changes made during your conversation and are created automatically after each approved task plan. They enable easy restoration of your app to a prior state. * **Update Sets Integration:** Each checkpoint corresponds to an update set that packages changes together for deployment. Update sets created by Build Agent appear in the Deployment tab of ServiceNow Studio, and can be merged if they are within the same application scope. * **Files List and Overview:** The log displays all files updated by Build Agent, categorized similarly to ServiceNow Studio's Navigator panel, along with a summary of the plan and actions taken during the conversation. * **Manual Edit Update Sets:** When preparing new checkpoints, Build Agent checks for manual edits. If present, it completes and includes those update sets; otherwise, it removes empty ones. These can be accessed directly from the checkpoints panel. ## Important Details for Customers * Checkpoint 0 serves as a UI placeholder to restore your application's initial state and does not create an update set itself. * Checkpoint 1 is the base update set and acts as the parent for all subsequent checkpoints, ensuring all update sets exist in the same application scope for easier merging. * Earlier versions (Australia Patch 3 and before) created update sets in different scopes, which cannot be merged. Current versions create all in the application scope. * You can open update sets relevant to each checkpoint directly from the conversation change log for quick access and deployment. ## Practical Benefits Using the conversation change log and checkpoints helps ServiceNow customers maintain control over application changes made through Build Agent. It simplifies tracking progress, enables safe rollbacks to previous states, and streamlines deployment through well-organized update sets. This ensures your application development is transparent, reversible, and aligned with best practices for change management within the ServiceNow platform. The conversation change log tracks every change Build Agent makes to your application. It appears automatically in an integrated tab in ServiceNow Studio and lets you view updates, roll back to a previous checkpoint, and deploy changes to an update set. ## Conversation change log {#ba-conversational-change-log__section_pkp_1k3_sjc} Use the conversation change log to do the following actions: * View the changes you have made since a checkpoint * Roll back changes to the previous checkpoint * Approve and deploy changes to an update set {#ba-conversational-change-log__ul_cdj_tph_53c}When viewing the conversation change log, you can also view update sets created by Build Agent from within the chat panel. Each checkpoint includes a button that opens the relevant update set in a new tab. For information on how the change log and checkpoints work with update sets, see [Update sets and Build Agent](https://servicenow-prod.fluidtopics.net/25K10uRGfz2uc5gvqIreEA "When you work with Build Agent, your changes are automatically tracked in update sets so you can review, revert, and deploy them without leaving ServiceNow Studio."). The change log displays the following: * The Files list displays all the files that Build Agent updated during your conversation. The categories mirror the ones in the ServiceNow Studio Navigator panel. * The menu at the top shows the current checkpoint. You can use the list at the end of the checkpoint name to select a different checkpoint to view. When there are multiple checkpoints, a Summary option appears, which shows changes from each checkpoint all together. * The overview section shows the plan and actions Build Agent took based on the conversation. * The action in the corner menu to pen the chat, Restore your app to a previous checkpoint, or open the app details page. Changes from each checkpoint in the conversation are packaged together into an update set. You can find each update set on the Deployment tab on the ServiceNow Studio home page. For more information on deployment, see [Deploying what you built with Build Agent](https://servicenow-prod.fluidtopics.net/UfO9v7wOOeW1T_UazSmw1A "Learn about deployment methods and workflows for moving applications created with Build Agent from development to production environments. Choose the right deployment approach based on your application complexity and organizational requirements."). ## Checkpoints {#ba-conversational-change-log__section_pxq_dk3_sjc} Checkpoints are groups of changes that you made to an application that you can revert to at any time during your conversation with Build Agent. Checkpoints are created automatically after you approve each task plan. Note: With Australia Patch 3 and earlier, checkpoint 0 creates an update set in global scope, and subsequent checkpoints created update sets in your application scope. However, update sets that exist across different scopes and can't be merged. * Checkpoint 0 creates an update set in global scope, and subsequent checkpoints created update sets in your application scope. However, update sets that exist across different scopes and can't be merged. * Checkpoint 0 doesn't create an update set. Instead, it serves as a placeholder in the UI that you can use to restore your application to its initial state. * Checkpoint 1 is the base update set for your application. The checkpoint 1 update set is the parent, or chain root, for all subsequent update sets created during the conversation. Because all update sets exist in the same application scope, you can merge them together when you're ready to move your changes to another environment. For information on update sets, see [Update sets and Build Agent](https://servicenow-prod.fluidtopics.net/25K10uRGfz2uc5gvqIreEA "When you work with Build Agent, your changes are automatically tracked in update sets so you can review, revert, and deploy them without leaving ServiceNow Studio."). {#ba-conversational-change-log__ul_pkh_gk3_sjc} Figure 1. Checkpoints card When Build Agent prepares to create the next checkpoint, it checks whether any changes exist in the manual edit update set. If no changes are present, Build Agent removes the update set. If changes exist, Build Agent completes the update set and renders it with the other update sets from your conversation. You can access manual edit update sets directly from the checkpoints panel in your Build Agent conversation.