Keep the agent up to date

A Web Agent is generated from your code at one commit. When the app changes, an update compares the new code with that commit and changes only the actions the difference affects. Updates run on every push or when you ask for one. A re-analysis starts again from nothing.

Choose how the agent follows your code

Way	When it runs	What it does to your edits
Auto-update	On every push to the connected branch.	Keeps them.
Check for updates	When you select it.	Keeps them.
Re-analyze repo	When you select it.	Overwrites the edits in the draft.
Upload a new version	When you upload a newer ZIP. Agents built from a ZIP only.	Keeps them.

Auto-update is the recommended setting for an agent built from a repository, because the actions stop matching the app as soon as an endpoint changes. Every run uses tokens from your model provider. A run that changes the agent publishes a version, and that version is served on the release target immediately. If the release target is the environment your users load, each push to the branch can change what they get without anyone reading the change first.

Turn auto-update on or off

To change the setting you chose when you created the agent:

In the portal, go to Web Agents and select your agent.
In the Overview tab, find the card with the repository and turn Auto-update on or off.

With the switch on, the card reads Re-analyzes on every push. With it off, it reads Manual re-analysis. The switch is not available for an agent built from a ZIP.

Check for updates

To run an update yourself:

In the agent's header, open the Actions menu and select Check for updates.
The Activity tab opens on the new run. Select the run to follow its log.

The run compares the branch with the commit the agent was generated from, and ends in one of these states:

State	Meaning
No impact	The commits did not touch anything the agent uses. Nothing changed.
Published v2, with the number of the new version	The run changed the draft and published it as a new version. The run's change report says what was added and changed, and whether a change breaks the version in service.
Draft updated	The run changed the draft and did not publish it. The draft was edited or a version was published while the run worked, or the publish failed. The run's log gives the reason. Review the draft and publish it yourself.
Queued	The draft had unpublished changes when the run was requested. The run waits.

A version published by an update is served on the release target, like a version you publish yourself. Other environments keep the version they serve. See Versions, environments and deployments.

Resolve pending updates

An update starts from a draft with no unpublished changes. If you have edits in the draft, updates queue behind them, and the Activity tab shows the number of pending updates.

To run them:

Publish the draft. See Publish a version.
In the Activity tab, select Resolve next to run the oldest pending update, or Resolve all to run them as one.

Re-analyze

A re-analysis discovers the modules and writes every action again. Use it to add modules you did not select the first time, or after a rewrite of the app that an update cannot follow.

Warning

A re-analysis overwrites the edits you made in the draft, by hand or in the Advanced editor. What your environments serve does not change until you publish, and published versions can be restored.

To re-analyze:

In the agent's header, open the Actions menu and select Re-analyze repo. For an agent built from a ZIP, the item is Re-analyze.
Leave Use current analysis as context on to keep the module names and your selection. Turn it off for a clean run that discovers everything again. A clean run is slower, and module names can change.
Select Re-analyze.

The analysis page opens. See The analysis.

Upload a new version

An agent built from a ZIP has no branch to follow. To update it:

In the agent's header, open the Actions menu and select Upload a new version.
Upload the code as it is now.
Turn on Keep the code after the analysis if you plan to upload another version later. The next update needs this archive to compare with.
Select Replace the code.

Faustine compares the new archive with the one it analyzed and starts an update run, which you follow in the Activity tab. If the stored code was deleted, the menu item is Upload the code again, and the portal offers a re-analysis because it has nothing to compare with.

Troubleshooting

Symptom	Cause	Fix
The draft still has unpublished changes — publish it first.	You selected Resolve next or Resolve all with edits in the draft.	Publish the draft, then resolve again.
The repository card says your connection predates auto-update	The GitLab or Bitbucket connection cannot create the webhook that reports pushes.	Select Re-connect on the card.
Advanced editor and Re-analyze are disabled for an agent built from a ZIP	The stored code was deleted.	Select Upload the code again in the Actions menu.
A run ends with Published but your site still shows the old behavior	The environment your site loads is not the release target.	Deploy the new version to that environment. See Deploy a version to an environment.

Next steps

Activity: the record of every analysis and update run.
Publish a version: publish the draft an update is waiting for.
Upload a ZIP instead of a repository: keep or delete the uploaded code.