Quiet Hours & Scheduling Controls

Quiet Hours let you define time windows when the agent should not send messages or take visible actions on your behalf. Your agent keeps working in the background — reading, processing, and preparing — but holds all outbound activity until the quiet period ends.

How It Works

When a quiet window is active:

Inbound events are still collected. Messages arrive, emails are read, calendar changes are tracked, and repo activity is monitored as normal.
Processing continues. The agent evaluates events, drafts replies, and prepares actions just as it would outside of quiet hours.
Outbound actions are queued. Any action that would result in a visible effect — sending a message, posting a reply, triggering an automation, updating a calendar event — is held in a queue rather than executed immediately.
Queue flushes automatically. As soon as the quiet window ends, queued actions are dispatched in order.

This means you get the full benefit of continuous AI processing without interruptions at unwanted hours.

Configuration

Quiet Hours are configured per-agent in your Sidekick dashboard.

Setting a Quiet Window

Open Settings → Agent Behavior → Quiet Hours.
Toggle Enable Quiet Hours on.
Set your Start time and End time.
Select your Timezone from the dropdown.
Save your settings.

You can define multiple quiet windows if needed (for example, a midday focus block in addition to overnight hours).

Timezone Awareness

Quiet hours are always evaluated against the timezone you select — not the server's timezone. If you travel, update your timezone setting so the schedule continues to match your local day.

Example: A quiet window of 22:00 – 08:00 in America/New_York will correctly shift if you change your timezone to Europe/London, becoming 22:00 – 08:00 BST.

Queued Actions

Actions queued during a quiet window can be reviewed before they are sent.

Navigate to Activity → Pending Actions to see what is scheduled to go out.
Individual queued actions can be cancelled, edited, or sent immediately at any time — even during a quiet window.
Actions are dispatched in the order they were queued, immediately after the window closes.

Supported Action Types

The following action categories are subject to quiet hours gating:

Action Type	Queued During Quiet Hours?
Send message (Slack, Teams, Discord, etc.)	✅ Yes
Send or reply to email	✅ Yes
Post a comment (GitHub, Jira, Linear, etc.)	✅ Yes
Calendar event creation / updates	✅ Yes
Smart home / device actions	✅ Yes
Event ingestion and processing	❌ No (continues normally)
Skill background tasks	❌ No (continues normally)

Notes

Quiet Hours apply globally across all connected integrations unless overridden at the integration level (per-integration overrides coming in a future release).
If the agent is mid-action when a quiet window starts, the current action completes before gating begins.
ClawHub skills that trigger outbound actions via the standard adapter interface are automatically subject to quiet hours — no skill-level changes are required.