Conversation
…rded usage - show the fail-closed tool access boundary (toolPolicy rejected, use paseoTools and disallowedTools) in the Plugin tab, and note it in docs/configuration.md - say in the quota pill title and popover that quotas are the last recorded usage from the local agent database, not read live
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.
Why
Two spots in the OMP plugin UI leave users guessing:
toolPolicyis rejected at startup, but nothing in the UI says so or points topaseoTools/disallowedTools.Change
docs/configuration.mdpointing to it.No protocol or server behavior changes.
Verification
npm run typecheck,bun x biome check .clean.bun x vitest run: 848 passed, 7 skipped, 0 failed.