What problem does this solve in your TCC permission workflow?
Before exporting a modified database, users may want a clear review of exactly what changed so they can catch mistakes and verify edits with confidence.
What behaviour do you want?
Show a diff or change summary for the current session before writing or exporting the database.
At minimum, the view should identify:
- which apps changed
- which permission columns changed
- the before/after value for each change
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This strengthens the existing local edit-and-export workflow by adding a review step before the user commits changes to the 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
This could be a modal, side panel, or export preview. The key requirement is making pending changes auditable before the modified .db is saved.
What problem does this solve in your TCC permission workflow?
Before exporting a modified database, users may want a clear review of exactly what changed so they can catch mistakes and verify edits with confidence.
What behaviour do you want?
Show a diff or change summary for the current session before writing or exporting the database.
At minimum, the view should identify:
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This strengthens the existing local edit-and-export workflow by adding a review step before the user commits changes to the 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
This could be a modal, side panel, or export preview. The key requirement is making pending changes auditable before the modified
.dbis saved.