PandaOSPandaOS
Teach and automate

Unattended runs

Keep automations running while the window is closed, and decide what they may do without you.

Feature Updated 18 Nov 2026

What an unattended run is

An unattended run is an automation running while you are not watching, often with the PandaOS window closed. You care about it because nobody is there to answer a question, so the automation needs to know in advance what it may do.

A background service in the system tray keeps the scheduler, your connected apps and their sign-ins alive. Two switches in Settings, General, under Automations, control it, and both are on by default:

SwitchWhat it does
Start Background Service at LoginStarts PandaOS in the tray when you log in, without opening a window.
Keep Running in BackgroundClosing the window hides PandaOS to the tray instead of quitting. Quit it from the tray menu.

Quitting PandaOS stops every automation that runs on this computer until you open it again.

When the computer sleeps

Nothing runs while the computer sleeps. Each automation decides what happens to the runs it missed, under If a run is missed while asleep:

  • Run once: it runs one time shortly after the computer wakes or the service starts, however many runs were missed.
  • Skip: the missed run is recorded as skipped, with the reason "Machine was asleep" or "App was closed".

A new automation takes the default from Missed Runs After Sleep in Settings, General, which is Run once on wake. Automations made before this choice existed use Skip, so an update never starts runs you did not expect.

What it may do

Every automation has a permission mode. Open it and press the shield, Permissions & rules, to change it.

ModeWhat it means
Full accessRuns any tool and never asks. The simplest, and the most that can go wrong.
RestrictedA limited set of tools, and it never asks.
RulesOnly calls you allowed in advance run. Anything else pauses the run until you answer.

A new automation starts in the mode set under Default Automation Permissions in Settings, General, which is Rules until you change it. A run started by a webhook or an app event never gets Full access. It uses Rules, because what started it was written by someone else.

When a run asks for approval

In Rules mode, a call no rule covers pauses the run and shows a notification. Click it, or open Automations, where an approval card at the top shows the tool and everything it was about to send. Choose:

  • Deny: the call does not happen, and the automation carries on without it.
  • Approve once: this exact call runs, for this run only.
  • Approve & add as rule: the call runs, and a rule is saved so it runs without asking next time. Widen the rule before saving it if you like, for example from one address to *@your-domain.com.

Automation Approval Timeout in Settings, General is 24 hours by default. If you do not answer within it, the automation's fallback applies: deny the call and carry on, or fail the run.

A paused run does not survive a restart of PandaOS. It fails with "Interrupted while paused for approval" and runs again on its next schedule.

How rules match

A rule names one tool, and can add a matcher per setting of that tool. For example, gmail_send only when to matches *@pandata.de, or Bash only when command matches npm run *:check. A matcher is exact, glob, where * matches anything, or regex. Commands and file paths must match their case, except Windows paths, which match in any case. Other values, such as an email address or a subject, match in any case. Every matcher on a rule must match, and any rule in the list can allow a call. Tools that only read, such as Read, Grep and Glob, are always allowed.

Rules attach to one automation, or come from a rule set. That is a reusable bundle you manage in the Rule-set library in the Automations header and share across automations. The automation's permissions show every rule it may use and where each one comes from.

An automation in Rules mode always runs on the Claude Code engine, whatever engine you picked for it.

A run fails with credentials locked

An unattended run uses the app sign-ins stored on this computer. If the system keychain cannot be unlocked when a run starts, the run stops at once. The run detail shows an amber warning that the credentials could not be unlocked, with a notification. It does not run half signed in, and it runs again on its next schedule.