Sync scout configs

The skill this config controls as a scout. Set at creation, not editable.

Human-readable summary of what this scout investigates, sourced from the scout skill's description metadata. Use it for a quick steer on the scout's focus without loading the full skill body. Empty if the skill is not currently present on the team or carries no description.

Name shown in the UI. Does not change the skill name. Leave blank to use the default name.

• canonical - canonical
• custom - custom

Whether this scout runs on its schedule. Disabled scouts are skipped by the coordinator. Derived from status: true for active and pending_pause, false for the paused statuses.

• active - Active
• pending_pause - Pending pause
• paused_by_system - Paused by system
• paused_by_user - Paused by user

• team - Team
• background - Background

Whether the scout writes findings to the inbox. False = dry-run: it runs and logs but emits nothing.

Minutes between runs (30–43200). The scout runs once this interval has elapsed since its last run.

Optional five-field cron expression evaluated in the project timezone, e.g. '30 9 * * *'. Takes precedence over run_interval_minutes when set. Null means the rolling interval schedule.

• trusted - Trusted domains only
• full - Full

Optional model id this scout's runs are pinned to, e.g. claude-opus-4-5. Must be one of the platform's agent models; an invalid id is rejected with the available ones listed. Null keeps the default model, chosen by the platform. Early access: the pin can only be set on projects enrolled in the scout model preview, and only takes effect there. Set null to clear it.

Opt-in guard on this scout's lifecycle. Off by default, so anyone with scout write access may pause, resume, switch the scout to dry run, or delete it. On, only the person the scout's runs act as or a project admin may do any of those, or change this flag. Use it on a scout whose output people depend on: signal_scout:write is a project-wide scope held by people and by unattended agents alike, and a resume has to pass the project's enabled-scout maximum that a pause does not, so a bulk pause is not undone in one step. The lock never stops an automatic pause, such as the inactivity sweep or the repeated-failure breaker.

Preset used to select the saved tool list, custom for an explicit list, or null when unrestricted.

Optional HogQL SELECT a scheduled run evaluates before it starts. When it returns no rows, or one row with one false value (false, 0, null or empty), the run is skipped: no sandbox, no model call, and no run row. Any other result starts the run, and the scout reads the rows. A query error also starts the run. Use {since} (the start of the last run that ran, or when the scout was created) and {now} to look only at what is new, e.g. SELECT count() FROM events WHERE event = '$exception' AND timestamp > {since}. To run at least once a week however quiet it is, add OR {since} < {now} - INTERVAL 7 DAY to the condition. Only scheduled runs evaluate it: a manual or workflow run always starts. {interval_minutes} is the gap between two scheduled runs, so a backstop can follow the schedule: {since} < {now} - toIntervalMinute(greatest(1440, 2 * {interval_minutes})) runs at least daily and never more often than every two intervals. The query stops after 10 seconds and reads at most 50 rows. Try a query with scout-config-precheck-test before you save it. Null or blank uses the default pre-check the scout's skill ships, if any. To turn every pre-check off, set precheck_disabled.

True turns off the pre-check, both precheck_query and the default the skill ships, so every scheduled run starts. False (the default) uses precheck_query, or the skill default when that is null.

The pre-check query the next scheduled run uses: precheck_query, or the default the scout's skill ships. Null when no pre-check runs.

When the coordinator last dispatched this scout. Null if it has never run.

How many of this scout's runs have failed in a row. Back to 0 after a successful run or any config edit. At the failure limit the scout pauses itself (status becomes paused_by_system with pause_reason repeated_failures) and retries about once a day; a successful retry resumes it, and so does setting enabled=true.

When status last changed. For pending_pause this is when the warning was issued (an ignored warning pauses about a week later unless someone engages with the scout's reports — opening one counts; a no_output warning only flags the scout); for the paused statuses it is when the scout was paused. Null if the status never changed.

Whether this scout is exempt from the inactivity sweep, meaning both the ignored pause and the no_output quiet warning. Set it on watchdog scouts whose value is staying quiet. Only ever set explicitly: re-enabling a swept scout instead grants a fresh grace window before the sweep may judge it again.

The product that stood this scout up for one of its own objects. Null when a person created it.

Id of the owning object in source_product, e.g. a Replay Vision scanner id.

When this config last changed: an edit through this API, or a status change the system made such as an automatic pause. A scheduled run does not bump it — the coordinator stamps last_run_at with a direct write — so this reads as when the scout was last tuned rather than when it last ran.