2026-01-09 00:32:48 +00:00
|
|
|
|
---
|
|
|
|
|
|
summary: "Repository scripts: purpose, scope, and safety notes"
|
|
|
|
|
|
read_when:
|
|
|
|
|
|
- Running scripts from the repo
|
|
|
|
|
|
- Adding or changing scripts under ./scripts
|
2026-01-31 16:04:03 -05:00
|
|
|
|
title: "Scripts"
|
2026-01-09 00:32:48 +00:00
|
|
|
|
---
|
2026-01-31 21:13:13 +09:00
|
|
|
|
|
2026-01-09 00:32:48 +00:00
|
|
|
|
# Scripts
|
|
|
|
|
|
|
|
|
|
|
|
The `scripts/` directory contains helper scripts for local workflows and ops tasks.
|
|
|
|
|
|
Use these when a task is clearly tied to a script; otherwise prefer the CLI.
|
|
|
|
|
|
|
|
|
|
|
|
## Conventions
|
|
|
|
|
|
|
|
|
|
|
|
- Scripts are **optional** unless referenced in docs or release checklists.
|
2026-01-30 03:15:10 +01:00
|
|
|
|
- Prefer CLI surfaces when they exist (example: auth monitoring uses `openclaw models status --check`).
|
2026-01-09 00:32:48 +00:00
|
|
|
|
- Assume scripts are host‑specific; read them before running on a new machine.
|
|
|
|
|
|
|
|
|
|
|
|
## Auth monitoring scripts
|
|
|
|
|
|
|
|
|
|
|
|
Auth monitoring scripts are documented here:
|
|
|
|
|
|
[/automation/auth-monitoring](/automation/auth-monitoring)
|
|
|
|
|
|
|
|
|
|
|
|
## When adding scripts
|
|
|
|
|
|
|
|
|
|
|
|
- Keep scripts focused and documented.
|
|
|
|
|
|
- Add a short entry in the relevant doc (or create one if missing).
|
