Repository navigation
docs: a revoked token's tunnels end within 40 seconds - #14
Merged
Merged
Conversation
…elay ends them at once State the revocation bound the Perfloop API now guarantees, and the immediate alternative. Describe the per-tenant tunnel limit without the API's internal layout, and keep SECURITY.md to the reporting address and what is supported. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
States the revocation bound the Perfloop API guarantees for open tunnels (40 seconds, including when the API cannot confirm the key) and that stopping the relay ends its tunnels at once. Describes the per-tenant tunnel limit without internal detail, and trims SECURITY.md to the reporting address and what is supported. Documentation only; no code change.
🤖 Generated with Claude Code