feat(desktop): add local provider allowance indicator#2765
Draft
NYTEMODEONLY wants to merge 2 commits into
Draft
feat(desktop): add local provider allowance indicator#2765NYTEMODEONLY wants to merge 2 commits into
NYTEMODEONLY wants to merge 2 commits into
Conversation
Co-authored-by: nytemodeonly <contact@nytemode.com> Signed-off-by: nytemodeonly <contact@nytemode.com>
Co-authored-by: nytemodeonly <contact@nytemode.com> Signed-off-by: nytemodeonly <contact@nytemode.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.
What changed
Closes #2764.
Tauri command surface
Settings → Experiments
response-ID correlation, timeout/process-tree cleanup, and invalid-shape
rejection
Why
Users should be able to see the constraining window on their personal AI
provider allowance without leaving Buzz. The architecture must remain
provider-neutral without pretending that organization API billing or scraped
consumer pages are equivalent to personal subscription allowance.
Privacy
The Codex adapter reuses the existing local Codex sign-in. Buzz stores only the
non-secret provider preference. No credentials, raw responses, account
identifiers, or provider error bodies cross IPC or enter logs, analytics, crash
payloads, or Nostr. Only provider, product, source, plan, normalized windows,
optional totals, and freshness reach the frontend. Claude and Grok expose
capability metadata only and make no provider calls.
Validation
83a9e156ca773bb542244b6d359c7666427544abjust desktop-ci: static checks, TypeScript validation, productionbuild, Cargo check, Rust formatting, and all Desktop tests
window, constraining-window selection, and persistence
expected
Settings, manual refresh, focus return, explicit Codex selection, and restart
all returned allowance windows and optional totals rendered
The broader repository
just cireaches untouched mobile code and is blockedlocally because this Mac has Dart 3.10.7 while the repository requires Dart
3.11.4 / Flutter 3.44.8. Desktop CI is fully green.
Manual test
provider-scoped data remain coherent.
Deferred
contract