Choose what to analyze | Faustine Docs

Choose what to analyze is the stage where the analysis waits for you to select modules. A module is one feature area of your app. Faustine writes actions only for the modules you select, and each module you add takes more time and more tokens from your model provider.

Before you begin

The analysis has finished Analyze the architecture & modules. The stage shows how many modules and insights it found.

Select the modules

To choose what becomes actions:

On the analysis page, go to Choose what to analyze. The stage lists Application Insights and Modules.
Under Modules, select the modules the agent needs. Each one has a name and a line that says what it covers. All selects every module and None clears the selection.
Select Analyze selected.

Each selected module shows its progress, its time and its cost while it runs. When they finish, the page moves to Summary.

The entries under Application Insights are Authentication and Navigation. They are analyzed together with the architecture, so they are already done when this stage opens and you do not select them.

What to select

Start with the modules your users work in every day. A first agent with two or three modules is quicker to review and to test than one with every module, and you can analyze the others later.

Leave out areas the agent should not touch, such as an internal admin section. An action that was never generated cannot be run. You can also turn off single actions afterwards. See Turn an action on or off and test it.

Analyze more modules later

To add modules to an agent that already has a version:

In the agent's header, open the Actions menu and select Re-analyze repo.
Leave Use current analysis as context on. The run keeps the module names and your earlier selection.
Select Re-analyze, and select the modules when the run reaches Choose what to analyze.

Warning

A re-analysis overwrites the edits you made to the draft by hand or in the Advanced editor. Publish what you want to keep first. Published versions can be restored.

Troubleshooting

Symptom	Cause	Fix
Couldn't start the module analysis appears above the button	The service did not accept the selection. The message after the colon is the reason.	Select Analyze selected again.
The summary shows a number of modules that couldn't be analyzed	Those modules failed. Their work is not in the draft.	Select Retry failed modules. The modules that succeeded are kept.
A feature you expected has no module of its own	The analysis groups the code into feature areas, and the feature is part of another module.	Read the descriptions of the listed modules. To get a separate module, describe it in the analysis notes and re-analyze. See Keep the agent up to date.

Next steps

Actions: review the actions of each module.
The analysis: the other stages and what they produce.
Keep the agent up to date: updates and re-analysis.