Add local detection insights - #13
Merged
Merged
Conversation
Co-authored-by: Codex <noreply@openai.com>
theMobiusStrip
marked this pull request as ready for review
July 23, 2026 23:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Perch already retains minimal detection metadata locally, but users had no durable way to explore what the endpoint observed after the transient risk cards disappeared. This adds immediate endpoint awareness while preserving Perch's small, offline, read-only identity.
User impact
Users can inspect recent caution and danger trends directly in Perch and clearly see that an observed request does not prove execution, approval, or outcome. Existing monitoring and export behavior remain unchanged.
Validation
make verifymake appcodesign --verify --deep --strict dist/Perch.appGenerated with Codex.