Settings
Open Settings in the dashboard to choose how SourceAnt reads, reviews and remembers your code. Check where a setting applies before changing it.
Where settings apply
The repository and organisation selector chooses what you are configuring. With neither selected, the settings apply to your account. The available sections depend on that selection and the features enabled on your deployment.
For settings available at each level, SourceAnt uses the first value set on the repository, workspace, organisation or your account, in that order, then the default. The panel marks values as set here, inherited or default.
Change a value and choose Save. Reset removes the override at the selected level so the inherited value applies again. Not every setting can be changed at every level.
Choose a model
Open Model and choose where the model applies:
- Global (all my workspaces): your personal default where a workspace or repository has not chosen a model. It is not a deployment-wide setting for every user.
- This workspace: a shared choice for the active workspace.
- The selected repository: a model override for that repository. It uses a compatible workspace or personal key.
For a personal or workspace setup, select a Provider and model, enter its API key, then choose Save. The form checks the key before saving. It also shows where the current model and key come from.
Credentials must match the chosen provider. Selecting a model from another provider does not make an existing key work with it. A repository override takes priority over a workspace or personal model choice.
See and delete saved keys
Open Model → Keys to see saved provider settings for your account and the workspaces you can access, including where they apply. Secret key values are never displayed.
Delete key removes the key, model and endpoint stored at that level. Deleting a workspace override lets your requests fall back to your personal settings; other members fall back to their own. A repository model override still applies, and requests need a key compatible with that model.
To remove only a repository's model choice, use Use inherited model. A saved key without a model selected at its level is not used until a model is selected there.
Control reviews and background work
These sections show the settings available for your selection. Each control includes a description and any limits on its value.
| Section | What it controls |
|---|---|
| Review | Whether pull requests and drafts are reviewed, when outdated work stops, reuse of earlier reviews and model answers, and review limits. |
| Initialization | How much evidence and how many parts are read, which paths stay out of the index, and limits on knowledge proposals and follow-up investigations. |
| Schedule | How often repositories are read again and new knowledge is sought. |
| Knowledge | The confidence threshold for accepting knowledge automatically. |
| Skills | Extra places to look for skills. |
| Background work | How many jobs a workspace can run at once and how long finished jobs are kept. |
Clear cached results
In Cache, choose Everything, the active workspace, or a selected repository. Then choose Clear beside the cache you want to empty. The result reports how many entries were removed.
Clearing a cache means its contents must be rebuilt when needed, which can require more model calls. Workspace and repository filters reach entries recorded for that owner; Everything also includes entries without an owner.
Connect an editor or agent
Open MCP to see the tools available on your deployment and generate an access token for the active workspace. Copy the token when it is shown, then use the configuration snippets under Connect your tools in your client.
The token is shown once and has an expiry date. Generating another token does not revoke an earlier one. Calls can access repositories connected to the token's workspace.
Account and repository access
Account shows your profile, connected repositories and GitHub App installations. Use Install on GitHub or Install somewhere else to give the app access to another account. See Cloud setup for connecting repositories.