What problem does this solve in your TCC permission workflow?
Reviewing and correcting many rows one cell at a time can be slow. Users may want a quick way to normalize obvious entries before making smaller manual adjustments.
What behaviour do you want?
Add an “Auto-fix” action that analyzes the current table and proposes changes automatically.
The action should offer at least two modes:
- Default: restore a conservative baseline/default state
- Suggested: apply a more opinionated recommendation set
Ideally the action should stage changes as normal pending edits so the user can review them before export.
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This builds directly on Clearance’s existing local edit/export workflow by helping users prepare safer, faster bulk edits on a copied database.
Scope check
Please confirm this request fits the project scope in CONTRIBUTING.md: local file workflow, no network dependency, and no writes to system TCC files.
Additional context
To keep the feature safe and predictable:
- show a preview/count of proposed changes before applying
- mark auto-generated edits as pending, not final
- explain how “default” differs from “suggested”
- allow one-click reset if the result is too aggressive
What problem does this solve in your TCC permission workflow?
Reviewing and correcting many rows one cell at a time can be slow. Users may want a quick way to normalize obvious entries before making smaller manual adjustments.
What behaviour do you want?
Add an “Auto-fix” action that analyzes the current table and proposes changes automatically.
The action should offer at least two modes:
Ideally the action should stage changes as normal pending edits so the user can review them before export.
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This builds directly on Clearance’s existing local edit/export workflow by helping users prepare safer, faster bulk edits on a copied database.
Scope check
Please confirm this request fits the project scope in
CONTRIBUTING.md: local file workflow, no network dependency, and no writes to system TCC files.Additional context
To keep the feature safe and predictable: