3 Commits

Include renames

Author	SHA1	Message	Date
Mohamed Boudra	5eb4c8afad	feat(usage): show each agent's own plan usage in its context window details (#5975) ... * feat(usage): stream reports for live agent accounts Resolve account scope from the running harness environment without invoking lifecycle hooks. Keep the client aggregate result while delivering report updates as each fetch settles; the app presentation follows separately. * fix(usage): retain account scope for open agent sessions Capture the launch environment once per session, independently of lazy child-process startup or exit. Use a session UUID for registry identity. Update remaining global discovery fixtures to the scoped SDK contract. * test(usage): update browser fixtures for scoped report streams * feat(usage): let a usage card show window rows without pins UsageCard takes a required pinnable prop. When false, a window row is a plain bar: no Pressable, hover highlight, or pin glyph. The settings Usage list passes true. * feat(usage): show the agent's usage in the context window popover Reports stream into the query cache as each update arrives, for the host list and for a new per-agent query keyed by agent. The context window popover fetches its agent's reports while open and renders one unpinnable card per report as it lands, a loading sentence before the first, the request error as a sentence, and nothing on hosts without usage reports. * feat(usage): hide the Refresh button on popover usage cards UsageCard takes a required refreshable prop. The popover passes false because its content takes no pointer events, so the button could not be pressed; the card then shows its freshness inline. The settings Usage list keeps the button. * feat(usage): make the sidebar Usage summary opt-in The sidebar Usage item starts hidden on every layout, not only on compact ones, so resolveSidebarNavItems drops its compact input. While the summary is off, the Usage list renders window rows without pins; saved pins stay in preferences and return when it is turned on. Specs that read the summary now turn it on first. * docs(glossary): describe the popover usage card and the opt-in sidebar summary * fix(usage): show a popover request error without retrying A daemon error for an agent's usage, such as an unknown agent, does not heal on retry, and reopening the popover fetches again. Retrying held the loading sentence for about seven seconds before the error. * test(usage): cover agent usage in the context window popover The usage fixture records agentId, streams reports held behind promises, and can switch host support between reloads. The meter spec walks loading, streaming, a report problem, a request error and a host without usage reports, on desktop and compact in both themes. * fix(usage): keep the plain context window tooltip on hosts without usage The popover widened to fit usage cards on every host. Hosts that cannot report usage now keep the tooltip's default padding and width, as before, and mount no usage section. * fix(usage): let a report's Refresh replace it in the agent's list too Refresh wrote the refreshed report only into the host's list, so a card rendered from an agent's list kept the old report. Both lists now sit under one host key and Refresh replaces the report in each that holds it. * feat(usage): open the context window details in a sheet on compact screens Wide screens keep the tooltip. On compact screens pressing the meter opens a content-sized bottom sheet titled Context window. Both render one ContextWindowDetails body; only the sheet's usage cards have Refresh, since the tooltip cannot be pressed. Pins stay off in both. * test(usage): cover the compact context window sheet On the compact viewport the meter opens the sheet; its cards have Refresh, a Refresh replaces the card, and Close dismisses the sheet. The glossary names the sheet. * feat(ui): give tooltips and the context window sheet accessible roles Tooltip content is role=tooltip, and the context window sheet is a dialog named Context window, so assistive tech and tests find them by role. The agent usage message drops its test ID; it is found by its text. * test(usage): reshape the context window and Usage switch specs as journeys The context window spec runs one tooltip journey and one sheet journey per theme, with no layout branches. Its fixture script, meter actions and report builders move to a context-window helper, and it finds the meter, tooltip, sheet and Refresh buttons by role. The theme comes from the system colour scheme. The Usage switch test uses named helpers for the Usage icon and the Summary in sidebar switch. * fix(usage): say an agent's usage request failed instead of showing older reports A failed request keeps whatever reports the query held: those from an earlier open, or those that streamed in before the failure. The context window details showed them as if they were the agent's current usage. The request error now wins over held reports. * test(usage): let a fixture clean up the context window spec's agent The tooltip and sheet tests no longer wrap their steps in try/finally; a spec-local fixture seeds the agent and removes it after the test. * fix(usage): keep a refreshed report when the list it is in finishes Pressing Refresh on one card while another source was still streaming put the pre-refresh report back: the finished list replaced the query's data with the copies the request had fetched when it started. A report now keeps whichever copy was fetched later, both when a streamed copy arrives and when the finished list replaces the streamed one. * fix(usage): show only the login a resumed agent runs under now An agent resumed under another login keeps its ID, so its usage query kept the previous login's reports: reopening the context window showed them while the new login's reports loaded, then both side by side until the request finished. The agent's usage is now dropped as soon as its tooltip or sheet closes, so each open loads the login the agent runs under at that moment. * fix(usage): stop a closed agent usage request from writing reports Closing the context window details cancels the agent's usage request and drops reports still on their way, so reopening after a resume under another login sends a new request instead of joining the old one.	2026-10-03 23:12:57 +01:00
Mohamed Boudra	05e94ab52e	Keep usage logins visible and explain unavailable quota (#5876) ... * fix(usage): keep existing logins visible and explain unavailable quota Credential discovery must preserve accounts whose login exists even when it has expired. Keep vendor failures on the discovered account and isolate discovery failures without inventing provider cards. * test(usage): align credential route tests with account discovery	2026-10-02 00:30:11 +01:00
Mohamed Boudra	792715e762	feat(usage): usage sources as built-in plugins, following the session's account (#5465) ... * feat(server): run internal plugins in-process through the plugin runtime * fix(server): harden internal plugin startup and boundary checks * feat(usage): add plugin usage sources and Codex discovery * fix(usage): share SDK helpers and bound source cache * feat(usage): migrate usage fetchers to plugin sources Serve the legacy usage RPC from discovered source reports so older apps retain the same host usage list while new clients use the source registry. Keep credential reads and normalization inside each source. * refactor(usage): shape sources as fetch functions Keep the plugin usage API limited to stable report and presentation helpers. Source-local parsers and timeout handling preserve credential and response parity while the cases move alongside each source. * feat(usage): resolve reports from active session accounts Resolve source inputs at fetch time so model and credential changes select the account each session spends. Keep the legacy discovered-account RPC for existing clients. Sync OpenCode model events outside foreground turns so usage follows model switches. * fix usage source discovery and session report parity * test adapter usage references through daemon RPC * name usage reference contract across server * refactor(usage): own usage RPCs and validate session auth * feat(omp): resolve session usage from active OAuth credential * fix(omp): match usage source input and valid credential fallback * test(omp): use upstream credential database schema * test(omp): verify live session usage references * fix(usage): declare YAML parser and consolidate credential validation * feat(app): show usage sources in the composer and a Usage screen Replace the provider-matched usage in the context ring tooltip with a composer pill driven by agent.get_usage_report, add a sidebar Usage screen over usage.list_reports grouped by host, and move the host settings Usage page to usage.list_reports. Hosts without features.usageSources show an update message. Source icons come from the report's catalog SVG. The app no longer calls provider.usage.list. * fix(usage): declare the Paseo requirement on internal usage-source plugins A manifest without requirements.paseo targets Paseo before 0.8, so the daemon refused to start eight of the nine usage sources. * fix(app): keep host connection statuses live under the React Compiler The hook read a store version only as a memo trigger (void version); the compiler dropped it, so pages that mounted before a host came online kept showing it as connecting. * fix(app): place the context ring slot before the usage pill The ring reserves its slot before it has data. With the pill first, the empty slot sat between the pill and the mic; now it falls in the flexible space. * refactor(app): extract the settings page layout into PageLayout Desktop puts the title in the page above a centered column; compact moves it into a back header. Settings renders the same pixels through it. * feat(app): lay out the Usage screen like a settings page The title moves from the header bar into the page on desktop; compact gets the settings back header, which returns home when the screen was opened by URL. * refactor(app): drop the unused actions slot from PageLayout * test(plugin): classify the usage source SDK entry * fix(usage): preserve platform test contracts * fix(settings): preserve page title test contract * feat(usage): identify and cache reports by account ID Keep report identity stable across input routes and token rotation, and make selective refresh operate on known account reports. * feat(app): read usage reports through report IDs Share report data between agent pills and host views while preserving the existing popover interaction for the next UI phase. * fix(usage): keep account identity aligned with credentials Read labels from local token claims and use one credential lookup for usage fetches and account identification. Bound cached profile identities across token rotation. * fix(usage): isolate failure IDs and prune expired reports Failure reports live outside the account-key namespace, and cache writes discard entries past the five-minute TTL. * refactor(app): share the compact time-ago prose formatter Move the tab tooltip's "3m" -> "3m ago" wording into utils/time so the usage card can reuse it. * feat(usage): show when each report was fetched The usage card reads fetchedAt as "Updated 3m ago": a tooltip on the card header where hover exists (web, desktop), printed in the card footer on native and compact. Shared by the pill popover and the Usage screen. * feat(usage): open the pill popover from cache and refresh on demand Opening the popover no longer forces a vendor fetch; it shows the cached report. A Refresh control force-refreshes only this report (usage.list_reports with its single ID and forceRefresh), shows Refreshing... while it runs, keeps the previous report visible, and says "Unable to refresh usage" if the request fails. * feat(app): let ToolbarButton show a tooltip other than its label An icon action can now say a status in its tooltip ("Updated 3m ago") while keeping its label for accessibility. * feat(usage): refresh a report from its card header Refresh is an icon button at the right edge of every usage card header, in the pill popover and on the Usage screen. It force-refreshes only that report, writes the result to the report's cache and its host list, shows a spinner and disables itself while pending, and prints "Unable to refresh usage" in the card on failure. Its tooltip carries the freshness; without hover the freshness stays in the card footer. The status indicator sits just left of the button, and the popover's separate refresh row is gone. * fix(server): include internal plugin assets in built output * feat(server): built-in plugins in /plugins (#5544) * feat(server): load compiled built-in Codex plugin * test(server): guard built-in plugin loading and installs * test(server): verify built-in plugins from dist in CI * refactor(server): migrate remaining usage sources to built-in plugins * test(server): guard all packaged usage source registrations * docs: describe usage validation across plugin hosts * test(ci): include built-in plugins in routing contract * test(server): import moved Codex usage source * fix(server): retain ACP updates received with session creation	2026-09-28 16:36:34 +01:00