---
title: Lingering emergency settings-revert alerts
---

# Lingering emergency settings-revert alerts

## What it is

Sometimes an AI agent flips one of your settings OFF as an **emergency workaround** — a
"kill-switch until the bug is fixed" change, made through the normal settings-approval flow
with a note explaining why. The problem: once the underlying bug is fixed, nothing used to
turn the setting back on. The override just sat in your config forever, silently keeping a
fixed feature disabled (this really happened: mobile instant new-session stayed off for a
week after its bug was fixed).

Omniscio now audits those approved agent settings changes in the background (about every 6
hours). When it finds an **emergency-style revert** that is **3+ days old** and **still
overriding the app's default**, it raises ONE inbox card:

- The card names the setting, when it was changed, and **quotes the original reason** the
  agent gave at the time.
- Its **"Open this setting"** button jumps straight to that exact setting in Settings —
  scrolled to and highlighted — so restoring it is one tap away.
- **Dismissing the card is a permanent answer** for that revert: it never nags you again
  about the same change, even across restarts. (A brand-new emergency revert later gets its
  own fresh card.)
- If you (or anyone) restore the setting by hand, any still-open card **clears itself** —
  no stale reminders.

## Where to find it

### What you'll see

A card titled **"A temporary settings change is still in effect"** in your inbox, under the
Alerts group. It reads like: *"The setting 'mobileCreateOnSendEnabled' was changed as an
emergency workaround on 2026-07-19 and never restored — the reason given was: '…' It still
overrides the app default (current: false, default: true)."*

Your choices:

- **Open this setting** — jump to it in Settings and flip it back.
- **Dismiss** — keep the setting as it is; Omniscio won't ask about this revert again.
- **Start session** — like every alert card, you can spin up an agent session about it.

## How it behaves

### Details & limits

- Only **agent-made** settings changes are audited (they leave an approval-note audit
  trail). A change you make yourself in Settings is treated as deliberate and never nagged.
- A revert counts as "emergency-style" when its approval note says so — words like
  *emergency, revert, kill-switch, temporary, workaround, "until … fixed"*.
- **A restore back to where it was doesn't nag.** If a setting is temporarily changed and
  then set *back* to the value it had before (e.g. flipped for a test, then restored),
  Omniscio recognizes that round-trip and stays quiet — even when the restore's own note
  reads like a "revert" and the restored value differs from the factory default. Only a
  change that actually *leaves* a setting on a lingering non-default value is surfaced.
- At most 5 new cards surface per sweep (a backlog trickles in politely).
- These cards respect the master **agent alerts** switch (Settings → Notifications).

## Related

Nothing else in the library covers this audit, so start at [INDEX.md](INDEX.md), the library index, to find the pages about settings and about the inbox alerts Omniscio raises.