Use a monitor to compare a page over time. Agents propose monitors. A person approves the proposal in Monitors before scheduling starts. Swarmtab must stay open; there is no hosted monitoring service.

Propose a check

{"name":"site","arguments":{"action":"monitor_add","url":"https://example.com","watch":{"format":"status"},"every":900}}

every is seconds. The minimum is 900 seconds and the maximum is 604,800 seconds. Human settings may require a longer minimum. There are at most 100 monitors. A status check watches response status. Other watch formats include Markdown, JSON fields, a selector and links. Choose a narrow watch so routine page changes do not create noise.

Approve and inspect

Review the URL, watch and interval in Monitors. Approve the exact proposal. The agent can list only its own monitors with site and {"action":"monitors"}. Human controls manage active monitors, including removal. An agent cannot approve its own monitor or remove an active one.

Change reports can include text and field differences. A webhook, when configured and approved by the human, sends signed counts. Treat this as an external destination and review it before enabling it. A monitor is separate from the interactive task. Review its status in the window and pause or remove it when you no longer need it. Closing an agent is not a monitor-removal control.

When checks stop

Check that the app is running, the monitor is approved, and the site is reachable under its current permissions and proxy. A sleeping Mac cannot guarantee a schedule. Review failures before reactivating a monitor rather than promising continuous coverage.