Skip to content

Add Duck ai usage warning debug screen - #9823

Open
YoussefKeyrouz wants to merge 1 commit into
feature/youssef/chat_limit_messagingfrom
feature/youssef/usage_limit_debug_screen
Open

YoussefKeyrouz wants to merge 1 commit into
feature/youssef/chat_limit_messagingfrom
feature/youssef/usage_limit_debug_screen

Conversation

@YoussefKeyrouz

@YoussefKeyrouz YoussefKeyrouz commented Sep 22, 2026 •

Copy link
Copy Markdown
Collaborator

Task/Issue URL: https://app.asana.com/1/137249556945/project/1212810093780571/task/1218737010316389?focus=true
Tech Design URL (if applicable): https://app.asana.com/1/137249556945/project/72649045549333/task/1218250488028912?focus=true
API Proposals URL(s) (if applicable):

Description

Stacked PR 2

Adds an internal-only "Usage Warnings" screen under the Duck.ai dev tools. It lists the high-usage messages dismissed by the user and lets a tester reset those dismissals.

This is the home for the usage-limit debug controls coming with the next slices.

Steps to test this PR

Entry

  • Internal build. Settings > Developer settings > Duck.ai. A "Usage Warnings" row is listed and opens the screen

Dismissals

  • Enable duckAiUsageWarnings in Feature Flag Inventory
  • Login to an account with PRO subscription (Access to Opus)
  • Fresh state: "Dismissed high-usage models" says "None" and the reset button is disabled
  • Select Opus 4.8 in Duck.ai mode, dismiss the notice with the X.
  • Return to the dev screen: The row lists claude-opus-4-8 and the button is enabled
  • Tap "Reset high-usage dismissals".
  • Open the native input with Opus 4.8 selected. The notice is back

UI changes

Screenshot_20260922_022948

@YoussefKeyrouz
YoussefKeyrouz added this pull request to stack #9824 September 22, 2026 09:32

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

Tip: disable this comment in your organization's Code Review settings.

@YoussefKeyrouz
YoussefKeyrouz force-pushed the feature/youssef/usage_limit_debug_screen branch from 43b2467 to bb9afd4 Compare September 23, 2026 12:03

@joshliebe joshliebe left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested, works as expected ✅🚀

@YoussefKeyrouz
YoussefKeyrouz force-pushed the feature/youssef/usage_limit_debug_screen branch from bb9afd4 to 78f9c4d Compare September 24, 2026 14:44
@YoussefKeyrouz
YoussefKeyrouz force-pushed the feature/youssef/usage_limit_debug_screen branch from 78f9c4d to d446a2a Compare September 27, 2026 12:48

@malmstein malmstein left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

</com.google.android.material.appbar.AppBarLayout>

<LinearLayout
android:id="@+id/contentLayout"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: worth wrapping contentLayout in a ScrollView now, since the description says this screen is where the usage limit controls land next. activity_duck_ai_dev.xml already scrolls for the same reason.

@malmstein malmstein self-assigned this Sep 28, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants