docs: add a Security page - #26
Merged
Merged
Conversation
New Project-section page enumerating the security model that follows from being read-only and local-only: what it reads (metadata only, no prompt text or tool output), what it never does (no writes, no signals, no shell-outs, no unsafe), the exact two network calls it can make, the one fixed command line the upgrade prompt runs, and the files it touches on disk. Also rewords "The longer view of what agent-top is and is not is in Vision" into a clearer see-also sentence.
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
1 participant
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
docs/security.mdunder Project: what agent-top reads (metadata only), what it never does (no writes, no signals, no shell-outs, no unsafe code), the two network calls it can make enumerated exactly (version check,trace --endpoint), the one fixed command line the upgrade prompt runs, and the files it touches on disk.Test plan
mise run docs:build(strict) passes.