Skip to main content

Reusable Checks

Reusable checks preserve a requirement you want applicable future tasks to verify. They begin with your explicit action on a saved user message; Locus does not automatically collect corrections or approve new rules.

Propose and approve a check​

  1. Open the menu on your saved message and choose Make reusable check.
  2. The selected model creates a visible proposal. Review the original correction, requirement, project, file or agent scope, and verification limits. Proposal generation is recorded in the source task's usage.
  3. Choose the check type: Human review, File exists, File contains text, JSON value, or Command succeeds. Edit any proposed details.
  4. Optionally choose Test check. Command tests use the task's existing permissions; respond to any permission prompt in that task.
  5. Choose Approve for future tasks to activate this version, or Dismiss to reject the proposal.

For example, a correction that all release notes must include migration instructions can become a required-text check for the relevant release document. A requirement that cannot be tested reliably should remain a human review check, with its limitation written down.

Scope and versioning​

An empty file scope applies across the project. A file scope such as Sources/** applies when matching files change or are named by the task. Only this agent or chat further narrows the check's owner.

Approved versions are saved into applicable future chat, team, goal, and capsule requirements. Existing tasks keep their saved versions. Editing an approved check creates a new proposal; the previous approved version remains active until the replacement is approved or the series is disabled.

Where available, Apply to this task explicitly adds the approved check and invalidates prior evidence so verification can run again. Goals and capsules use their own requirement-edit controls. Approval does not grant tools, bypass command permissions, or increase repair allowances.

Manage the library​

Open Settings → Agents & Teams → Manage reusable checks to review, edit, test, or disable saved project checks. Opening the library does not generate a proposal. Disable for future tasks stops new tasks from selecting the check while preserving versions already saved with existing tasks.

Remote deployment includes only the approved versions you select, together with their origin and version. Evaluation repetitions also keep the exact approved checks in their immutable configuration. Check outcomes use the same current evidence and bounded repair rules described in Task Recovery & Restoration.