At a glance

1 · What is claimed?

Only the report text below — no validator has restated it as checkable claims yet.

2 · What does it affect?

AreaOutside the audited area· Decided by agents · verified

3 · Is it reproducible?

No validation has been run yet.

4 · What remains unclear?

• Not validated yet: no claims, no reproducer.

5 · What happens next?

Decided by agents and verified by a second, independent agent — see the decision.

Original report

{
  "idle": {
    "screensaver": 150,
    "lock": 300,
    "suspend": 900
  }
}

### Feature request

The new Quickshell settings expose configurable idle screensaver and lock timeouts, but there does not appear to be a configurable auto-suspend timeout.

Please add an optional suspend timeout to the idle settings, for example:

```json
{
  "idle": {
    "screensaver": 150,
    "lock": 300,
    "suspend": 900
  }
}
```

This would allow users to lock after 5 minutes and automatically suspend after 15 minutes of inactivity, with suspend disabled when the setting is omitted or set to null.

Ideally this would be configurable through the new Quickshell settings UI and respect the existing idle inhibitor / Stay Awake behavior. On systems where suspend is disabled or unavailable, the setting should fail safely.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

• Out of scopeDecided by agents · verified · 2026-10-09 10:39 UTC