Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runaegis.co/llms.txt

Use this file to discover all available pages before exploring further.

A freeze window is a scheduled time period during which Aegis automatically blocks all agent write actions. When an agent attempts a write operation inside a freeze window, Aegis returns DENY, the same outcome as any other blocked action, without requiring you to manually intervene. Freeze windows are useful for release lockdowns, change freeze periods, on-call hours, and public holidays.

Prerequisite: enable the policy

Freeze windows only take effect when the Freeze Window Enforcement policy is active. If this policy is disabled, Aegis will not check freeze windows when evaluating agent actions.
Creating a freeze window does not automatically block agent writes. You must enable the Freeze Window Enforcement policy under Dashboard > Policies for the schedule to be enforced.

Creating a freeze window

1

Open Freeze Windows

Navigate to Dashboard > Freeze Windows in the sidebar.
2

Click New Window

Click the New Window button in the top-right corner of the page. A creation form slides into view.
3

Set the schedule

Fill in the following fields:
  • Timezone, select the timezone the window times should be interpreted in.
  • Days, select the days of the week the freeze applies. You can select individual days, weekdays, or every day.
  • Start time, the time each selected day when the freeze begins.
  • End time, the time each selected day when the freeze lifts.
4

Click Create window

Submit the form. The new window appears in the active freeze windows list immediately.

What happens during a freeze window

When Aegis evaluates an agent action and determines that the current time falls within an active freeze window, it returns DENY for any write operation. The agent receives an error response and the action is not executed. Read-only operations are not affected by freeze windows.
A freeze window applies to all agent sessions under your account. There is no per-agent or per-repository scoping at the freeze window level, use policies for more granular control.

Editing a freeze window

To update an existing freeze window:
  1. Find the window in the list on the Freeze Windows page.
  2. Click the Edit button on the right side of the row.
  3. The creation form reopens pre-populated with the current values.
  4. Adjust any fields and click Update window.
The updated schedule takes effect immediately.

Deleting a freeze window

To remove a freeze window:
  1. Find the window in the list on the Freeze Windows page.
  2. Click the Delete button on the right side of the row.
  3. Confirm the deletion in the dialog.
The window is removed and its schedule is no longer enforced.

Common use cases

Release nights

Block agent writes during your deployment window to prevent unintended changes from landing alongside a production release.

Change freeze periods

Enforce your organization’s change freeze policy automatically without relying on manual communication to agents or developers.

Planned maintenance

Prevent agents from writing to infrastructure repositories while systems are undergoing maintenance and in a known-bad state.

Holidays and weekends

Schedule recurring freezes for days when on-call coverage is reduced and you want agents to stand down automatically.
You can create multiple freeze windows to cover different schedules. For example, one window for weekday business hours and another for weekend coverage. Each window is evaluated independently.