Guardrails
Decide what Auprimus is allowed to do in a project. Open Guardrails under the message box, next to the model.
The menu
Guardrails has three tabs. Agent covers what the system may do while it works, DAG covers how a workflow's runs execute, and Alerts covers what you are told about. Each guardrail is one line: its name, then its control on the right. Hover the ⓘ next to a name to read what it does.
A choice is a small track with one stop per option: select a stop, or use the arrow keys. The option you chose is shown in brackets after the name, for example Install packages (Ask). A number is a field where blank means no limit. Select Save to keep your changes, or Reset defaults to go back to the project's starting values.
Guardrails belong to the project: they hold for its chat runs and its scheduled runs.
Agent
| Guardrail | Options | Default |
|---|---|---|
| System self-configuration | Allow · Deny | Allow |
| Other projects' memory | Allow · Deny | Allow |
| Install packages | Allow · Ask · Block | Ask |
| Internet access | Connectors · + Packages · Any | Any |
| Personal data | Off · Mask · Block | Off |
| Hidden instructions | Off · Warn · Block | Warn |
| Grounded answers | Off · Warn · Block | Warn |
| Spend per chat | A number, in USD | No limit |
| At the spend limit | Ask · Stop | Ask |
| Models allowed | All · Chosen | All |
Each connector
What a run may do with one connected system is set in that connector's form, under Guardrails, so one database can be written freely while another is only read. The plan says what each step does with each connector, and the step asks or stops before it starts.
| Guardrail | Options | Default |
|---|---|---|
| Read | Allow · Ask · Block | Allow |
| Write | Allow · Ask · Block | Ask |
| Delete or overwrite | Allow · Ask · Block | Block |
DAG
| Guardrail | Options | Default |
|---|---|---|
| Input check | Off · Warn · Block | Block |
| Output check | Off · Warn · Block | Warn |
| Run time limit | A number, in minutes | No limit |
| Pause failing schedules | A number of failed runs in a row | Never |
| Reuse finished steps | Allow · Deny | Allow |
| Largest file | 10 MB · 100 MB · 1 GB | 100 MB |
| Delete run files after | Forever · 7 days · 30 days · 90 days · 1 year | Forever |
Alerts
Alerts only tell you; they never stop a run. Turn on Step failed, Workflow re-planned and Scheduled run failed, and set how long Waiting for your OK, a Long run or a Long step may last before you are alerted.
When Auprimus asks
A guardrail set to Ask makes the run wait: a Confirmation required card appears in the chat, saying what it wants to do. Select Confirm to go ahead or Reject to stop that action. In a scheduled run nobody can answer, so Ask counts as Block; scheduled runs also have their own budget, see Schedules.
Every decision a guardrail takes is recorded; see Auditing.